HonestOpinion

Wow, my unfounded speculation may actually have been correct, grin. First time for everything. If that indeed was the culprit then I would think that others that hit this just have to find a window where everyone is not updating there firmware at the same time and the Marketplace servers aren't too busy to ack.

Not yet and the bug is still there in the 3.01.0 firmware.

Hmm, haven't seen this one. Looked this up with Google rather than the forum and it looks like it is some kind of general license server error. I would try rebooting my PC. Could be a corrupt preset perhaps. Try selecting a different preset before attempting your backup. If all else fails I suppose you could backup a bundle, your setlists, and even individual presets and use them to restore if necessary. Does your version of HX Edit match your firmware version? If not take care of that first. Btw HX Edit 3.0 is the match for firmware 3.01.0. Another thing occurred to me and this is pure unfounded speculation. Do you have any presets purchased from the Line6 'Marketplace'. If so maybe their license server is trying to check them and because they may be slammed by too many users trying to update at the same time it is failing to acknowledge. Anyone else seen this and know what the issue is?

Been there!

Sounds like either you didn't upgrade your firmware to 3.01.0 or you did not upgrade HX Edit to 3.0. You need to do both.

Sure does! The Helix runs the rebuild process to ensure that presets from earlier firmware versions get upgraded to be compatible with the new firmware and HX Edit version.

Don't turn off your device during a preset rebuild. Could not tell for sure from your post if you let it complete, probably did, if so ignore the warning.. At least on the Helix there are up to 1,024 presets to rebuild(often skips the Factory presets as they are already at the current firmware version if you did a global reset). Wait for the rebuild process to complete and your device will show its usual operational screen. It is normal for the first startup after a firmware update or backup to include a preset rebuild. Just wait for it to complete and it should not do it upon your next restart.

Those should get backed up in the 'Create Backup' as well. There are new headings for them when you do a 'Restore From Backup'. I would think it should only be an issue if you do a global reset anyway(never a bad idea).

Looks like a follow-up version of the the 3.0 firmware has been released with bugfixes. You should probably update your firmware to 3.01.0 before you start a new topic or post about a 3.0 issue. I don't see a new HX Edit for 3.01.0 yet. This is just a firmware update. At least for the moment. As phil_m posted elsewhere, try using the "Check for updates" link at the bottom of HX Edit to do the firmware upgrade before you resort to using something like the standalone Updater. Worked fine for me. Update: This topic somewhat redundant now as Line6Tony just put up a sticky. Apparently there is some urgency connected with this update as 3.0 can corrupt the audio(presets?), so do it right away! Also per Line6Tony there will be a Native update coming in short order as well.

There is now a 3.01.0 firmware release out with bugfixes. Before you start a new topic or post about issues you are having with 3.0 please upgrade to the 3.01.0 firmware.

I could envision something like this having an initial "recognition" initialization routine where it gets a baseline for a specific guitar, pickups, cable, and set of strings. Anyway, like most things that are technically challenging now I am sure they will get around to it sooner or later. Just how much later I don't know. Who knows what is currently being worked on behind the silicon curtain? :-)

Without being able to reliably predict how long I will be on this blue marble I can't argue that. I can see someone eventually coming up with an algorithm that was able to reliably able to use the timbre of for example a low E string to only pitch shift that string. A low E still has a unique sonic signature that is not the same as a D string played up two frets.

Definitely a great deal for new buyers. Please let me know when this offer applies retroactively to Helix owners who have had there device for several years now :-) Note: I will not be holding my breath until then.

Having a poly whammy is fantastic but two of the most exciting things about poly for me are quick access to alternate(capo) tunings to cut down on having to switch guitars and the potential it has for delivering synth effects that can track decently without a hex pickup. To me part of the big picture when it comes to poly is the capability to finally merge a top-notch modeler and its attendant effects with a guitar synth. Perhaps we can stop thinking of guitar synthesis and amp and effect modeling as separate worlds and devices in the future. For those of us that have been using guitar synths for decades you usually have to make a choice(or run through two devices) - a quality guitar synth with subpar effects and guitar sound, or, a quality modeler with great guitar sound, effects, and amp modeling with perhaps some small measure of difficult to use, poorly performing/tracking synthesis with limited capability thrown in as an afterthought. I am hoping we move to modelers that combine the best of both worlds. For that to happen we may need to wait for a next generation device with the processing power to pull it off. Maybe the programmers at Line6 will surprise us though and figure out how to deliver on the current platform. Again, I can't help but think, wouldn't a modular approach be great where we could simply drop in an integrated synthesis module internally to our modeler. Btw, I would love to see poly able to downtune strings individually such that I can for example drop only the low E to a D for a Drop D tuning. I use my Variax for this currently but it would be great to have the capability with my "normal" guitars.

