datacommando

Hi, Apologies for the delayed response, and being unclear about my directions regarding the procedure. If you managed to follow along about downloading the components required for the offline installation, then you should realise that reference to the “Flash Memory” is the actual Firmware “flash memory” file required to perform the update. The file name for this will most likely end with “_bundle.hxf” for example: “HELIX_Floor_v3.60.0_0xe171dae81_bundle.hxf” As I mentioned in the earlier post, you should have made a note of where these various component files had been downloaded to on your computer. Then when you launch the Line 6 Updater Utility and select "Offline Mode". Your HELIX and current firmware version should now show up in the window, click on the dark green coloured band and you should now have the option to select a local file - specifically the Firmware Flash Memory bundle noted above. While in the Updater Utility, you simply need to navigate to (point it at), and select the firmware bundle which you downloaded previously. Hope this helps/makes sense.

Nice attitude - see how far that takes your request, Jedi, really?

Hi, Two people have already answered your question about the factory reset options! @silverhead posted a link to reset procedures, and @MusicLaw pointed you in the direction of https://helixhelp.com/tips-and-guides/universal/reset-options Furthermore, if you click on the question mark in the black dot in the lower right hand corner of page, it will reveal the Help Page. Once again if you scroll down that section you will find the reset procedures for all the hardware below the Common Product FAQ. I really cannot comprehend how much clearer this guidance could be. Hope this help/makes sense.

Here ya go! YouTube is crammed with instructional videos for this stuff. Hope this helps/makes sense,

Bonjour, suivez le lien ci-dessous et utilisez Google translate pour convertir les instructions en français. Cette technique est connue pour fonctionner auparavant. Chaque fois qu'il mentionne Firmware, vous devez utiliser 3.6. Remarque : Les instructions étaient pour le Firmware 3.5, mais vous devez utiliser la dernière version 3.6. J'espère que cela aide / a du sens.

For the benefit of anyone else who may have issues with HX Native when changing to a new computer, hard drive, etc., here is the Line 6 advice. Hope this helps/makes sense.

Hi, Having had the chance to run both of these audio clips through my monitors, I think I agree with the comment from @SaschaFranck in the post above. My guess is you are driving the input of HX Native a bit to hot. Keep in the green on the meters.

Hi, I can’t make any comments about your audio examples as I’m using my iPad right now. Actually, beside the audio snippets, it would be a big help to know what your computer, operating system, DAW and monitor system are. Hope this helps/makes sense.

Hi, As he is asking about a recording made with Helix Native, he must be referring to a Direct Injected (dry) audio signal, played back through a preset in HX Native. It may be more useful to know what computer, OS, and DAW are being used for this, even though he said his friend has a similar set-up (not identical).

Hi, Interesting conundrum. You update your MacBook Air to a public beta release (MacOS Ventura 13.4), and now your copy of Helix Native doesn’t work correctly? Usually, I find software will stop working as expected when something changes to cause that to happen. Mmm … what could possibly have changed to bring this about? Couldn’t possibly be anything to do with a beta version of Apple’s OS, oh, no, not that! I know - blame Line 6 - Really annoying :( You also failed to mention if you actually tried the possible solutions presented here? Hope this helps/makes sense. (Possibly not!)

You’re about 5 years too late with your comment. :-)

Hi, Neil, The advice given in the post above from @silverhead about using your HX Stomp as the USB audio interface is possibly the best way for getting both the processed dry signal into your DAW. At the very least it is the simplest method. The other big thing to bear in mind when using HX Native to create presets that you can transfer back into the Stomp is, you will need to use Preset Compatibility Mode in Native. As Native uses your computer to the process the signal, it is not restricted in the complexity of the path it can create: - i.e. it can create a preset that exceeds the DSP in your hardware. Once you have created a compatible preset in Native you can easily save it to your HX native library or drag and drop it to your desktop and load it into HX Edit to transfer it to your Stomp ready for use in your live set. See "Preset Compatibility" on page 14 of the HX Native Pilot's Guide 3.6 available by clicking on the Question Mark Icon in the lower left of the GUI. Also see page 55 of the HX Stomp Owner's Manual for the full details of using your device as an audio interface via USB, DI recording and Re-Amping. https://line6.com/data/6/0a020a418962611d636e7c51b/application/pdf/HX Stomp 3.0 Owner's Manual - Rev D - English .pdf Hope this helps/make sense

