HonestOpinion

Try these in this order, these steps have worked for many people: Exit the Updater, unplug the USB and replug it and restart Updater. If the firmware update does not complete reboot your PC and try the same process in other USB ports and see if update completes Unplug everything from the Helix, reboot your PC, plug Helix back in and start the Updater and see if you can get the firmware process to complete Uninstall all Line6 software and download and reinstall "HX Edit" 2.80. Check all the install boxes - drivers, Updater, HX Edit. Start Updater and attempt firmware update. If it is still hanging try using a different USB cable and try connecting to every available USB port. If none of this worked check out this thread, there are a ton of tips over there as well as many other topics that were started in the few days since the upgrade that contain tips for completing the upgrade.

Yep, that would be one of many possible ways to do it. If it sounds good to you, go for it.

Just basking in the positive vibes in this thread. Great place to be reminded of all the new stuff to try in the new firmware. I know it has been mentioned already but QWERTY keyboard, , tempo display, expression position display, the KOT/POT pedals, undo/redo and the list goes on. Also never expected to see a Moog pedal on the Helix; so great, hope they do more of them. And just for a note of nostalgia from previous firmware, still very appreciative of the changes they made to the tuner. Made it much better for stage use. The Helix has far exceeded my expectations when I think about what was delivered years ago when it was first released. Also have to mention how inspired I think it is that Line6 has created a genuine modeling ecosystem. One that includes not only a family of HX devices as well as a plugin(Native) and the ability to share data and settings between them but also the integration of a modeling guitar cab like the PowerCab+ with a modeler(Helix, LT, etc.). The lack of intelligent linkage between cab and modeler was IMHO one of the glaring deficiencies in the modeling world.

Plenty you can do now for acoustic guitar but I agree a bit of focus on it now and then would be most welcome. It would probably generate some additional device sales, potentially quite a few, a lot of acoustic guitar pedals and amps get sold. I have posted this before but coincidentally my favorite acoustic guitar processing device of all time was made by Line6's parent company. The Yamaha AG Stomp. Don't even need to go out of house.

Although there are definitely defective USB cables out there on occasion, and swapping cables is a worthy troubleshooting step, I think for some users it is actually the process of swapping out the cable, not the cable itself that actually enables their system to reconnect. I would be curious to know if now that your upgrade is complete if your old cable works?

I posted one very minor one where if you use all of the characters available for a setlist name the last character doesn't display on the Helix. There are probably other bugs here and there. This truly was a massive rewrite to the code. I know people are tired of hearing it but the rewrite has the potential to expedite future improvement of the entire product line and prolong the time it remains in active development. Some issues will inevitably be introduced when you modify a product's architecture and codebase to this extent. I would ask my fellow users, what was the alternative? Probably a moribund product where updates came dramatically less often as all efforts would have had to be diverted to the next generation of HX products for any substantial progress to be made. In my eyes pursuing the current upgrade strategy is a huge win for us users but it does come with a cost. Yes there will be blood on the bleeding edge. In the interim I understand people's frustration but for anyone who wants to jump in now, depending on what other devices you have connected to your HX device and how you construct your presets you may find a bug. It may be minor and something you can work around or it may be a showstopper for you. Anyone who dives in right now to the latest upgrade (and I believe it is worth doing), should be prepared to roll back if they hit an issue that they can't tolerate. If rolling back is something repugnant to you I would recommend waiting until at least the next fix or release. Why subject yourself to needless aggravation? Personally so far I am delighted with the new update but perfectly prepared to roll back if I hit something in this firmware that I can't work around.

Interesting behavior on this as well. If you set the 'Snapshot Bypass' = "Off" with for example your Reverb block in an active state and bypass it either on the existing snapshot or another snapshot, now when you switch to any of your snapshots it is off in all of them. This provides a convenient method to change the state for a block from active to bypass or vice-versa in all of your snapshots at one time. Handy for previously constructed presets as well as ones you are creating! This used to be a more tedious process where depending on your global snapshot behavior settings and how you set up your snapshots initially you would have to go to each of them and change the block state and save.

Nope, did not say that there was no way to get it working (that would have been incorrect), sorry if my post implied that, Just sharing that I had run into it before and how it was resolved by other hardware vendors whose hardware looked like an external keyboard to iOS. Great tip, thanks for sharing it. This is a much better resolution than the one used by the Bluetooth pedal manufacturers. Having the solution be within iOS means that every peripheral device that presents itself as a keyboard does not have to work around this issue. I wonder when this was added to iOS? Seems almost redundant and an added expense for other hardware manufacturers like the Bluetooth pedal manufacturers to add a button to do this. Maybe they thought it would be faster/easier? Let us know if the long press method works for you.

