Helix Bug Reports

[haydenikerd]

Hi Helix community, my first time on here ! Having an issue with the volume / expression pedal...

 

I occasionally use swells in songs our band plays. For these, you take the volume pedal all the way to down to heel, play a chord or notes, and then open up the volume to get a neat shimmering effect. However, recently, even with the volume pedal cut all the way down, (it even reads 0% on the display) a weak signal still comes thru ? Wondering if anyone has run into this or if anyone can help me here. 

 

Short version -- when my volume pedal is all the way off, my volume is not all the way off.

 

Thank y'all !!

[PeterHamm]

1 hour ago, haydenikerd said:

Hi Helix community, my first time on here ! Having an issue with the volume / expression pedal...

 

I occasionally use swells in songs our band plays. For these, you take the volume pedal all the way to down to heel, play a chord or notes, and then open up the volume to get a neat shimmering effect. However, recently, even with the volume pedal cut all the way down, (it even reads 0% on the display) a weak signal still comes thru ? Wondering if anyone has run into this or if anyone can help me here. 

 

Short version -- when my volume pedal is all the way off, my volume is not all the way off.

 

Thank y'all !!

Double check first to make sure that you don't have the guitar inputting on another path. Perhaps you could take a screen shot of your signal chain? Never seen that happen.

[rd2rk]

5 hours ago, haydenikerd said:

Hi Helix community, my first time on here ! Having an issue with the volume / expression pedal...

 

I occasionally use swells in songs our band plays. For these, you take the volume pedal all the way to down to heel, play a chord or notes, and then open up the volume to get a neat shimmering effect. However, recently, even with the volume pedal cut all the way down, (it even reads 0% on the display) a weak signal still comes thru ? Wondering if anyone has run into this or if anyone can help me here. 

 

Short version -- when my volume pedal is all the way off, my volume is not all the way off.

 

Thank y'all !!

 

Attach your preset (not a screenshot) and I'll load it on mine to test..

[Mutonium]

There appears to be a paste preset bug in HX Edit, at least with my HX Stomp running version 3.11.

 

The desired action is to paste the same preset multiple times, such as to clear out multiple slots with a blank preset or with a template.

 

Copy the preset.  Select multiple slots.  Right click and paste on one of the selected slots.  HX Edit then prompts, "Are you sure you want to overwrite the highlighted presets?"  Notice it says plural "presets."  Upon clicking "Yes," only the first selected preset is overwritten, even if you right clicked on one of the other presets in the selection.

 

It gets worse.  After pasting the first selected preset, if you then try to right click and paste on one of the remaining selected presets/slots, HX Edit jumps to the currently active preset slot, not the one you right clicked on.  Not even one of the selected presets/slots.

 

I've lost a couple of presets this way.  Tried to paste one preset into multiple selected presets/slots.  Only the first one is pasted.  Then, when right clicking on one of the remaining selected slots, HX Edit jumps to the currently loaded/active preset behind the prompt.  The prompt asks if you want to overwrite the preset, and I knew what I clicked on, so I click "Yes," only to find out the preset wasn't pasted into the clicked slot, and instead overwrote the active preset.

 

Am I doing something wrong?

[phil_m]

10 hours ago, Mutonium said:

There appears to be a paste preset bug in HX Edit, at least with my HX Stomp running version 3.11.

 

The desired action is to paste the same preset multiple times, such as to clear out multiple slots with a blank preset or with a template.

 

Copy the preset.  Select multiple slots.  Right click and paste on one of the selected slots.  HX Edit then prompts, "Are you sure you want to overwrite the highlighted presets?"  Notice it says plural "presets."  Upon clicking "Yes," only the first selected preset is overwritten, even if you right clicked on one of the other presets in the selection.

 

It gets worse.  After pasting the first selected preset, if you then try to right click and paste on one of the remaining selected presets/slots, HX Edit jumps to the currently active preset slot, not the one you right clicked on.  Not even one of the selected presets/slots.

 

I've lost a couple of presets this way.  Tried to paste one preset into multiple selected presets/slots.  Only the first one is pasted.  Then, when right clicking on one of the remaining selected slots, HX Edit jumps to the currently loaded/active preset behind the prompt.  The prompt asks if you want to overwrite the preset, and I knew what I clicked on, so I click "Yes," only to find out the preset wasn't pasted into the clicked slot, and instead overwrote the active preset.

 

