Snapshots don’t honor volume pedal position…

[dandesy]

This is probably really simple, but in a preset (all my presets) I have a volume block assigned to the pedal somewhere after the amp.  In stadium, when I change to a snapshot for the first time, even though the volume pedal is all the way up, there is no sound.  Until I move the pedal anyways, then it tracks it.

 

I have a feeling I went through this on my OG helix, 8 years ago, but can’t find a setting for it.

 

anyone?

[Nos402]

On 11/20/2025 at 9:34 PM, dandesy said:

This is probably really simple, but in a preset (all my presets) I have a volume block assigned to the pedal somewhere after the amp.  In stadium, when I change to a snapshot for the first time, even though the volume pedal is all the way up, there is no sound.  Until I move the pedal anyways, then it tracks it.

 

I have a feeling I went through this on my OG helix, 8 years ago, but can’t find a setting for it.

 

anyone?

I can't swear to this but I believe this has happened to me if I turned the volume pedal down then saved the preset. On my old Helix it would save the position of the volume when you saved the preset.

[dandesy]

These are all presets that wiorked on Helix, imported into Helix Stadium.

[silverhead]

Check the Global Settings. There’s one that controls how pedal position is managed.

[dandesy]

Thanks.  I did set the expression settings to global.  No dice…

[decreebass]

Seems to be a snapshot bug. Snaps don't honor (all) edits made in Focus View, either. I just made a topic on that, but I thought I'd come in and validate your concerns. Maybe Line 6 will see this and dig in.

[silverhead]

Make sure you are aware of the Snapshot Discard Edits On/Off settings, and its potential role in what you may be considering a bug. It’s possible that the edits you think are not being honoured are in fact following your instruction to discard them.

[aparedes]

Not sure if something changed on the backend, but you could use the "press/turn" method in the inspector window to assign this value as a snapshot, then change the different values for each snapshot on the volume position (Encoder 1). 

[jemenake]

I just posted on Reddit about this issue. As background, I have about 100 presets on my Helix Floor where I saved them all with the volume rocked all the way back (so that I didn't get blasted if I forgot to turn my guitar volume knob down when switching presets). This way, I select a new preset, then make sure my strings are muted or guitar volume is down, and then I rock the volume pedal.

 

With these presets imported to the Stadium, switching to the preset leaves the volume at what it was, switching to another snapshot leaves it up, and then switching back to the initial snapshot sets the volume to zero.

 

This seems to have happened with the global setting for the pedal set to Global or Preset. I'll have to see if there are some more global settings about this because, now that I think about it, it's the Helix's treatment of the volume level that seems idiosyncratic; if the volume were being treated exactly like all other effect parameters, I'd expect that the snapshot would record any values that are changed after switching to it. It's only because pedal volume is something we usually expect to not change across snapshots... I wonder if it is given special treatment by the Helix.

[mattsteeves]

I am having a similar issue where the snapshots won't honor EXP 1 or EXP 2 selected when saving. For example I want all snapshots to start with EXP 1 but some of them just wont save that way.

[dandesy]

I opened a ticket and was told they couldn’t reproduce the issue… obviously, you guys can!

[silverhead]

On 11/27/2025 at 11:44 AM, jemenake said:

I just posted on Reddit about this issue....

 

On 11/28/2025 at 9:16 PM, mattsteeves said:

I am having a similar issue ....

 

On 11/29/2025 at 12:16 AM, dandesy said:

I opened a ticket and was told they couldn’t reproduce the issue… 

@jemenake, @mattsteeves  Perhaps if you also opened a support ticket Line 6 would take another look.

[mattsteeves]

I've found a pattern to this bug.

 

• Say I want the expression pedal to default to EXP 1 for all snapshots within a preset. This is how I built them in my Helix Floor.

• The preset, now in Stadium XL, selects random loading EXP 1 or EXP 2 for each snapshot. 

• When I go to fix this is when the problem arrises, and the pattern emerges...

 

• I will turn off "discard edits" and set the expression pedal to EXP 1 for a snapshot. I go to each snapshot and select EXP 1. Everything appears to be working at this point.

• When I SAVE the preset is where the problem emerges. Depending on the current snapshot that is selected when I save, that snapshot reverts to EXP 2 while the others are correctly defaulting to EXP 1. If I choose a different snapshot that is correctly defaulting to EXP 1 and then save the preset again, THAT snapshot will now default to EXP 2 and the others will remain correct. This behavior is able to be replicated every time for every preset.

 

• The only workaround I have now isn't ideal, which is to find a snapshot within that preset that I know I wont need instant access to my EXP 1 and save the preset with that snapshot selected, so the other snapshots may live their life normally. In other words, one snapshot must sacrifice its correct default settings for the others to be correct.

 

Additionally, and somewhat of a separate issue but is consistent across the board for me...

Presets that were built in my Helix Floor and transferred to Stadium will change the bypass controller assignment to be "backwards". For example, most of my presets I like to have the wah activated not by a toe press, but by just rocking the pedal back during use and returning it to the down position to deactivate. In the Helix Floor, this behavior is programmed by having the "Bypass" assignment set to position 99% with behavior set to "toggle".

 

Now, all of the presets I had set up this way and transferred to Stadium will default that switch behavior to "toe down" and to 1%. This setting results in the wah activating when the pedal is all the way heel down, and ONLY heel down. If the pedal is moved anywhere else the block is deactivated. I've had to change each preset to behave correctly, and that is really a pain.

 

That, coupled with the inability to correctly set the default EXP 1 or 2 setting upon preset load is independent of the global setting for expression pedal position set to either "global" or "preset". The issue is also independent of the snapshot discard edits set to on or off. Can anyone else replicate this?

[PMJNugent]

On 11/21/2025 at 3:34 AM, dandesy said:

This is probably really simple, but in a preset (all my presets) I have a volume block assigned to the pedal somewhere after the amp.  In stadium, when I change to a snapshot for the first time, even though the volume pedal is all the way up, there is no sound.  Until I move the pedal anyways, then it tracks it.

 

I have a feeling I went through this on my OG helix, 8 years ago, but can’t find a setting for it.

 

anyone?

Aha …. I think I’ve sussed this out (I only just noticed this glitch).  It seems that when importing a preset the volume pedal doesn’t copy over properly.  
Try clearing the volume block and then adding it back in!  Bit of a nuisance but worked for me. 

Let me know if it works for you 

[gbr13697]

Something to bear in mind is that, when presets were imported from Helix Floor to Stadium on Firmware 1.1, snapshot control assignments were added to anything that had expression pedal control assignments. So where something was assigned to expression pedal control in Helix Floor, in Stadium it will have snapshot control AND expression control. It took me hours to clear up to 24 unwanted snapshot control assignments from about 50 imported presets. Even then I am still having glitches where the block fails to respond to the expression pedal, even though the assignment is on and the Max/Min settings are visible on the parameters, often for expression control of several parameters in a single block.

I have cured most of these by clearing the expression control from one of the parameters, and then reassigning it. This will revive all the expression pedal control assignments in the block, even though I only removed and restored the assignment for one parameter.

However, I have had instances where I have had to delete and recreate the block altogether as mentioned by PMJNugent above. Copying and pasting blocks also fails to include assignments.

I suspect that, when an imported preset already had both snapshot and expression control assigned to a block, the corruption on import to Stadium would cause all sorts of problems. Combine this with the inconsistency when saving snapshots and presets with particular assignments to both EXP1 and EXP2 in different pedal positions, plus the various Global Settings that can have effects, and it all turns into a nightmare.

There are so many variables in this that the possibilities of being able to reproduce particular scenarios for Line 6 Support are very remote.