Two bugs on Helix editor

[stephane_dupont]

Two bug reports I made to the Line 6 support center, the second making the editor unusable for me. Be cautious if you don't want to lose some time parameters in your presets!

 

Bug 1:

When we send a Program Change MIDI message to the Helix, the following behavior occurs:

 

- If we send a program change with value X and the preset X is not selected, preset X is selected (normal behavior)

- If we send a program change with value X and the preset X is already selected, preset 0 is selected: this is not normal, was not the case before the last firmware and has no sense. It should do nothing (or reload the current preset, but I would prefer like before, that it does nothing), but certainly not selecting preset 0!

 

Bug 2:

There's a bug with the timings in Helix editor. I have a preset with a controller (EXP pedal 2) changing the Time parameter of a Simple Delay from 596ms to 964ms. It works well, but:

 

- If Helix editor is open, it goes from 590ms to 960ms instead

- If I save the preset while Helix editor is open, I lose my values, they became theses rounded 590ms and 960ms values forever.

 

Hopefully we can get a fix soon?

 

UPDATE: added on this thread: http://line6.com/support/topic/16083-helix-bug-reports/

[klangmaler]

You should add this here:

 

http://line6.com/support/topic/16083-helix-bug-reports/

[zooey]

Personally re  #1, I think a program change should ALWAYS recall the saved state of that preset. It should NOT do nothing, because that leaves any footswitches and controllers you changed while the preset was loaded in their current state, not how they were saved in the preset.

 

(And not that it needs to be said, but it should recall patch 0 either, that's just wrong.)