HonestOpinion

You can try some of the options provided on this http://helixhelp.com/pmwiki.php?n=Main.ResetOptions page, particularly the safe boot. Make sure you have backups though.

Not sure if you just meant this humorously or if this comment implies that you have updated previous versions of the firmware/software without doing the global reset. If so then Silverhead may unfortunately be correct that it may be possible that you have corrupt presets. Did the rest of your presets load alright, except for the problem six you described?

Thanks for everything hefonthefjords and you have contributed on this conversion issue. This workaround is probably huge for people with relatively few old presets or for someone who wants to use the new firmware with snapshots before the fix comes out. For people with a lot of presets though that conversion fix in an updated firmware release is going to be most welcome! :)

I just figured out what is required to eliminate the save in between each snapshot to correct this problem. You must have the parameter 'Snapshot Edits' set to 'Recall' under Global Settings > Preferences. This eliminates the need to save in between each snapshot and cuts the saves down to one per preset (versus a potential of 8 saves, 1 per snapshot, if you have the 'Snapshot Edits' parameter set to 'Discard). You still have to switch to and short the plug for every snapshot you intend to use however. If you have blank snapshots you don't need to fix them as long as you don't stomp on them.

It looks like there may be a fix for this prior preset conversion issue in short order (thanks so much for that info phil_m). In the meantime, if anyone has to play a show and is bent on fixing this themselves I highly recommend using the method above suggested by TLF2007 using a screwdriver to short the cable. I cannot think that it is good to be inserting and pulling a cable out of your EXP 2 jack hundreds of times unnecessarily. I know these jacks are built to last but why push your luck? ;)

Thanks very much for the response Phil! You are the man! :) That information is huge and I would not have expected a fix before the holiday. Just good to know it is coming shortly, not everyone may be aware of it yet but I think I just heard a huge collective sigh of relief. Btw, if you know a way in the meantime of executing the workaround without having to do it for each snapshot, please let us know. I have not been able to get it to work without doing a save in between each snapshot fix.

I should probably keep my mouth shut as this post will probably not endear me with DI or Line6 as well as some of the old faithful here (that ship probably already sailed a while ago anyway ;) ) but I feel I need to make a comment. I admit to feeling a little conflicted on this issue. As I expressed in my earlier comment I actually am ok with having to occasionally do some work to take advantage of a new update, comes with the territory. What I don't understand here is the baffling silence from DI and the rest of the Line6 crew regarding this fairly substantial issue in the new update with upgrading old presets. After a year in the open field there are many Helix users with quite a few presets from their old firmware, these include not only ones they have spent hundreds of hours crafting but presets they have purchased as well. This bug could theoretically cause people to have to update thousands of snapshots (number of presets multiplied by up to 8 snapshots). Obviously most people will not have filled all their User preset slots or modified all their Factory presets but the potential is there. Given the monumental amount of work that would be required by many users that this conversion issue from the old presets to the new firmware could entail, would it not behoove Line6 to have the courtesy to chime in here and let us know what they are planning? Forgive me if I have missed it but I have seen no official comment regarding this. It seems like it would be common decency to either let us know a fix is coming in short order or to inform us that this was the cost of improving the expression pedal behavior so we can get moving on a conversion plan of our own. Usually I understand why Line6 does not share its plans ahead of time and you will rarely to never see me on the boards complaining about 'transparency' but this is ridiculous. Would someone from Line6 please make a statement regarding their plans or lack thereof for fixing this. This appears to me to go beyond the usual corporate reticence and borders on rude, or at least an extremely poor decision regarding communication with the user base. Maybe I just don't understand the reason for staying mum on this issue, would not be the first time, but this issue appears to require Line6 let us in on whether they are planning (or not) to fix it, and if so, how soon. Please let us know what you guys are planning on this one. Thank you!

You need to download the latest version of the Helix app, 2.10 from the Line6 downloads page. It may not be a bad idea to uninstall all your old Helix software from your PC first and then reinstall the latest Helix 2.10 app. It should install the latest Editor, Updater, and driver. The firmware on your Helix should be fine as it is. Hopefully you made backups before you upgraded the firmware so you can restore your old presets and IRs.

Sorry for the repetition in this topic as I posted this elsewhere but I feel my earlier comment requires modification given the fact that this 'bug' does not occur with newly created presets. So... I have to amend my earlier comment or risk being a hypocrite. I have stated on the forum before that if new functionality or better sound occasionally require that we dig in and modify old presets I am more than willing. Well, here is a perfect example. We now have major improved functionality on the expression pedal behavior. Would it have been nice if the upgrade had been seamless with old presets? Sure! However, I am perfectly willing to go in and modify my old presets if they released this firmware, perhaps aware of this 'bug'/limitation, but also knowing the benefits the new firmware brought or not wanting to make us wait too long for it. Of course, if there is a quick fix that will obviate the need for the workaround, please bring it as this one requires a lot of work as it affects every snapshot! Thanks again for the new features Line6, I am more than willing to spend a little time adjusting old presets to get this in return! :)