Am I doing something wrong?

I don’t think there was ever a functionality that allowed you to paste the same presets into multiple slots at the same time. It’s like Excel - you can only paste into the same number of slots as you originally copied. If you want to paste the same preset into multiple slots, you just have to use the Paste function multiple times.

 

It might be some buggy behavior around that, but basically you’re trying to do something it wasn’t designed to do.

[DreadNotPop]

I just loaded my helix lt with the 3.11 update and not my up/down footswitches don't work. When I press on it to change the preset i can hear the preset change but the screen does not show a new preset or the corresponding number. Anyone else experiencing glitches. I want to go back to 3.10 

[datacommando]

11 hours ago, DreadNotPop said:

I just loaded my helix lt with the 3.11 update and not my up/down footswitches don't work. When I press on it to change the preset i can hear the preset change but the screen does not show a new preset or the corresponding number. Anyone else experiencing glitches. I want to go back to 3.10 

Why go backwards? It’s probably unnecessary. Thousands of happy Helix users in the world.

 

When updating the firmware, you must follow the installation instructions to the letter - up to, and including, a factory reset and restore from back up. If you haven’t done this, then you will experience problems.

 

From the 3.11 Update Notes:

Anything else I should know?

Yes. We STRONGLY recommend performing a factory reset AFTER UPDATING your Helix/HX firmware to 3.11 and THEN RESTORING YOUR BACKUP. (Backing up is part of the update process). Here's how to perform a factory reset. IMPORTANT: MAKE SURE YOU HAVE A BACKUP FIRST, AS A FACTORY RESET WILL ERASE ALL YOUR WORK!

• Helix Floor/LT: While holding footswitches 9 & 10 (bottom row, 2 middle switches), turn on Helix Floor/LT

 

When weird stuff happens the first thing to do is perform a factory reset - here’s the full list of options.

 

Reset Options

Helix Floor/LT

Button Combination	Description
2	LED light Fun
3 & 4	Test Mode
5 & 6	Global reset
7 & 8	Reset setlists to factory, Keep IRs
8 & 9	Reset setlists to factory, Clear IRs
9 & 10	Reset setlists to factory, Global reset, Clear IRs
10 & 11	Upgrades existing presets to latest format
11 & 12	Clear current preset
5 & 12	Clear setlists, clear IRs, Return system settings to default
6 & 12	Safe boot mode

To use Reset Options:

• Power off the Helix
• Hold the desired button combination
• Power on the Helix
• Release the button combination

 

Please note: Buttons are numbered from top left to bottom right.

 

Hope this helps/makes sense.

[Mutonium]

On 12/9/2021 at 9:16 AM, phil_m said:

I don’t think there was ever a functionality that allowed you to paste the same presets into multiple slots at the same time. It’s like Excel - you can only paste into the same number of slots as you originally copied. If you want to paste the same preset into multiple slots, you just have to use the Paste function multiple times.

 

It might be some buggy behavior around that, but basically you’re trying to do something it wasn’t designed to do.

 

Makes sense.  Thank you for the explanation.

 

Although, in Excel, I often paste the entry of one cell into multiple cells by copying the original cell, highlighting multiple cells, and then pasting it, which is why I tried a similar operation in HX Edit.  The fact that HX Edit prompted with a warning about overwriting the plural "presets" implied it was doing the same thing. 

 

The buggy operation is after trying that operation, when you click to paste on one of the remaining slots that were not written, but are still shown as highlighted, it warns you about overwriting the highlighted slot, but jumps to the active slot in the background.  If you do not notice that, you lose the active preset and there is no undo to recover it.

 

I know HX Edit is not trying to be Excel and will work the available options for copying presets.

[lvidarte]

I found this bug for Helix Rack, for firmware versions 3.10, 3.11 and 3.15.
The 3.01 version works well, it seems like this error was introduced on 3.10.
 

Bug description:
If I change the effect type of some block (example: from Amp+Cab to Reverb)
When I change the type in the first column and then I click some of the options on the second column,

the first column change again to the previous type.

That's why you can see something like this, on where the first column has not relation with the others:
- First column: Amp+Cab
- Second column: Mono/Stereo/Legacy
- Third column: All the reverb effects (Dynamic Hall, Hot Springs...)

Video:

 