Hi, After you complete the restore from back up, you will notice that the next time you restart the hardware, it will run the “Rebuilding Presets” routine. This is perfectly normal as it ensures that all you older presets are optimised for use in the new firmware. Also, any time you install a preset created with an earlier version of the firmware (e.g. your backup files, a preset downloaded from CustomTone, etc.), the Rebuilding Presets function will run again after the next restart - this is an expected housekeeping routine for the unit. Hope this helps/makes sense.

Hi, Thanks for the clarification, about your situation, and I’m glad you have found that reverting to the previous firmware seems to fixed the issue of “freezing”. Not ideal, but at least it is functioning. It seems to be very odd that you actually managed to install 3.6, but would lock up after a short time. Did this happen while being disconnected from your MBP or was it still on the USB? It appears to me that there is some sort of mysterious voodoo involved with USB and firmware update glitches. As for your Helix being “quite old” - I don’t think that is the real problem. I have and my Helix since 2015 and it is in use in my studio for several hours almost every day. I’ve lways managed to keep up to the latest firmware revision. Hope this helps/makes sense.

Hi, That’s because you are trying to import files designed to be used in dual processor devices into your HX Stomp. The presets here are specifically for use with HELIX, HELIX LT & HELIX RACK. If you want to check out the presets for your Stomp, ensure you have a backup of all your stuff (this should have been done prior to updating the firmware), then restart your HX Stomp whist holding down footswitches 2&3. This will load the new presets for you to check out, play around with, save or whatever. Then whenever you wish you can simply reload your own saved presets from your backup bundle. Hope this helps/makes sense.

Hi, Glad to know that you have managed to update your Helix Rack successfully - finally! Apologies, yes, the safe boot/update encoders 1&6 are correct, exactly as stated at helixhelp.com - I will edit my instructions. Re: Factory Reset - From the Release Notes for v3.6 Firmware: Perform a factory reset. IMPORTANT! MAKE SURE YOU HAVE A BACKUP FIRST, AS A FACTORY RESET WILL ERASE ALL YOUR WORK! Helix Floor/LT: While holding footswitches 9 & 10 (bottom row, 2 middle switches), turn on Helix Floor/LT Helix Rack: While holding knobs 5 & 6 (2 furthest right knobs below the screen), turn on Helix Rack HX Effects: While holding footswitches 6 & TAP (2 farthest right switches on the bottom row), turn on HX Effects HX Stomp: While holding footswitches 2 & 3, turn on HX Stomp HX Stomp XL: While holding footswitches C & D, turn on HX Stomp OPTIONAL: Performing a factory reset loads the new 3.60 Factory Presets, but restoring from your backup will overwrite these. Spend some time exploring these and export the factory presets you want to keep (or drag them to your desktop). If you have unused setlists in Helix Floor/Rack/LT, you can also export the entire FACTORY 1 bundle for loading into an unused setlist later. From the top File menu, select Restore From Backup... If you don't have any important presets in Setlist 1, click the disclosure triangle next to Presets and uncheck the first setlist's box; this will retain 3.60's FACTORY 1 setlist. Select the backup file created in Step 1 and click Restore Backup. Hope this helps/makes sense. Note: In a similar thread on here, it was suggested that anyone having an issue with trying update using HX Edit, should raise a ticket with Customer Support reporting details of the error. There is a possibility that this may be a bug in the update routine, and the more people who can report this, then the more chance of a fix. My ticket is already in listing the Unknown Error [code - 2004] specifically.

Done.

