silverhead

So... are you saying that the extended warranty isn't BS after all? That the title of this thread is misleading?

Unlike Snapshots on the Helix device, you don't need to do anything to activate/save them. There is no equivalent to the Snapshot Controller and no Recall/Discard snapshot changes switch. All Snapshots are always active - just make your changes and they are recalled/saved automatically. Every Snapshot will be in the state you left it when you return to it.

Great! Are we having fun yet?

Please explain what you mean by 'no change'. What are you expecting and not seeing?

Yay!!! This is what I was looking forward to with the release of v2.50. I know you did this just for me!, you angel you.

Presets from older firmware versions are not rebuilt when they are imported. They are rebuilt during the next startup. I agree with HonestOpinion - after importing a few setlists post-firmware update it is good practice to restart Helix and force an immediate rebuild before doing a lot of editing. Just good practice, not necessarily necessary. 😉🤓

Contact Line 6 support (see Contact Us link at the bottom of this page).

Some presets are potentially rebuilt at every startup. Helix will rebuild any preset that was built in a previous firmware version and imported during the previous session. The rebuild you saw this morning indicates that yesterday you restored some saved presets when Helix was last operating.

Leave the physical Tuning knob on your guitar set to Standard. In each Helix preset set the Variax Tuning parameter to Custom (not Don't Force) and define the 'Custom' tuning that you want for each preset. For standard tuning define all string offsets = 0. The only time you would set the Tuning knob on your Variax to Custom is when you have used Workbench to define a custom tuning that is embedded in the model. And in that case the Helix preset should be set to standard tuning.

That step is not needed in this situation.

Yes, correct. That should do it for you.

The latest Mac driver for Helix is v1.04. It is listed as being compatible with OSX and forward. It also includes this notice: IMPORTANT! Installing the Helix Mac Driver 1.0.4 precludes using Helix with the class-compliant OS X Core Audio driver. Note that macOS High Sierra 10.13 has implemented a change to how drivers are accessed that may require your attention. If you cannot use your Line 6 device after installing this driver, please see this article: macOS High Sierra 10.13 Driver Installation Change

Did you also update the driver as part of the HX Edit 2.51 installation?

Restart your computer and Helix. What version of Helix firmware do you have installed currently?

See my post #5 in this thread, which is relevant after you have done the firmware update. If you haven't already updated post #13 in this thread is a good procedure (thanks Dshow). It's not odd to make a backup before updating even though a successful update will leave everything intact. The backup serves as a precaution in the event that the firmware update fails mid-stream and you are left having to perform a recovery procedure that wipes everything out.

Problem is that the update process does NOT replace the old factory presets with the new ones. It leaves ALL setlists unaffected. Choosing not to reinstall the old ones during the restore still leaves the old ones in place.

Thanks to those who have responded with their experiences. Looks like it doesn't really matter whether you use HX Edit v2.30 or v2.51 to perform the pre-update backup.

And don't forget that Variax owners can have Workbench HD running too! During beta testing I had Helix as my audio interface to my DAW (Reaper) running multiple instances of Helix Native using Snaphot-rich presets simultaneously with HX Edit and my JTV-59 with Workbench HD. All worked seamlessly together. Magic.

All patches run the same firmware, in this case v2.50 after updating. However, the firmware installation of v2.50 does NOT replace any existing presets/setlists - not even the factory setlists. The new factory setlists are stored in the new firmware but not available until you explicitly perform the startup sequence to restore stock presets and setlists. See: http://line6.com/sup...bleshootin-r768 Note that this will overwrite any existing custom setlists with the factory USER1 - USER5 setlists all containing the empty New Preset in all slots. So if you've already restored your custom setlists after the update, you will need to restore them again. If you have made any changes to these since the update you will need to back them up again before performing the factory restore.

To get the new factory presets you need to perform the startup sequence to restore stock presets and setlists. See: http://line6.com/sup...bleshootin-r768 Note that this will overwrite any existing custom setlists with the factory USER1 - USER5 setlists all containing the empty New Preset in all slots. Back up any custom setlists first and restore later.

To get the new factory presets you need to perform the startup sequence to restore stock presets and setlists. See: http://line6.com/support/page/kb/_/effects-controllers/helix/helixltfx-reset-procedures-and-troubleshootin-r768 Note that this will overwrite any existing custom setlists with the factory USER1 - USER5 setlists all containing the empty New Preset in all slots. Back up any custom setlists first.

To get the new factory presets you need to perform the startup sequence to restore stock presets and setlists. See: http://line6.com/support/page/kb/_/effects-controllers/helix/helixltfx-reset-procedures-and-troubleshootin-r768 Note that this will overwrite any existing custom setlists with the factory USER1 - USER5 setlists all containing the empty New Preset in all slots. Back up any custom setlists first.

I'm not saying that's the only new preset - it's just the one I noticed immediately.

I'm not sure it matter either. But in case it does I'm suggesting folks go with the 2.50 release notes that you have seen and use HX Edit 2.51backups.

I have updated the initial post. Thanks.