[nkrcompany]

I'm using a Helix rack, just updated to 3.15 firmware (and made a factory reset too).

I'm using a midi controller and regularly use MIDI CC51, CC52, CC53, or CC54 messages to emulate footswitch operation. Unfortunately Helix Rack does not respond as expected. 

I don't know what version made this bug, but it guess it was present since 3.0. That's sure this bug was present in the preceding 3.11

 

In HX Edit I linked Footswitch 3-7 to turn on/off individual effects. So on the bypass/controller assign panel I made four setup for the individual blocks, setting parameter to Bypass, and Source the Footswitch 3-7. Now, when I send these CCs to Helix Rack sometimes it doesn't respond, sometimes it makes a preset change instead of turning on/off the individual effect blocks. Earlier this worked great and without problems.

 

I really would like to use these footswitch CCs, can you please to help to resolve this issue?

[Phillip1]

just updated to 3.15 and now my external footswitches FS7/FS8 (which were assigned to scroll up and down through my 4 snapshots) went all schizo on me.

 

it now skips randomly between the 4 snapshots rather than cycling up or down sequentially.

 

for example if i'm on snapshot 1 and i press the "up" footswitch once it won't go to 2, it'll go to 3 or maybe 4 etc.

 

it's almost as if it registers a single press as a double press.

 

anyone know what's going on?

[Schmalle]

In 3.15 I still find the Das Benzin level (both channels) too low. I use it with master at 2, because it looses clarity / high end and 'Diezelness' with higher values.

[theElevators]

In 3.15, HX Edit appears to be saving several presets by itself, when you change the Bypass Behavior in a different preset. 

 

Pre-req:

Set Snapshot Edit: Discard.  Expectation is that if you re-enter the preset/snapshot, any changes that you made will be discarded. 

 

Bug:

1. in HX Edit, go to a block of any preset, e.g. wah-wah

2. Go to Bypass/Controller Assign and locate the "Bypass" parameter.

3. Change the newly-added "Behavior" parameter to "Heel Down" or "Toe Down". 

4. Move the expression pedal up/down a few times

 

Go to a different preset, then come back. 

1. you will see the change you made has been saved for you. 

2. you will see the same change appears to be applied to other presets as well.  It appears that identical or nearly-identical presets are updated all at the same time. 

 

--

 

Expectation: No changes should be auto-saved, if you have Snapshot Edit disabled.  This bug only applies to Bypass Assignment Behavior change.  Other changes are discarded as they should be. 

 

[datacommando]

10 hours ago, theElevators said:

Change the newly-added "Behavior" parameter to "Heel Down" or "Toe Down"

Hi,

 

Is what you are experiencing something possibly related to this.

 

From the release notes

 

Bypass Assign > EXP Pedal 1/2 now has a new Behavior parameter to control how bypassing is handled. 

The default value "Toggle" behaves as this feature always has - bringing the pedal past threshold will toggle the block's bypass state from what it is currently (i.e. enable if currently bypassed and vice versa). "Toe Down" and "Heel Down" always bypass the block at the designated position, regardless of the block's starting state. So with "Heel Down" selected, the block will always enable when you cross the Position threshold and bypass when you return below it

[theElevators]

47 minutes ago, datacommando said:

Hi,

 

Is what you are experiencing something possibly related to this.

 

From the release notes

 

Bypass Assign > EXP Pedal 1/2 now has a new Behavior parameter to control how bypassing is handled. 

The default value "Toggle" behaves as this feature always has - bringing the pedal past threshold will toggle the block's bypass state from what it is currently (i.e. enable if currently bypassed and vice versa). "Toe Down" and "Heel Down" always bypass the block at the designated position, regardless of the block's starting state. So with "Heel Down" selected, the block will always enable when you cross the Position threshold and bypass when you return below it

Yes, this new parameter is not working correctly.  HX Edit automatically saves changes to it in unrelated presets. 

 

I started experimenting with different values of the bypass behavior, and observed that my preset and other presets got saved without me doing anything. 

[bassbene]

After updating to 3.15, I noticed that Rochester Comp block seems to have a quite big shift in phase.
Some of my presets that use that block in a parallel path sounded significantly different (loss of low end) after the update. I could trace it down to the Rochester comp block.