Hi, Five hours is an extraordinary length of time to run the update. There is definitely something not right for it to take such a long time. You didn’t say if this was while you are still connected to the internet, because it appears to me that the File Transfer Protocol is flakey, and that is why HX Edit puts up the error message. Here is the way I did the update on my Helix floor in local/offline mode. I have swapped all references to Helix to Helix Rack. First - remove all prior installations of Line 6 HX Edit - on a Mac ensure there are no aliases pointing back to an earlier version. Now go to the "DOWNLOADS" menu at the top of this page and from "- Choose Hardware -" select Helix Rack, then under "- Choose Software -" select HX Edit, now select your PC/Mac OS from under the "- Choose OS -" tab, then click “Go”. From the next page you can select HX Edit 3.6 for your Helix Rack, repeat the download procedure for the Firmware v.3.6 Flash Memory, and the Line 6 Updater version 1.27. Download all these items to your computer and note where they are. Unplug the USB cable from both your computer and the Helix Rack, then turn the HX Rack off, and then on again while holding in Encoders 1&6 while turning the power on. This will put your Rack into “Safe Boot” mode, at this point you may see a black, or error screen, but just keep going. Ensure that HX Edit is closed and reconnect you Helix Rack to your computer with a known good USB cable - do not use a hub, some front USB ports on PCs act like a hub, so use one of the ports on the back. Ensure you are disconnected from the internet, also Shut down all Line 6 software or any programs that use audio, like DAWs, iTunes, Spotify, video games, etc. If your computer's sleep timer is set relatively short, disable it, as the update can fail if your computer goes to sleep. Make sure external devices are not currently sending MIDI to Helix/HX. If you're unsure, unplug Helix/HX's MIDI IN port. Now launch the Updater Utility that you downloaded earlier, and then select "Offline Mode". Your Helix and current firmware version should now show up in the window, click on the dark green coloured band and you should now have the option to select a local file - click “Choose File”, point it at the Flash Memory file you downloaded and let it get on with the update. If you are updating from a firmware version prior to v.2.80 the installation may appear to happen twice - this is normal as the Core operating system is being modified. When it completes, you need to perform a factory reset on your Helix Rack, then you can install the new HX Edit v.3.6 software, perform a restore from backup using the file you created before starting the failed update,and you should be good to go. Please note: After you complete the restore from back up, you will notice that the next time you restart the hardware, it will run the “Rebuilding Presets” routine. This is perfectly normal as it ensures that all you older presets are optimised for use in the new firmware. Also, any time you install a preset created with an earlier version of the firmware (e.g. a preset downloaded from CustomTone, etc.), the Rebuilding Presets function will run again after the next restart - this is an expected housekeeping routine for the unit. No guarantees are given or implied, you do this at your own risk. If it doesn’t work, raise a ticket with Customer Support - you may have a hardware issue that cannot be resolved by anyone in this user forum. Hope this helps/makes sense.

Hi, It’s like using the “get out of jail free” card. All the elements that are in the payload bundle of the Firmware Update can be downloaded as separate files. It is usually used as a last resort for a failed firmware update. In fact Line 6 has the basic instructions listed here in the “Knowledge Base” area of this forum - (see link below). I, amongst several other regular users of this forum, have developed an instinct for how to deal with some general weirdness that can surface during the course of flashing the Helix firmware. What we haven’t been able to fix is user error. AFAIK, you didn’t encounter “user error”, but rather more likely some strange disruption to the FTP on the servers. Line 6 has spent quite some time trying to make the Firmware update installation process as user friendly as possible, but as we are aware, if it can go wrong, it will. Hope this helps/makes sense. Here’s the Line 6 Recovery Info. Enjoy your new update.

