Snapshot recall and discard mode

[Aenglish88]

Have been using Helix LT for many years, never noticed until a few weeks ago at church that my snapshots were all messed up. Had huge gain issues, pedals were on that shouldn't be and drive was cranked for some reason on my patch. Now I noticed Snapshot Discard mode no longer works as I thought it did, it only affects a bypass state, not a set parameter across all snapshots.

 

I don't remember it working like this, has it always functioned ONLY on a bypass state? I thought ANY changes made at all across the entire snapshot would be lost if I have it on Discard.

 

Need to make sure I use tape or something to prevent any buttons and knobs from being touched if this is indeed true, almost had a messed up patch before worship starting Sunday. Had to remember my settings real fast to make it usable.

 

EDIT: I just replicated the issue again, it changed Drive parameter across entire preset and all snapshots from 4.0 to 6.0, my clean trem snapshot went big drive just from changing snapshots from one clean preset to my rhythm preset. It changed the Drive parameter (not a bypass) across ENTIRE preset. 3rd time I have had to manually reset multiple bypassed and non bypassed parameters run the last 30 minutes on my preset. Never had this issue before, been using same patch for a while now. SO far the helix has been very consistent. 

 

I need this functional tomorrow morning, am I seeing why digital modelers with software may be unreliable? hopefully not been happy with helix for years now, but absolute need this t o operate as intended every time I use it....

Edited September 7 by Aenglish88

[silverhead]

With Snapshot Edits -> Discard any change you make to a snapshot will be discarded if you switch to another snapshot without saving the preset. With Snapshot Edits -> Recall any change you make to a snapshot will be retained if you switch to another snapshot; you don’t need to save the preset until you are finished edits to all snapshots. This behaviour hasn’t changed, and yes, it affects parameter changes as well as block bypass states.

[datacommando]

On 9/8/2024 at 12:43 AM, Aenglish88 said:

I need this functional tomorrow morning, am I seeing why digital modelers with software may be unreliable?

It has been my experience that the “unreliability” of these devices is generally the product of “human error” that is introduced by the user.

 

Check the Helix 3.0 Owner’s Manual > page 48 > Determining Snapshot Edit Behavior.

Also, page 64 - Global Settings > Preferences

Link:

https://line6.com/data/6/0a00050b287e6643b71cda93a/application/pdf/Helix 3.0 Owner's Manual - English .pdf

 

Hope this helps/makes sense.

 

[SaschaFranck]

On 9/8/2024 at 1:43 AM, Aenglish88 said:

EDIT: I just replicated the issue again, it changed Drive parameter across entire preset and all snapshots from 4.0 to 6.0, my clean trem snapshot went big drive just from changing snapshots from one clean preset to my rhythm preset.

 

Is the parameter value displayed in white?

[theElevators]

In terms of preventing yourself from messing up your presets, I have a nice video with all the best practices I've been able to find.  For example, put the cursor in the corner, so the knobs are not going to change any setting. Otherwise, you can easily press on those knobs and create/change bypass behavior. 

 

 

 

I'm curious about the exact steps to replicate this!  If you are saying the gain settings are all weird, could it be that you accidentally removed the snapshot assignment?  And simply changed the settings of your gain block, so all snapshots would get the same value? 

 

I just updated my Helixes to the latest firmware because I needed one specific reverb for one of the songs, which turns out we are not even playing :)  Prior to that I've been on 3.11 for several years without an issue you describe. 

[codamedia]

On 9/7/2024 at 6:43 PM, Aenglish88 said:

I just replicated the issue again, it changed Drive parameter across entire preset and all snapshots from 4.0 to 6.0, my clean trem snapshot went big drive just from changing snapshots from one clean preset to my rhythm preset. It changed the Drive parameter (not a bypass) across ENTIRE preset.

 

That is exactly how it would operate if you didn't ASSIGN the parameter to snapshot control. By default, nothing is controlled by snapshots other than the on/off state of the block.

• If you want a parameter to be controlled by snapshots, you need to assign it as such - then set it accordingly from snapshot to snapshot.
• If you want the on/off state of a block to be ignored by snapshots, you need to assign it as such