I could reproduce the issue with Helix native as well. The screenshots show an analyzer after Helix Native, fed with white noise. You can see the phase cancelations if the model is used in a parallel path.
Is this the "correct" behavior of the model? I am pretty sure that it sounded differently before the update to 3.15

[datacommando]

2 hours ago, theElevators said:

Yes, this new parameter is not working correctly.  HX Edit automatically saves changes to it in unrelated presets.

 

That's very odd. I haven't looked at the "Behaviours" option yet, may be time to check it out. 

 

Is it something in your Global Setting - Per Snapshot > Per Preset > Global ?

 

The reason I ask is, while typing this, I just tried on the Helix floor (not HX Edit) and is only worked on that one specific preset, none of the others. Does It happen whatever Wah Model you're using or just one model?

 

[theElevators]

1 hour ago, datacommando said:

 

That's very odd. I haven't looked at the "Behaviours" option yet, may be time to check it out. 

 

Is it something in your Global Setting - Per Snapshot > Per Preset > Global ?

 

The reason I ask is, while typing this, I just tried on the Helix floor (not HX Edit) and is only worked on that one specific preset, none of the others. Does It happen whatever Wah Model you're using or just one model?

 

I'm using Weeper wah.  So I briefly tried it on one such preset.  I have an exact copy of the preset, and whatever I did to the first preset, the second one also got the "toe down" setting or whatever.  Any other setting change like clearing a block does not get auto-saved, and does not propagate to other presets.

 

So since I don't know what the heck is going on, I'm not going to be using this setting for the time being.  I restored from my backup and everything is back to normal.  Don't want to have a fun adventure with wah not turning off / turning on when not needed on stage.

[lucilanga]

On 2/9/2022 at 5:48 PM, nkrcompany said:

I'm using a Helix rack, just updated to 3.15 firmware (and made a factory reset too).

I'm using a midi controller and regularly use MIDI CC51, CC52, CC53, or CC54 messages to emulate footswitch operation. Unfortunately Helix Rack does not respond as expected. 

I don't know what version made this bug, but it guess it was present since 3.0. That's sure this bug was present in the preceding 3.11

 

In HX Edit I linked Footswitch 3-7 to turn on/off individual effects. So on the bypass/controller assign panel I made four setup for the individual blocks, setting parameter to Bypass, and Source the Footswitch 3-7. Now, when I send these CCs to Helix Rack sometimes it doesn't respond, sometimes it makes a preset change instead of turning on/off the individual effect blocks. Earlier this worked great and without problems.

 

I really would like to use these footswitch CCs, can you please to help to resolve this issue?

 

I'm experiencing the same behavior on Helix Floor. Sending MIDI CC51, CC52 though CC58 will switch presets, which is obviously wrong according to manual. But what I find interesting it does that only when in preset mode (pressing FS6) when in stomp mode sending CC51,CC52..etc work as expected (eg. switching individual effects on/off). I guess I could leave Helix in Stomp mode all the time (preset changing works fine in stomp mode). One could argue that it kinda emulates what happens when you physically step on FS3,FS4 and Preset Mode is active, but the manual clearly states that CC49 to CC58 "Emulates Stomp footswitch mode's FS1->FS11"

[lucilanga]

All right. So, yeah, I went back downgrading the FW,  it seems they "broke" CC51, CC52 .. etc behavior in 3.10. But looking at 3.10 release info I found this:

 

Bank/Preset/Snapshot Up and Down messages how properly work via incoming FS1/FS7 emulation MIDI messages 

and

New MIDI message (Helix Floor/Rack/LT/HX Stomp XL): CC71 engages the MODE switch 

 

So I guess the behavior is intentional. I suspect Board/Floor/LT are in the same boat.

I wish they update the manual manual more often. Even on version F there is no mention of CC71, let alone the new 3.15 stuff CC77-81.

[scotterp]

OK - So  I have gone through the update process a couple of times and have reset things from my backup and I'm having one issue in particular.

 

I only have 2 presets where, within snapshots, some snapshots are using Variax settings, and others are using the built in pickups. For instance:

 

Snapshot 1 uses the spank setting #2, where snapshot #3 uses Variax mags, wherever the switch may be positioned. 

 

What I'm finding is that when I switch to snapshot #3 now, it maintains the spank setting. It used to turn off the Variax and just go to whatever the mags were currently positioned to. The Variax no longer turns off when I switch to a snapshot where it used to do that. 

 

