HonestOpinion

If this was indeed the cause then users like the OP who experienced this should just give it another go and unless they have the incredibly bad luck to hit the same server issue again, one that most of us have not encountered, the update should be successful. If this turns out to be a problem on the server side it would have been nice to see a heads up from Line6 on TGP - and on the Line6 forum(cracked myself up there). To be fair though, rather than this being caused by an issue with Line6's servers it might have been a problem somewhere in the hops between the user's ISP and the Line6 servers rather than a problem on the servers themselves.

So far with the exception of the odd preset that is corrupt or perhaps a firmware that left something out that impacted a specific parameter of a certain effect, all of the old presets and setlists have stayed compatible with every firmware revision and editor version up to the current day. Congrats to Line6 for keeping restores backwards compatible. No. Whether extracted from an old or new backup you get the same error message when you try to open an "Extracted" preset with Native that you get with the Helix - "8103 - Target is incompatible.". There may be a pattern but I don't think so. So far when using the files produced by the "Extract Files From Bakcup" command, every preset seems to fail on import, even blank "New Preset"s. Have not tested them all obviously.

The Helix seems pretty forgiving in regards to heat but this sounds like a recipe for overheating your device or electrocution to me. I would set up some kind of three sided box over it before I ever put my device in a bag. And hey, playing in the rain is just plain dangerous as in potentially fatal unless you have a properly covered stage anyway. I have done it(hopefully never again) against my better judgement and defying all natural survival instincts because it was a show I had been really looking forward to combined with a monumental failure of said judgement. It was a case of the frog coming blissfully unaware to a slow boil in the pot as the covering on the stage gradually failed under torrential rain. Does "Is it a bad thing that my pedalboard is sitting in at least a 1/2 inch of water and the PA, backline, and everyone on stage is soaking wet?" sound familiar. If so, well, it shouldn't. I feel lucky to have lived to tell the tale.

You can find a compromise of various recommendations that works best for you but Line6 has stated on numerous occasions that the best place to set the large output knob is on max or close to it(if you want a bit more flexibility). As already stated above many including me use the global settings such that the output knob only controls my onstage monitor and not the feed to the FOH which results in the max level being sent to FOH. This actually has the opposite effect that you are worried about - "blow off my own head". It ensures that you don't have to remember where you had the output knob set when you designed a particular preset. You simply make sure you have all your presets leveled properly with the 'Ch Vol', output block, or wherever you choose to gain stage them, knowing that they will always be sent out to FOH at the output knob's max output level Hopefully no nasty surprises for your sound person. Getting sufficient level out to your monitors or PA is critical for tone and S/N ratio. Obviously it shouldn't be too hot either though. Just turn down the channel on the mixing board or your amp/monitor as necessary. It will probably extend your PA or monitors' life too as they don't have to work as hard when they get adequate signal.

A lot of those internet speed tests tell you your average speed but don't indicate if there were significant lapses in connectivity. So the average speed can test ok but if the app, e.g. HX Edit, has a shorter timeout setting than the duration of your internet connectivity lapses the download can still fail. Definitely try disabling your firewall and antivirus for the duration of the update as this is one of the common causes of downloads failing. I have seen this happen sometimes when something gets stuck in a browser's cache but that should not apply here. I would also check and make sure my hard drive wasn't full or close to it. If you have not already I would uninstall HX Edit and reinstall. Btw, what version of HX Edit and the firmware are you currently on? A question we probably should have asked right off the bat. Go ahead and download and install HX Edit 3.10 if you have not already. Seems like we have touched on most of the usual causes for file downloads failing - security settings & permissions, antivirus/firewall, disk full, incorrect software, problems with cache memory, computer requires reboot, etc.. A freakin' mystery. Please let us know if you get it figured out.

I just ran the extract on one of my backups made with HX Edit 2.30 back in 2017. HX Edit 2.30 was the first editor version to offer the 'Create Backup' command which resulted in a file with the "hxb" extension and format required for the Extract command. All the presets from that backup seem to have been successfully extracted. They just still can't be imported due to the current bug with the extracted files' format(-8103 - Target is incompatible). So... looks like the extract should work with any backup made since the advent of the 'Create Backup' command. Wouldn't be surprised if you could find a way to edit the old "bundles" too, which were the format used for backups in the early versions of the editor prior to 2.30, or even old setlist backups and prepare them for the Extract command but it might be more effort than just parsing them for the presets yourself.