I emailed him a question about a problem with a Boss pedal I was trying to repair many years ago that he kindly took the time to answer in fairly decent detail. This was when his pedals were first starting to get some traction and I believe he was still custom making all of them himself. I always appreciated that he had bothered to help me out.

Man that thing sounds awesome! Ideascale? That would make one fine addition to the Helix.

Particularly since you are starting from scratch make sure to do the global reset to get the latest Factory and Templates setlists. They are the final steps in the upgrade instructions.

If you are in Windows you can simply right click on a directory in File Explorer, select 'Propeties' and click on the 'Security' tab. Then select something like the "Everyone" group and grant/check the permissions below you want to grant that group which will of course include read/write.

I think it is a given and users who do the upgrade should be resigned to the fact that there are going to be a fair number of bugs to be discovered as "Core" constitutes a major code rewrite. You almost need to think of this as a brand new product. There will also be the usual share of erroneous bug reports due to wholly or partially failed upgrades or confusion about global settings. If the legitimate bugs are something that interferes substantially enough with how you use your HX device you may want to wait until the next hotfix or a couple of minor revisions when the major bugs have a chance to be worked out of the new Core rewrite. For me the new features far outweigh the bugs I have run into so far but YMMV.

Is there a pattern? In the past I seem to remember at least one firmware revision where copying a preset from one location to another would initiate a rebuild on the next restart. Another question would be have you loaded or created any new presets and if so, are those the ones that get rebuilt on your next startup?

The 1.91 drivers can be found here: https://line6.com/software/readeula.html?rid=8569

Interesting, I used to run into a very similar issue using OnSong with my Bluetooth pedal. It was solved by activating a button on the Bluetooth pedal. I think it would be a very well received feature if Line6 added something similar to the Helix in the future. This link helps explain why this happens. https://onsongapp.com/docs/faq/foot-pedals/

I would go one step further and like to see the software actively prevent people from ending up with for example non-matching versions of HX Edit, drivers, and the firmware. Would be great to see HX Edit pop up a message and say "Nope, sorry, you are running firmware 2.71 and this is HX Edit 2.8. Please update your firmware". Or alternately, "You are running an outdated version of HX Edit, your firmware is 2.80, please update to HX Edit 2.80." Another way to do this would be to integrate the Updater into HX Edit so that downloading the new HX Edit package was the only way you could execute a firmware upgrade. Less flexibility with that approach but also a lot less failed upgrades. Ultimately the objective would be to tie the editor, updater, and driver versions together so that users can't mix and "mis"match components.

Multiple parameter pages are indicated by a bar on the Helix instead of dots now. I realize many/most people may be aware of this but just in case you think you are looking at all the options available when you select a Global category or an effect block, you many not be. Just wanted to point out that the indicator for multiple pages has changed since the last firmware. Under Global setting for example some of the categories will have multiple pages. The dots that used to indicate that a Global category had multiple pages has just been replaced by a bar. This applies to the parameters for all other types of blocks that have multiple pages as well. So if you see a bar that is not solid white all the way across, this indicates that Global category, block(effect, input, amp, whatever, etc.) has multiple pages. They are accessible by using the page right or left buttons as in the past.

Added general request for polyphonic processing to Ideascale. Would love to see this come to an upcoming firmware upgrade. Vote 'er up: https://line6.ideascale.com/a/dtd/Polyphonic-Everything/960087-23508

Interesting idea, you should put it in IdeaScale where it will be seen by Line6. https://line6.ideascale.com/a/community/login

A couple of more things occurred to me to try if you have not already. Create a new directory on the F: drive and make sure you give permissions to "Everyone" to try to eliminate permissions problems. Also if you haven't already, try saving a preset other than the one named "TEMPLATE". You just want to make that your preset does not have a name that could have even a remote chance of being reserved.

Has not been my experience. Mine has always saved to other drives in previous versions and still does in 2.8.

Strange, have you tried another directory on that drive? Could be a bug, just not having this issue on my setup. I'm curious, when you highlight for example two or three presets simultaneously and export them all at the same time(which supplies a different style dialog box on my PC) does it export them successfully to this directory or any directory on your F: drive?

I would probably double-check my USB connections, try other USB ports, reboot my computer, and if necessary uninstall and reinstall HX Edit 2.80. If it continues to crash on create backujp you can backup the setlists and IRs individually(if it lets you) and see which one is crashing. Narrow it down from there. Btw, curious if you would have this problem running HX Edit as Administrator just to make sure it is not a permissions problem on the directory you are backing up to. Do you have any anti-virus program running that you can suspend for the duration of the test.

Good catch! I can confirm I see the same thing. When I disable the tap tempo LED the LED ring on FS2 no longer reflects its bypass state properly when I switch to stomp mode. Turn tap tempo LED back on and it is working properly. I think this is a legit bug.