Anyone else seeing this?

[datacommando]

10 minutes ago, scotterp said:

The Variax no longer turns off when I switch to a snapshot where it used to do that. 

 

Just a thought.

Have you checked your Global settings to make sure everything is as it should be?

 

 

[scotterp]

Good point. I did check. I'm thinking the one that would affect this is the Recall snapshot edits vs Discard Snaphot edits. It is set to Recall. I can't think of another that might affect this behavior. 

[HonestOpinion]

50 minutes ago, scotterp said:

OK - So  I have gone through the update process a couple of times and have reset things from my backup and I'm having one issue in particular.

 

I only have 2 presets where, within snapshots, some snapshots are using Variax settings, and others are using the built in pickups. For instance:

 

Snapshot 1 uses the spank setting #2, where snapshot #3 uses Variax mags, wherever the switch may be positioned. 

 

What I'm finding is that when I switch to snapshot #3 now, it maintains the spank setting. It used to turn off the Variax and just go to whatever the mags were currently positioned to. The Variax no longer turns off when I switch to a snapshot where it used to do that. 

 

Anyone else seeing this?

 

Go over to the second page of parameters on the Input block of any preset using a Variax input block and make sure 'Variax Settings'="Per Preset". Once you set it in one preset it will apply to all, that is actually a global setting located in a preset. Also, if, as @datacommando indicated, if the problem is in your global presets, make sure you did the factory reset and restore backup step recommended by Line6. If you use the backup that was made by the update process, it will restore all your global settings to their state prior to the update(as they should be).

[scotterp]

Variax settings is per preset. Factory reset was done (twice to be sure) and reset from backup each time. 

 

This seems to work fine for the initial snapshot when coming into a preset. But if there is a " secondary" snapshot where the Variax should be "turned off" and let the mags take over, this is where I'm having an issue. The Variax is not turned off. 

 

I can always change the snapshots to use another Variax setting, not a big deal, but the behavior does seem to be different than previous releases. 

 

This is the only issue I have found. 

[HonestOpinion]

21 hours ago, scotterp said:

Variax settings is per preset. Factory reset was done (twice to be sure) and reset from backup each time. 

 

This seems to work fine for the initial snapshot when coming into a preset. But if there is a " secondary" snapshot where the Variax should be "turned off" and let the mags take over, this is where I'm having an issue. The Variax is not turned off. 

 

I can always change the snapshots to use another Variax setting, not a big deal, but the behavior does seem to be different than previous releases. 

 

This is the only issue I have found. 

 

As far as I know you can't assign the Input block type to a snapshot. Are you using one of the snapshot strategies described in the two links below to switch between Variax and mag pups? Any chance you changed a setting on the Variax rather than the Helix?  Maybe one of the resident Variax gurus here can chime in.

 

 

How do I switch off the Variax model when changing to a different preset on Helix - Helix - Line 6 Community

[scotterp]

I think I will need to go back to 3.11 and capture exactly how it worked there, then come back to 3.15 and compare. Just to make sure I have my head straight. 

 

IIRC (and I'm not sure I do 100%) I could save a snapshot with the Variax enabled with a specific Variax setting. I could then change to another snapshot, disengage the Variax, save the preset and the disengagement of the Variax was saved for that snapshot only. Toggling between the two snapshots would engage/disengage the Variax. 

 

Now, if I save the preset with the Variax engaged, it saves that state for all of the snapshots. Same if I disengage it. It no longer saves the state of the Variax per snapshot. 

 

I hope this explains it?

 

It's been a while since I set these up and it just seemed to work that way. 

[silverhead]

The selection of mags or model is made  in the Input block. You select either Variax Magnetics or Variax (modeling). These are mutually exclusive. selections at the physical input level and are not  parameters in the sense that they can be assigned to the Snapshot controller.

 

I have presets that allow me to switch between mags and models using an expression pedal. I use a dual-path preset with Input 1 = Variax Magnetics and Input 2 = Variax. I include a Vol or Gain block in each path and assign them to the same pedal, e.g. EXP-1. I then assign the Min/Max values for each so that I can mute one path or the other, or blend both.

 

There are other ways such as using a switch to toggle the pedal values to 0 and 100, oppositely, at each press of the switch. These parameter changes can be  assigned to Snapshots if you wish. But you can't use Snapshots to change a Variax Magnetics Input setting to a Variax model.

[scotterp]

I have done the dual path as well and toggling output volumes for different snapshots. 

 

I have a gig this Friday and don't want to mess around too much until that is done with. Then I will reinstall 3.11 and see exactly what it did before. I know that it is working differently now than it did before. I just want to prove that I'm not going crazy and misremembering something. :)