Thanks for updating us. Glad to see you back in action!

None of these are stupid questions, they all sound relevant to me. I would say the problem is the format of the files after extraction, rather than the import/conversion but it could be either/both. It makes more sense to me that Line6 would not want to dedicate development resources to two conversion/import paths, one for exported presets and one for extracted. So you would think the preset file should be the same or close enough in format whether it is created with the "Extract.." command or by an Export command to be "import ready". Regarding how old a backup it will work on will be difficult to answer with confidence until they fix the utility so that the extractions can be properly loaded afterwards. I suspect it will be able to extract from most any firmware version's backups, but I guess that depends on how dissimilar the oldest firmware's backups' formats are to the current format. I would hope the Extract utility operates in a manner similar to the way the Import command can still import even old CustomTone presets as well as old setlist/preset backups from early firmware versions. I guess more experimentation with this utility will answer your questions definitively. Will be interesting to test once they fix it.

Check in HX Edit under 'Help' --> 'About HX Edit'. Are you running HX Edit 3.10 with the 3.11 firmware? One possible cause of the import failing is the wrong version of HX Edit.

Would be great to hear this workaround confirmed by some other users with this issue.

Yes, this issue is only when extracting presets from the backup with the 'Extract Files From Backup' command. All other backup/restore and import/export operations continue to work and are the same "as it ever was" as far as I know. I can see where my original comment might cause confusion. I edited it to make it hopefully clearer.

The 'Extract Files From Backup' command is still buggy, even if run on backups created after the latest firmware(HX Edit 3.10 & firmware 3.11). The backups work fine, just not the files yielded by the extraction command. In the interest of not generating any confusion, I am not referring to the 'Create Backup', 'Restore From Backup' or any of the old export/import functions in the HX Edit librarian section. Only the "Extract..." command.

Well done sir! Glad you checked the "Helix Bug Reports" topic where I posted that.

Hope you are kidding. I hear you though. It is always dangerous for a piece of software to have a backup or extraction function that does not work as people mistakenly think they have a dependable backup when they actually don't. Better in my opinion to pull it out of HX Edit until it works properly. You should at least have the backup you extracted from. That will have all your setlists which can always be loaded and the presets sifted through using the old functionality. Sincerely hoping Line6 will fix this utility soon and definitely by the next firmware update.

Thanks to AgFX for bringing attention to an additional bug that renders this command unreliable until it is fixed. The preset files the 'Extract Files From Backup' utility extracts fail when you try to import them back into your device with the following message: "-8103 - Target is incompatible". Perhaps there is a manual edit that could be done to the extracted preset files in the meantime that could get them in the proper format for import but who wants to have to do that. I opened up a Line6 ticket with all three of the bugs discovered so far. Update: AgFx posted that he went ahead and figured out the manual edit required for the preset files produced by the extraction and was able to import them so they do provide some measure of usefulness but for most users this utility still needs to be fixed.

Another great preset thank you. If I might make a suggestion. You seem to be a fairly prolific creator of presets and as such you may want to consider starting a single topic named for example "Timeblock's Presets" and start posting all your presets there instead of opening a new topic for each preset you create. This will consolidate them and make it easy for your fellow forum members to find them all in one place and quite frankly be a better way to use the forum.

UPDATE: After doing more testing thanks to the user AgFx's topic it has become apparent that the 'Extract Files From Backup' command does have an additional showstopping bug. The presets it extracts fail when you try to import them with the following message: "-8103 - Target is incompatible". This makes the extracts currently unusable. At least on HX Edit 3.10 and firmware 3.11. I have opened a ticket with Line6 with this major bug and also including the more minor bugs I already reported. Hopefully others will open a ticket on this utility as well. Would like to see it fixed soon as it is as already commented on very useful. Dissapointing but until Line6 fixes it I would encourage those who make backups of their setlists or presets to keep using HX Edit's old export functions until this utility is dependable.

