Helix 3.7: The Freeman Update

The overall speed and acceleration was generally improved, yes I agree, it's the 0.1, 1ms, 1%, 1Hz, single digit step parameters that are too sensitive.
Is it possible to make the 0.1 clicks a little less sensitive and keep the new acceleration ballistics as is?
 
Which Helix hardware do you use? I wonder if it behaves differently on Floor vs. LT vs. Stomp...? On my Floor I purchased in 2019, the current ballistics are fantastic. I haven't encountered any jumpiness on EQ settings or block skipping.

I'm not doubting the experience of others. I'm just wondering if it's more to do with hardware differences or aging encoders vs. the software implementation.
HX Stomp. It's definitely a firmware bug from my point of view.
I described the skipping here.
 
100%
If there is one thing that annoys me when using my Helix is the encoder sensitivity after 3.50.
I avoid tweaking on the hardware as much as possible due to this, it used to be a tad slow but now it's out of control.
Trying to adjust 0.1 steps tests my patience, forget about it if your encoders are not brand new and skip clicks.


From 3.50 release notes:

internet seriously GIF


Going from 0 to 10 in one turn is not a drastic improvement if adjusting 0.1 steps precision has been compromised.
I much prefer comfortable 0.1 step adjustment than 360 in one turn, heck I would even take pre-3.50 ballistics than what we have now.

I advocated for 'one turn' sensitivity because it allows a better sense of what the control is doing but what we got in 3.50 is way too sensitive.
It was a good step in the right direction but the result is not satisfactory in my personal opinion.
We need a happy medium.
If you need to adjust in 0.1 increments, a hardware knob, or software slider is not the tool of choice. Speaking of tools, if you're adjusting in 0.1 increments... :rofl :beer
 
Last edited:
HX Stomp. It's definitely a firmware bug from my point of view.
I described the skipping here.
Interesting, so they updated global encoder sensitivity on the Stomp and not only the encoders under the screen, was that even necessary?
On the big Helix/LT units the joystick encoder rotation is much more stiff and clicky than the screen encoders, so block scrolling was never an issue after even after 3.50.

The encoders behavior can do with more refinement across the entire SKU range.
I think user experience is important and DI himself is a big fan of muscle memory and interface familiarity.
 
Last edited:
Electronically speaking, in every button press and encoder 'click' there is a small amount of noise when switching happens that can cause false triggering.
The solution to that can be in software or hardware, it's called Debounce or Debouncing, just adding a small amount of 'wait time' after the first rise/fall edges can solve that.

overview.jpg


I am sure there is a debounce code in the Helix like in everything else, but maybe it could use a touch more 'wait time' between clicks to mitigate false triggering on encoders that are slightly noisier?
 
Electronically speaking, in every button press and encoder 'click' there is a small amount of noise when switching happens that can cause false triggering.
The solution to that can be in software or hardware, it's called Debounce or Debouncing, just adding a small amount of 'wait time' after the first rise/fall edges can solve that.

overview.jpg


I am sure there is a debounce code in the Helix like in everything else, but maybe it could use a touch more 'wait time' between clicks to mitigate false triggering on encoders that are slightly noisier?
You ever own an HP 50G calculator? Am I over-exposing my nerd factor here?
 
The overall speed and acceleration was generally improved, yes I agree, it's the 0.1, 1ms, 1%, 1Hz, single digit step parameters that are too sensitive.
Is it possible to make the 0.1 clicks a little less sensitive and keep the new acceleration ballistics as is?

Yes please.
And fwiw, I just hate the new ballistics. And there's a good reason for it: the HX family encoders are operating with very little friction. Way less friction than on any, say, drive pedal, amp or whatsoever. In addition, their heads are pretty small, too. As a result, we have pretty tiny encoders with very little haptic feedback. For such encoders, "parameter value movement resolution" as in the analog world is simply making no sense. They just *need* to be less sensitive for proper operation.

Fwiw #2: I absolutely liked the old behaviour, it's just been the larger parameter changes that were cumbersome. No problem, add "aufo acceleration" - move the knob quicker and you're getting from one end to the other end of the parameter range quicker. Zoom does it that way and it's working absolutely fine (add to this that Zoom is using "clicking" encoders, which is fantastic, too - but "Hey, no, here at Line 6 we're rather re-inventing the wheel!", just that it turned out to become a triangle...).

Ffs, at least give us an option to switch back to the old behaviour. Would be the very first thing I'd do.
 
It definitely doesn't do that on my stomp. That would annoy the crap out of me. Hope you get a fix for it soon.

Just wait until it happens. It will, at one point in time (I have been lucky at first, too - now it seems to happen more often, but that might have to do with the fact that I'm editing onboard a little more than before for some reasons). Simply because it's a software thing.
No idea what takes L6 so long to fix this most horrible issue.
 
No problem, add "aufo acceleration" - move the knob quicker and you're getting from one end to the other end of the parameter range quicker.
It had this before, though. And it worked so poorly that's probably why you didn't notice it ;) The only way I could get acceleration to kick-in was to spin the knob by sliding my finger down the side of it. And the knobs are spaced so closely together that you can't really do this without getting your knuckle stuck between them.

I think this one definitely comes down to user preference. For me, the new encoder behavior is excellent. I love it. But a sensitivity setting might make everyone happy.
 
It had this before, though. And it worked so poorly that's probably why you didn't notice it ;) The only way I could get acceleration to kick-in was to spin the knob by sliding my finger down the side of it. And the knobs are spaced so closely together that you can't really do this without getting your knuckle stuck between them.

I think this one definitely comes down to user preference. For me, the new encoder behavior is excellent. I love it. But a sensitivity setting might make everyone happy.
Couldn't agree more, even did the same thing sliding the finger on the knob, hahaha!!! 😂

I do think the current encoder "feel" is nice, but definitely wouldn't oppose a global setting parameter for anyone who prefers the "old" version. Should be simple to implement.

Simplement. Huh? 😜
 
Back
Top