Hi I had this exact situation last week after logging in to my account. I'm running OSX Catalina (10.15.7) and my installed version of HX Edit detected the update and started to download the new HX Edit v3.6, but at about 70% it stopped and a message appeared on screen which said it would launch a web browser for me to manually download the editor. I did that without issue and installed HX Edit 3.6 After launching HX Edit 3.6 it detected my Helix and I started the firmware download and installation once more . Again, part way through the process HX Edit threw the towel in and popped up the message - “"HX Edit Failed to download firmware update file. Please check your internet connection and try again. Unknown Error. [code -2004]. First time this has ever happened to me, and I put it down to network traffic, or possibly a busy server. I don’t have other things open, or running in the background, while updating. Using the web browser to download all the components for a local off-line install, it did not present an issue - my internet connection was solid. Then using the Line 6 Updater, while disconnected from my local network and the internet, the installation was quick and flawless. Done, no problems! I have no idea what caused HX Edit to flag an “Unknown Error”. and there seems to be less “update bricked my Helix” posts on this update, but it is still not totally pain free. As for young Mr Cordy’s presets, the are in the update, but if you followed the procedure of reloading your back up, you will have overwritten them. Don’t panic! You can go to this thread and grab them. Hope this helps/makes sense.

Hi, A couple of things about your post confuse me. Firstly, when asking for assistance with an issue it really is a BIG help to know what your computer and OS are. I don’t see that here. Secondly, you said that you installed v3.6 “Successfully”, but other than saying that all “the new amps/effects are there”, no mention of if the device conformed to the auto restart, preset rebuilding process. It is a quite important thing for a clean install. Did you also restore your Helix from the backup bundle you made before updating. Now you have a Helix that freezes after a short period and a reboot clears this but is a temporary fix, including “all manner of factory resets” to no avail. Now what bothers me is that you said “attempted to re-install 3.60 using Installer 2.70. No luck.” I guess you actually mean the Line 6 Updater Utility v.1.27, but once again don’t elaborate on how, or what made this fail. The Updater is the failed update recovery tool. I don’t understand why this didn’t work. Filling in some of these holes in the report might help narrow down what may be causing the issue. If you have opened a ticket on this, then the Line 6 techies are going to require the same sort info in order to help you. Hope this helps/makes sense.

Hi, Prior to updating your Helix firmware to the latest version, HX Edit suggests that you make a back up of the current state of your hardware. This can be any, and all presets, setlists, IRs, Favourites etc. The back up bundle is your "Fail Safe" option. Sometimes the Firmware Update may have some new Factory Presets added, but this is not always the case. This latest version has some of the earlier factory presets modified to utilise the new cabinet profiles. The new cabinets are a kind of very special IR and are additional to the previous type of cabinet in the HX family. Anything you created using the earlier cabinet models will not change via the update, although you have the option to swap the new for old cab models either on the device or via HX Edit. Amp and Cab choices now have both the new and legacy types available to use. Any other IRs that you may have created, bought through the Line 6 Marketplace, or other third party suppliers, are totally unaffected by the changes in the Core operating system of your Helix and will be in the same slots and should behave exactly like they did before the update. Hope this helps/makes sense.

Hi, Generally speaking you should not need to download the Line 6 Updater utility, other than when you have a unit in a “failed” state, or have chosen to do a local offline firmware update. Also, avoid having HX Edit, and the Updater open at the same time. Hope this helps/makes sense.

That’s a very good point. It would be helpful to others who stumble over this. I even consulted the latest version of The Big Book of Helix Tips and Tricks by @craiganderton, but that was just as vague as the Owner’s Manual, other than using crossover for a whole bunch of bi-amping tricks, and the mixer block for parallel paths, which allows the user to determine the overall levels.

As I indicated earlier the crossover and dynamic splits are not something I have ever really messed with, but I understand why you would use them with bass. I decided to trawl through some of the older posts on here trying to find any specific references to crossover and dynamic split points. Nope, nothing really obvious, other than a comment from the guy who I pointed you to previously. He commented - “I think a new "split crossfader" block or better a "merge crossfader" parameter! would be a good addon for a new firmware”, but that was back in 2019 and nothing as surfaced thus far. All other mentions are about the 3db pan law instance. The other thing is - I was looking for split block info, but my impression is this is more relevant to the MERGE block. Plus the Merge block does have an adjustable level control. Ultimately the control is in your hands. The only way that you may get any clarification on this is to raise a ticket with Customer Support, and tell them your findings, then maybe they can explain what should be actually happening to the levels. More science, or wizardry, no doubt. Hope this helps makes sense.