I think you have found a legitimate bug in the 'Extract Files From Backup' command. I am able to recreate this exact message when I attempt to import files created with this command. You should open a ticket with Line6. This utility is still clearly buggy but holds great potential. I listed a couple of more minor bugs I found in the bugs topic already but this one is a showstopper. Until Line6 fixes it I would encourage those who make backups of their setlists or presets to keep using HX Edit's old export functions until this utility is dependable. Update: I have opened a ticket with Line6 on this bug and the others I found previously but the more the merrier(tickets opened that is, not bugs).

Any possibility you were the one who named the snapshots in the older version? Are the contents/settings of the snapshots in the first screenshot the same as the second but just named generically with the defaults(e.g. "Snapshot 1")? Try exporting the old one in the second screenshot that is working properly and then importing it. Does that work? If so I would say that there is a good chance that your download is simply a different version of the preset, even if it appears the same as the one you downloaded initially. Also as always, check in HX Edit if 'Help' --> 'About HX Edit' is showing HX Edit 3.10 with the firmware at 3.11(assuming you are on the latest version).

My first thought would be a spotty internet connection. If so then downloading the firmware file manually and using the Line6 Updater probably is the best method for you to do an update. Do you have an antivirus/firewall program running? If so it might be worth disabling it for the duration of the update and seeing if it can successfully download the file. I hate that momentary security lapse but sometimes it is the only way to find out if that is the source of the problem. The only other thing that occurs to me is if somehow it can't overwrite the file from a previously interrupted download. That seems farfetched though and it has been a while since i have seen an install fail from permissions problems in any software; at least consumer based.

I would uninstall the Line6 software and then download and reinstall HX Edit 3.10. Try swapping around USB ports and cables. Try another PC if you have one available. Ben Vesco has most(all?) of the old factory presets stored on his site. Scroll down towards the bottom of this link. http://benvesco.com/store/line-6-helix/

Haven't tested the latest version of HX Edit and the firmware but in past versions just copying and pasting presets from one location to another even without importing any presets would cause just the copied/moved presets to be rebuilt upon restart. As has been stated though the only time you should see all the presets rebuilt is after a firmware upgrade or a restore.

As you state the Stomp is working properly when it is disconnected from the rest of your pedalboard I would probably start troubleshooting by removing, as in physically bypassing(reroute the cables), one pedal at a time to see if you can isolate this issue to one bad cable or pedal that might be causing problems with the HX Stomp. Also doublecheck your cabling to the Stomp to make sure that is correct. Unlikely to be the issue but I would also be curious to know whether or not a noise gate is on in your Stomp preset that might be overreacting to a substantial level change from one of your pedals? One last thought. If you have one available it might be worth powering up the Stomp on a different circuit than the rest of the pedals on your pedalboard in the event that one of the pedals is causing a power fluctuation that is impacting the Stomp's operation. Also make sure the power connection to your HX Stomp is secure as pressing the pedals on your pedalboard could otherwise cause a momentary disconnect.

Sounds like you need to download and install HX Edit 3.10. Make a backup first. After HX Edit 3.10 is installed you should get prompted to update to the 3.11 firmware. Make sure to follow the release instructions and restore your global settings and setlists afterwards. When everything is completed you can check 'Help' --> 'About HX Edit' in HX Edit and you should see your editor version at 3.10 and your firmware at 3.11.

Maybe I am not properly comprehending the behavior you are describing. As long as I keep the parameter 'Lock Control (Preset)' = "Volume+Tone". My volume and tone predictably change according to the preset every time. The one caveat being that if you move either the volume or tone down all the way. set them to "0.0", not "Don't Force" which is the setting below zero on the slider. This works for the Variax volume and tone controls in my presets as well as my snapshots. Are you talking about a different issue? Btw, I have a JTV69s and I am on HX Edit 3.10 and the 3.11 firmware on a Helix. Is your rig behaving differently? If so it might be worth checking with a different VDI cable or doing a global reset.