Wow, that is an incredibly nicely rendered document. Looking forward to more contributions from you on this forum.

Any chance your global settings --> 'EXP Pedals' --> 'EXP 2 Pedal Position' parameter setting has changed since you updated? Depending on how you had it set before the update it can cause unpredictable volume changes afterwards from one preset/snapshot to the other if it is not the same.

I can respect that. Even if I could I would never try to impose my standards for what is an acceptable tone or effect on another player. Just saying I think a lot of players will find this usable now at least for some applications. By all means post more examples and even open a ticket with Line6 with specific issues if it helps make Poly better.

Not that it can't bear some improvement but I have to say I can't see what I hear on @SaschFranck's recording being a huge problem in a live setting. Heck, at least in the clubs, given the sounds of conversation, glasses clinking, chairs moving, servers taking orders, etc.. I don't even see it being much of a problem in a solo setting unless you guys are getting much more polite crowds than I have experienced or are playing in an auditorium you can hear a pin drop in with a rapt audience. Even then I think it could be passable depending on what is being played. Btw, with the exception of a few socially distanced porch jams all my gigs post-COVID have been "solo", as in, just me :-) This is the first iteration of poly in the HX line and it took a while to get here so although everyone hoped it would be perfect out of the gate I think it is only reasonable to give Line6 a little time to refine it. It is pretty decent right now and a paradigm shift for HX with some serious potential. Code optimization is actually at the absolute top of my list for poly enhancements so that it chews up less DSP and allows more of the blocks I use in my signal path to remain. Yet another reason I would love to see a modular approach to modelers where I could just throw some more/faster DSP at this. Glad to see people make specific suggestions on where it can be improved though especially when accompanied by audio that demonstrates areas of concern. Those observations are what will hopefully help drive its future development. It is probably an overstatement to call it unusable(not implying you were saying that) but standards differ between players. Perhaps some will have to wait(could be a long time) to use it live until it hits their threshold for performance use. For me I think I could find places to use it now, as it is.

Great writeup!

You say you notice the issue in the updated HX Edit. Did you also update to the matching firmware?

Definitely worthy of mention. I can see some users having to make adjustments to their presets after enabling this. For example resetting the EQ, reshuffling blocks, or undoing the footwsitchable impedance setting workarounds some of us employed previously. After that the preset should behave predictably afterwards.

Btw, also worth mentioning you can assign block parameters to the Variax's volume or tone controls. For example you can assign the 'Drive' parameter from your Distortion block to the Variax's volume knob such that when you turn it up the amount of drive on the distortion also increases.

Glad to hear that! One note, maybe you already did this already, but if you are on firmware 3.0 now you should also download and install HX Edit 3.0.

I can confirm this bug and nice writeup. Can tell you read the first post in the "Helix Bug Reports" topic.

LOL, thanks for reviving this topic. I think it is still relevant but I doubt it will ever change. When snapshots were first released, at times I wanted to use more descriptive names, e.g. "DistFlangWahComp" but by this time the character limit has pretty much conditioned me to use "Clean", "Crunch", "Lead", "Intro", "Verse", etc. and that is about it. For many(most?) snapshots the current limit(10) is perfectly adequate. Would still be nice to have the six extra characters(would give us 16) that the camera icon eats up but at this point the implementation feels pretty baked in. As @ricksteruk so presciently alluded to back in 2016, now that snapshots can be randomly mixed in with stomps or presets on the footswitches there would be an even greater need than previously for a visually distinct way to spot them once the camera icon was removed. Would love to see it done but it would require some thought as to the best implementation. I would still leave the camera icon as an option 'cos people have grown up with it by now and learned to love 'em. After all these years, still low on my list of priorities but if it required minimal coding effort I would still vote for changing it. To me the camera icon would be like attaching a disco ball to my steering wheel. Looks kind of interesting and makes it really obvious where the steering wheel is but do I really need it obscuring the dashboard and my vision through the windshield :-)