Thanks guys!

[nkrcompany]

On 2/13/2022 at 7:51 PM, lucilanga said:

All right. So, yeah, I went back downgrading the FW,  it seems they "broke" CC51, CC52 .. etc behavior in 3.10. But looking at 3.10 release info I found this:

 

Bank/Preset/Snapshot Up and Down messages how properly work via incoming FS1/FS7 emulation MIDI messages 

and

New MIDI message (Helix Floor/Rack/LT/HX Stomp XL): CC71 engages the MODE switch 

 

So I guess the behavior is intentional. I suspect Board/Floor/LT are in the same boat.

I wish they update the manual manual more often. Even on version F there is no mention of CC71, let alone the new 3.15 stuff CC77-81.

 

Thanks, I'll check CC71 operation with my Helix Rack. Yeah, it would be great to get updated midi manual with version updates.

[lucilanga]

Below is the list of the new CCs I could find so far:

 

CC71    - mode switch
CC72 value 64-127 = next preset, value 0-63 = previous preset
CC73 toggles between Play and Edit views
CC74    - save preset
CC75    - knob1
CC76    - knob2
CC77    - knob3
CC78    - knob4
CC79    - knob5
CC80    - knob6
CC81    - buttons "< page" - "page >"

 

I wasn't able to find what CC70 does. I do not think it is mentioned anywhere. Perhaps somebody here knows?

I even threw random values using CC70 but I wasn't able to tell if it does do anything.

I'm sure it must be used for something, I doubt they let one CC empty before user CCs

[nkrcompany]

On 2/13/2022 at 7:51 PM, lucilanga said:

All right. So, yeah, I went back downgrading the FW,  it seems they "broke" CC51, CC52 .. etc behavior in 3.10. But looking at 3.10 release info I found this:

 

Bank/Preset/Snapshot Up and Down messages how properly work via incoming FS1/FS7 emulation MIDI messages 

and

New MIDI message (Helix Floor/Rack/LT/HX Stomp XL): CC71 engages the MODE switch 

 

So I guess the behavior is intentional. I suspect Board/Floor/LT are in the same boat.

I wish they update the manual manual more often. Even on version F there is no mention of CC71, let alone the new 3.15 stuff CC77-81.

I just tried using CC71 with my Helix Rack. I would like to report that my problem has been solved.

After sending a CC71 with value 0, I can send CC49-58 to control footswitches bypass state.

However CC71 values are completely missing from Helix manual, so here it is (from HX Stomp manual):

CC71
Values: 0-5
Footswitch Mode (0=Stomp, 1=Scroll, 2=Preset, 3=Snapshot, 4=Next footswitch mode, 5=Previous footswitch mode)

[SaschaFranck]

3.15 is really getting on my **** already. I'm getting "Timeout waiting for a response from device" messages pretty regularly from HX Edit - and once that happens, the Helix itself will freeze in as well, just a reboot will help. I can often only "hard kill" HX Edit as well, CMD+Q in 50% of all cases doesn't do anything. Sometimes rebooting just the Helix fixes this, sometimes I need to restart my computer.

The Timeout message has got to be kind of a joke, too - because even when the message is displayed, the Helix continues to work as an audio interface.

Getting this around 2-3 times a day, depending on how long I'm using my stuff. Highly annoying.

 

[nateandersona]

I've had this issue as well almost immediately after downloading the new update.  Sometimes Hx edit will work but nothing can be operated on the unit itself.  Everything looks normal on the unit but no sound and can't press any buttons.  The only thing that works is the blinking tap tempo light indicator.  

[jamkid]

Hardware: HX Stomp
Firmware/Editor: Firmware 3.15

Bug:  CC71 (engages the MODE switch) does not work after the update to 3.15

 

Have tried sending the CC command using multiple midi controllers. All the other commands are working fine, but CC71 does not do anything.

[molul]

The new "change snapshot" command seems to have a problem. 

 

I have a setlist with 10 songs programmed with the new "change snapshot" command. This works alright.

 

