Snapshots do not remember bypass state

[eriksan007]

Why is it that some blocks do not come back to their set bypass state, after toggling from and back to that snapshot? For example, as in the attached video, in snapshot 1 I turn off wah, go to snapshot 2, then back to 1 and the wah is on. The wah is set to “Snapshot Bypass”. 

[lou-kash]

On 2/26/2024 at 11:11 AM, eriksan007 said:

The wah is set to “Snapshot Bypass”. 

 

Slightly confusingly, if "Snapshot Bypass" has a check mark, then it will remember its saved snaphot state.
To be completely "snapshot agnostic", the check mark needs to be off.
Also remember to save the preset to library before switching to another one.

[eriksan007]

On 2/26/2024 at 1:33 PM, lou-kash said:

 

Slightly confusingly, if "Snapshot Bypass" has a check mark, then it will remember its saved snaphot state.
To be completely "snapshot agnostic", the check mark needs to be off.
Also remember to save the preset to library before switching to another one.

Thanks and yes, the check mark is next to “Snapshot Bypass”. Unfortunately, it did not work. In snapshot 2 I turn off wah, save to library, then go to snapshot 1, then back to snapshot 2 and the wah is on again!

[PaulTBaker]

you may want to check the snapshot setting on the global page (?) that determines the behavior of the snapshot when returning to it.  I can't remember the names, but one is recall and the other is ???.  one of them will return to the settings of when the snapshot was saved.

 

It could be that you had your wah on when you saved it.  Then with the specific setting chosen, returning to the snapshot will turn the wah on (because that's how it was saved).

 

As others say (which I mildly hate), read the manual for the correct settings.  look some where in the global settings for snapshots.

 

good luck

[lou-kash]

On 2/26/2024 at 6:37 PM, PaulTBaker said:

you may want to check the snapshot setting on the global page (?) that determines the behavior of the snapshot when returning to it.  I can't remember the names, but one is recall and the other is ???.  one of them will return to the settings of when the snapshot was saved.

 

From the Helix Native Pilot's Guide:

 

Quote

Bypass Assignments

A common practice within Helix devices is to configure “bypass assignments” where the bypass parameter of blocks is then toggled Off/On via the device’s footswitches, or optionally by expression pedals or external MIDI commands. Currently, MIDI bypass assignments are supported in Helix Native (see next section), but not other types of bypass assignments that can be created within Helix hardware. If you happen to change the bypass state of the block that includes a Helix hardware bypass assignment and export the preset, you will overwrite the saved state of the assignment when the preset is imported back into a Helix device.

Also, note that when a preset is loaded while Helix Native is currently in a different HC mode from which the preset was created, bypass assignments for footswitches and con- trollers that don’t exist within the device HC mode are discarded when the preset is translated.

Controller Assignments

Helix device users can create “controller assignments” to map the control of parameters (such as a wah or volume, a delay’s Mix parameter, etc.) to a Helix expression pedal, footswitch, or external MIDI controller device. Currently, MIDI In controller assignments are supported in Helix Native plugin (see next section), but not other types of controller assignments that can be created within Helix hardware.* If you edit a parameter that includes a Helix hardware controller assignment and then export the preset from Helix Native, your last-used parameter value is the same value the parameter will default to upon import within a Helix device.

*NOTE: When importing a preset into Helix Native, which includes HX Edit-saved hardware controller assignments, you’ll see the assigned parameter sliders within Helix Native display their values in white brackets indicating the assignments. Even though these hardware con- troller assignments are not supported within Helix Native, they are preserved with the preset (as well as with the respective, individual blocks for copy/paste). Therefore, these assign- ments will still be intact if you import the preset back into HX Edit.

NOTE: Helix and HX devices' exported presets include a global Snapshot Control option where hardware controller assigned parameters can also be enabled or disabled for control via Snapshots. Helix Native does not offer this option but will preserve the presets' hardware settings upon import and export. Please see the HX Edit Pilot's Guide for details.

[eriksan007]

On 2/26/2024 at 9:54 PM, lou-kash said:

 

From the Helix Native Pilot's Guide:

 

I have the guide, but it’s not helpful in this case. I know how to configure bypass assignments and controller assignments. The issue is that certain blocks don’t remember their bypass states between snapshots. Updated youtube video.

(I’m not sure how this applies: “Helix and HX devices' exported presets include a global Snapshot Control option where hardware controller assigned parameters can also be enabled or disabled for control via Snapshots. Helix Native does not offer this option but will preserve the presets' hardware settings upon import and export.”)

[eriksan007]

On 2/26/2024 at 6:37 PM, PaulTBaker said:

you may want to check the snapshot setting on the global page (?) that determines the behavior of the snapshot when returning to it.  I can't remember the names, but one is recall and the other is ???.  one of them will return to the settings of when the snapshot was saved.

 

It could be that you had your wah on when you saved it.  Then with the specific setting chosen, returning to the snapshot will turn the wah on (because that's how it was saved).

 

As others say (which I mildly hate), read the manual for the correct settings.  look some where in the global settings for snapshots.

 

good luck

Thanks but there does not appear to be a global snapshot setting page in Helix Native. With regards to “saving the snapshot”, I assume it’s just a matter of selecting the snapshot and turning off the wah, and saving the preset to library? I have tried that.

[PaulTBaker]

Sorry, did not see this was for Native.  On Floor (which I know may not help you) the options are Discard and Recall.  Setting it to Recall, brings back the original settings when saved.  Discard brings back the settings from the last time the snapshot was used.

[aetguitars]

Set the "Current Hardware Compatibility Mode" to "Off".

[gastric]

This occurs every time when with blocks added from the FAVORITES category. Snapshots never retain the correct bypass state in Native for the blocks added via FAVORITES.

[datacommando]

On 11/29/2025 at 2:34 PM, gastric said:

This occurs every time when with blocks added from the FAVORITES category. Snapshots never retain the correct bypass state in Native for the blocks added via FAVORITES.

Hi,

 

Looking at the Helix Native Pilot’s Guide 3.80, it would appear that the function of Favorites is to simply save “Blocks” which retain any of the values you dial in as a “favourite” starting point for that particular block, You want save a delay block with settings that are different from the factory preset - for example you want a delay time 500ms with a feedback setting of 70%. Add that to a Preset and it retains the values you set.

 

Again, by reading the user manual it does mention that Snapshots, are applied to blocks that exist within the “Preset”.

 

”Within Helix Native plugin, it is possible to create & customize up to eight “snapshots” within a preset.* Snapshots can store a set of options (a block’s bypass state, snapshot-assigned parameter values, and tempo settings), and then recall them without the brief lag time and audible signal drop-out typically associated with changing presets.”

 

Then, later on page 39, there is this note.

 

”NOTE: All snapshots assignments and settings are retained within the current tone’s preset until another preset is loaded within the plugin. If you wish to retain all your snapshot assignments and settings with the preset permanently, be sure to use the File menu options to Save your tone to the Presets Library or Disk. The snapshot that is in use when you save your preset is the one that is recalled when the preset is loaded again.”

 

As you can see from these quotes - Snapshots and their parameter values are applied to selected “Blocks” and are actually part of a “Preset”, not the “Favourite”.

 

Hope this helps/makes sense.