Snapshot blocks not updating correctly when switching in reverse order

[Pechlivanos]

Hi everyone,
 

I’m having an issue with snapshot changes in some of my Helix presets and I’m not sure whether this is a bug or a setting I’m missing.

Here’s the behavior: When I switch snapshots in ascending order (Snapshot 1 → 2 → 3 → 4), everything works exactly as programmed. However, when I go in reverse order, the behavior breaks. For example, if I switch from Snapshot 3 back to Snapshot 2, a drive block that should be turned off stays active.

What’s odd is that if I then switch from Snapshot 2 back to Snapshot 1, and after that again from Snapshot 1 to Snapshot 2, the drive block deactivates correctly as programmed. So: Forward order: works fine. Reverse order: block state doesn’t update correctly. Going “around” via Snapshot 1 resets it and works again.
 

Is this a known issue? Is there a snapshot-related setting or concept I might be overlooking? If this has already been discussed or solved elsewhere, apologies for the duplicate question. I’d really appreciate any pointers or explanations.

Thanks in advance.

Panagiotis

[silverhead]

This is probably a known issue. Several bugs with Snapshots have been identified and will be fixed in a future update. I suggest you get along as best you can until then and revisit this after the update.

[bbehrens]

Is this a preset imported from an OG Helix, built using the Stadium App, or built from the ground up only on the Stadium Unit itself. Imported OG Helix presets are prone to a variety of issues, the Stadium App is not much better, and there are still occasional issues building only on the Stadium unit itself (I have seen with parameter assignments) - BUT, it is still the most reliable option.

[jpdennis]

I have noticed that there are times I have a FX that won't respond to on/off state changes between snapshots.  I found that if I copy the problematic FX block then delete it and immediately paste it back in I can control it with the snapshots just fine.  Not sure why.

 

That being said I am waiting for the next FW update to see which of the reported issues I have experienced are fixed.

 

jpd

[JakeHodges]

OMG, great tip, JPD.  Thank you.  Super maddening bug.  I have a really elaborate preset I've been working on all day, and after I deleted some blocks and re-mapped some Stomps none of my (dozen or so) remaining blocks (that I didn't touch) respect snapshot bypass anymore.  Copy-Clear-Paste each block seems to get it back, but then I need to remap all 8 snapshot and dozen or more blocks.  Very much looking forward to 1.2.1.

[jpdennis]

On 1/18/2026 at 5:26 PM, JakeHodges said:

OMG, great tip, JPD.  Thank you.  Super maddening bug.  I have a really elaborate preset I've been working on all day, and after I deleted some blocks and re-mapped some Stomps none of my (dozen or so) remaining blocks (that I didn't touch) respect snapshot bypass anymore.  Copy-Clear-Paste each block seems to get it back, but then I need to remap all 8 snapshot and dozen or more blocks.  Very much looking forward to 1.2.1.

 

JakeHodges,

 

You are welcome.  This workaround came from my 10 years working with the Helix Floor.  I am not sure if there is some DSP issue based upon fx block placement as well as the "at what point" I placed the block in the path that was never resolved.  I could not exactly replicate the issue when I needed to.  But when it does happen that is my solution.  Maybe others can chime in and add what they have done in this case.

 

just plain dennis (no one important) ;-)

 

[silverhead]

The firmware update released today claims to have fixed many bugs with Snapshots. Anyone tested it yet?

[Cerrucho]

Yes! So far so good. No issues yet.