I just noticed the same thing myself, you beat me to the punch. New presets create perfectly without demonstrating this bug. So... I have to amend my earlier comment or risk being a hypocrite. I have stated on the forum before that if new functionality or better sound occasionally require that we dig in and modify old presets I am more than willing. Well, here is a perfect example. We now have major improved functionality on the expression pedal behavior. Would it have been nice if the upgrade had been seamless with old presets? Sure! However, I am perfectly willing to go in and modify my old presets if they released this firmware, perhaps aware of this 'bug'/limitation, but also knowing the benefits the new firmware brought or not wanting to make us wait too long for it. Of course, if there is a quick fix that will obviate the need for the workaround, please bring it as this one requires a lot of work as it affects every snapshot! Thanks again for the new features Line6, I am more than willing to spend a little time adjusting old presets to get this in return! :)

Sounds like you know what I am referring to. If you go into the Command Center you will see the screen used for assigning, among other things, the MIDI commands. The six icons to the left on the top row look like lightning bolts. Those are 'Instant' commands and activate as soon as you change to the preset or a snapshot. If you want a MIDI command to be issued only when you explicitly hit a switch once you are in a preset you need to assign the MIDI command to one of the footswitch icons, not a lightning ('Instant') icon. Again, sounds like you were already aware of this but perhaps one got assigned in error? The video seems to be using the footswitch icons so if you did it like this without inadvertently programming an Instant command then perhaps something else is going on. Maybe one of the other LogicPro or MIDI mavens on the forum can offer more assistance.

The solution does work for me but it is a mighty large inconvenience to have to do the workaround to every preset. Although there is a workaround (perhaps not working for everyone or every preset) I think this is a crippling enough bug to warrant a quick patch and a fixed version of the firmware as quickly as possible. I hope we will not have to wait months for this one. This is a terrific firmware update, just needs a bit of massaging. Please don't kill the messengers.

I am not experiencing this. The fix does work for me after switching presets or after a reboot. I am on the floor version. Sorry to hear it is not working on your presets or your Helix fido083.

Not sure how this bug got past beta testing as all it required was switching from one snapshot to another and using the expression pedal switch to become immediately obvious. This bug is not exactly buried deep in a complex preset or arcane hardware configuration. Not saying this to fault anyone because that is rarely productive. Just means that a more comprehensive test of snapshot and expression pedal behavior needs to be added to the procedures used in the beta testing before every release (assuming this bug did not creep in unexpectedly at the last minute).

I have to agree, I am also a Variax owner and although I definitely hope Workbench functionality makes its way into the Helix at some point it is a low priority for me as that functionality already exists through the Variax USB adaptor even though as roscoe5 points out that is not ideal for the Helix workflow.

I say we model Horton's ear, he can even hear a 'Who'.

The great thing about snapshots is that this feature is what enables multiple footswitches to control the same parameter. For example, let's say you want to have a Clean' and a 'Lead' snapshot. When you hit the 'Lead' snapshot footswitch you can simultaneously turn on a distortion block but also turn up the 'Drive' and dial back the highs and presence on your amp block as well as for instance change the settings on your compression or delay. When you switch back to the 'Clean' snapshot all of the settings will go back to the ones that are more ideal for a clean sound such as the amp settings ('Drive' setting goes back down, presence and highs go back up) which now return to giving you a clean sound with a bit of shimmer on the high end that might have sounded ice-picky with your lead sound.

;)

Awesome that you archived these, what a great service to the Helix community, thanks! :)

Do these presets not 'work' or did they not load/import? I suppose you could always reflash the firmware and do another global reset and see if everything loads properly. What version of the firmware did you upgrade from, 2.01? Also, I am curious, are you restoring setlists, a bundle, or individual presets? If it is setlists, are the setlists loading and then rejecting just certain presets?

You make a good point Spikey, I edited my post a bit because I don't care what mechanism Line6 comes up with as long as a preset is able to refer to the correct IR after an update with a minimum of hassle. I most like the suggestions that have been made that have the lookup in the preset using the name such that it does not matter which slot the IR is restored to as long as it is on the Helix.

I think you just need to set the 'Snapshot Mode Switches' parameter under Global Settings > Footswitches

Interesting thought and worth investigating, that worked a few firmware versions ago when certain presets were causing Helix and Editor lockups.

Gotcha, sounds like it is behaving normally then. Thanks for the reply.

Workaround in this post as well, looks like the same one as here: http://line6.com/support/topic/24048-fw-210-expression-pedal-question/?p=183609