Now, I exported that setlist and imported it onto another setlist (I want to have a clone for tweaking stuff while having the original intact), and on that new imported setlist the "change snapshot" command doesn't work 100%. When I press a FS to change to another snapshot, it does change (I can see it in the top right corner) but it doesn't update the screen with what the footswitches are supposed to do.

 

Has anyone experienced this?

 

[kroqs]

On 2/10/2022 at 8:42 PM, Phillip1 said:

just updated to 3.15 and now my external footswitches FS7/FS8 (which were assigned to scroll up and down through my 4 snapshots) went all schizo on me.

 

it now skips randomly between the 4 snapshots rather than cycling up or down sequentially.

 

for example if i'm on snapshot 1 and i press the "up" footswitch once it won't go to 2, it'll go to 3 or maybe 4 etc.

 

it's almost as if it registers a single press as a double press.

 

anyone know what's going on?

 

I,ve got exactly the same problem and had to downgrade back to 3.11. Any known solution to fix this?

[HonestOpinion]

2 hours ago, molul said:

The new "change snapshot" command seems to have a problem. 

 

I have a setlist with 10 songs programmed with the new "change snapshot" command. This works alright.

 

Now, I exported that setlist and imported it onto another setlist (I want to have a clone for tweaking stuff while having the original intact), and on that new imported setlist the "change snapshot" command doesn't work 100%. When I press a FS to change to another snapshot, it does change (I can see it in the top right corner) but it doesn't update the screen with what the footswitches are supposed to do.

 

Has anyone experienced this?

 

 

Don't know if it still applies but in previous versions of the firmware doing something like copy/paste or I suppose import of an entire setlist would trigger a preset rebuild upon the next restart of the device. Have you tried restarting the device after importing the setlist? Also, you may also have already done this, but the usual advice regarding the update instructions to do a factory reset and restore after update also applies. 

[molul]

38 minutes ago, HonestOpinion said:

 

Don't know if it still applies but in previous versions of the firmware doing something like copy/paste or I suppose import of an entire setlist would trigger a preset rebuild upon the next restart of the device. Have you tried restarting the device after importing the setlist? Also, you may also have already done this, but the usual advice regarding the update instructions to do a factory reset and restore after update also applies. 

Thanks. Yes, I did the backup->update->factory reset->restore->turn off and on again to rebuild the 1024 presets.

 

Then I programmed all those "change snapshot" commands, exported the setlist, imported on another setlist, and it didn't work fine there (it was still working fine in the original one).

 

A strange thing I noticed is that after importing the setlist, when I turned the Helix LT off and on again, the rebuild presets process occurred again. Not sure if it's something normal after importing setlists, as I hadn't done it yet.

 

 

[HonestOpinion]

5 hours ago, molul said:

Thanks. Yes, I did the backup->update->factory reset->restore->turn off and on again to rebuild the 1024 presets.

 

Then I programmed all those "change snapshot" commands, exported the setlist, imported on another setlist, and it didn't work fine there (it was still working fine in the original one).

 

A strange thing I noticed is that after importing the setlist, when I turned the Helix LT off and on again, the rebuild presets process occurred again. Not sure if it's something normal after importing setlists, as I hadn't done it yet.

 

 

 

Yep, that rebuild upon restart after you copied/imported the setlist was exactly what I was referring to. As I mentioned this has been something we have observed in past firmware versions. Have you noticed any change (hopefully positive) in the snapshot behavior since you restarted, and the presets rebuilt?

 

In the past, due to this rebuild process (on presets that have been newly copied or imported), the prevailing wisdom has been that it is not a bad idea or perhaps a best practice to do a restart before beginning to edit or play with the copied presets, PITA though it may be. This may be more pertinent with more complex or sophisticated preset usage. Have never seen any confirmation as to this from Line 6, so perhaps it is unnecessary, but it just seems generally like a good idea to allow this secondary rebuild process to complete via a restart before forging ahead. This is outside and apart from the standard rebuild that occurs after a backup restore, for example after a firmware update. Btw, you will also I believe always see this one-time additional rebuild (upon restart) if you import a preset created with a prior firmware version from, for example, CustomTone, or a purchased preset pack.

 

The efficacy of these recommendations, hinges to some extent on you not having stumbled across a legitimate bug in the latest firmware.