Bug Report: Snapshot settings not applied correctly in Snapshots

[bbehrens]

I have a Preset with 8 Snapshots. Snapshot 4 has an Heir Apparent turned on, while Snapshot 5 has a Kinky Boost, Heir Apparent, and Prize Drive turned on.

When the Preset is loaded Snapshot 1 is correct.

When Snapshot 2 is loaded, it is also correct.

When Snapshot 3 is loaded, it is also correct.

When Snapshot 4 is loaded, the Heir Apparent is not turned on in Stadium App or on the Stadium Unit (It should be on).

When Snapshot 5 is loaded, the Kinky Boost, Heir Apparent, and the Prize Drive are all off (They should be on).

Heir Apparent is turned on in Snapshot 4 and the preset is saved on the Helix Unit.

When Snapshot 5 is loaded, the Heir Apparent is on (This is an apparent carry-over from Snapshot 4).

The Kinky Boost and the Prize Drive are also turned on via the Helix Unit and the preset is saved again.

When Snapshot 4 is loaded, all 3 three Distortion blocks are now on in both the App and the Unit (An apparent carry-over from Snapshot 5).

When Snapshot 3 is loaded, all 3 distortion blocks are off, which is correct.

When Snapshot 4 is loaded, all 3 Distortion blocks are still off (An apparent carry over from Snapshot 3), However, the Stadium App now shows that the Heir Apparent block is turned on (conflicting with what the Helix Unit is showing).

When Snapshot 5 is loaded, all 3 distortion blocks are still off in the Helix Unit. However, the Stadium App shows all 3 turned on.

 

Factory Reset of the Unit, and Importing and Exporting the Snapshot will not resolve this issue. When the Snapshot is reloaded, this issue is reproducible.

 

Bug Report has been filed with Line 6.com

[bverdon]

Appreciate the post... and that you opened a ticket with support. I have had a few issues with snapshots but when I started from scratch and rebuilt the preset, the issue was resolved. If I re-imported the old troublesome preset...the issue is there. Not sure if that helps for a workaround. 

[bbehrens]

 

On 12/29/2025 at 4:47 AM, bverdon said:

Appreciate the post... and that you opened a ticket with support. I have had a few issues with snapshots but when I started from scratch and rebuilt the preset, the issue was resolved. If I re-imported the old troublesome preset...the issue is there. Not sure if that helps for a workaround. 

 

Yes, I rebuilt the Preset from scratch and it worked as expected. Saving and re-loading the original problematic Snapshot did not correct the issue as it continued to persist.

 

Interestingly, while re-building the preset, when I moved a few of the blocks to a parallel path (From Path B to Path B1 and B2, I ran out of DSP and could add no further blocks. So I discarded the edits and added the other blocks first and then moved the blocks that I wanted to the parallel paths and it worked fine. And I could no longer produce the DSP issue. It should be noted that I was operating very close to maxing out the Max DSP (whatever/wherever that is).

 

I am very interested in the DSP values as I have my own spreadsheet for the OG Helix where I have DSP values for every block in the OG Helix down to hundredths of a percentage and is very accurate. I don't think that any DSP values like this will happen any time soon for the Stadium as Line 6 takes some time so stabilize the DSP allocations on the OG Helix. Some of the 3.8.0 new blocks have the same MONO and STEREO DSP values and the MONO version were always optimized prior to 3.8.0. I think that they went off to do other things (Obviously). There is also the possibility that some DSP blocks may be more variable than the OG Helix was due to the new Agoura Amp models (though I think that it would be limited to the Amp/Cabinet combination and not the OG helix effects models and Legacy Amps.

[silverhead]

I’m wondering if this is related just to the editor/app. Are Snapshot changes consistently working properly if you just use the device, not the editor, to create and modify the Snapshots? Seems to be the case for @bverfon. Is it true for others?

 

I expect this won’t help with importing presets from OG Helix but it may give the developers more insight to identify and fix any related bugs.

[bbehrens]

Just compared the file contents of the original (problematic) file with the second one I recreated from scratch and noticed that the snapshot settings for all of the blocks is populated with null after the first three Snapshots (which work correctly), instead of true or false as opposed to the Preset that is working properly. I did create the preset with the Stadium App (as that is still my preferred method) so I can not report whether it was the App or Stadium XL that created the problem. But once the preset is created with these null values then I think that it can not be corrected unless you edit the file (perilous and error-prone at best) or just re-create the Preset from scratch as @bverdon suggested. Either way, it is definitely a bug.

 

For further clarification: Original (problematic) Preset: the "snapshots" element is each block records "false, false, false, null, null, null, null, null"

The re-created Preset: the "snapshots" element is each block records "false, false, false, true, false, false, false, false"

 

I typically expect true/false to be binary unless there is another purpose being used for the value.

 

This would lead me to believe that those blocks are not being set properly and may either be turned on or off depending on the last snapshot loaded (or another internal array).

[mike-w]

I'm not sure if this is the exact answer, but I ran into something like this.  Blocks weren't being turned on or off when changing Snapshots on a Preset I created.  I tend to edit on the HSXL I've found the current editor version a bit buggy, and the HSXL is so easy to work on.

 

On the HSXL, if you touch the Block you want to control, at the bottom of the Action Menu, there is a Snapshot Bypass switch. Switch that to On.

 

From the Manual:

Adjust the preset by doing one or more of the following:

• Turn one or more effects on or off by pressing stomp mode footswitches or tapping their bypass icon

  
  . Snapshots remember every block’s on/off state

   

  • You can disable this behavior per block: Tap the selected block to open the Action Panel, then tap the Snapshot Bypass toggle OFF. When off, the block’s bypass state won’t change when switching snapshots.

[bbehrens]

Thanks Mike. This functionality was present on the OG Helix. Unfortunately, the blocks were all created equal but act differently. Not sure what magic combination of button pushes did that but the footswitch bypass was not one of them (pretty sure unless it is easy to change without intending to). I have a hunch that the Stadium App is a little buggy under the covers. But if the code is much different than the code in the presets on the Unit then we will be chasing twice as many bugs through the system. Even worse if they ever get a Stadium Native interface going for DAW's. But that has not been Line 6's approach. They unified their development process back as of 3.0 (I think) of the OG Helix. And the OG Helix has been, and is still, solid.

 

I don't know when I will be able to use this new (more expensive) Stadium thingy. I don't run it like it was a plain vanilla pedal board.