HonestOpinion

So true, they are theoretically not the same thing although there was a time where manufacturers were playing fast and loose with those names(maybe still are) and some probably produced envelope filters/'followers' that were labeled as "auto-wahs" or "touch-wahs"("touch"-wah being a better synonym for envelope filter). This was done probably to some extent depending on what name they thought would sell better or be more recognizable. As you say though, to comply with their original literal definitions, an envelope filter should vary with how the string is picked or the envelope of the source signal whereas an auto-wah should vary its timing according to something like the rate of an LFO or other often internal timing mechanism. Thanks for bringing this up 'cos I don't know if various manufacturers will ever adhere faithfully to these definitions. :)

Thanks for the response. I will sit tight until instructed otherwise or a new revision comes out.

DigitalIgloo(Line6) posted this over on The Gear Page. If your unit bricked doing the new update open up a ticket with Line6, email Frack Ritchotte, or give them a call. Quote from DI on The Gear Page: We're pulling FW 2.52 until we can find out why some people (typically running older firmware) can't update. If you've run into this problem and Helix isn't playing nice, open a ticket or hit @Frank Ritchotte up and they'll take care of ya'.

Too late, already installed. What issues? I did notice there were some spots during the upgrade where it seemed to be crawling more than usual but it completed successfully. Should I be rolling back?

Thanks, well aware of this and it is nice this option is available. Good to see old posts still get read but heads up you are responding to a post from January 2016. A lot of things have changed since then. :)

LOL, corrected, thanks! That solipsist #1 must have gotten orphaned during an edit. Was not separate initially. ;)

Interesting, I wonder if the "Rebuilding..." process you see on the Helix upon your first reboot after an upgrade addresses this. Rebuilding older presets to the latest Editor/firmware format may make for a more seamless migration of presets from other HX devices to Native. I notice you mention you only have Native. That means that perhaps you did not have that rebuild applied to old presets or that it is executed differently by Native than it would be by an HX device. Perhaps that rebuilding process needs to be built into(if it does not exist already) or tweaked in Native to accommodate presets from older HX Edit versions. There are certainly a lot of legacy presets on CustomTone as well as being sold by third parties. You also might assume they need to be upgraded with each new Native version. Or... perhaps it is just as you say a "corner" case, just speculating. Update: The more I think about it the more I believe there must be some kind of rebuild process in Native although it certainly does not kick back a "Rebuilding..." message like for example the Helix does. Otherwise how will they be able to keep the presets from previous versions of Native only users (no HX device) working as they release subsequent versions of Native? I suppose there are other methods than a rebuild but they must have some mechanism for allowing new versions of Native to work properly with presets from previous versions of Native or elsewhere that have not had an HX device update them to the latest software revision.

I had exactly the same idea and precisely that concern about the harmonics triggering the processing on the wrong side of the crossover. Was going to experiment with that myself. Thanks for saving us the trouble. And coincidentally, I also have a JTV so that is what I use for 12 string passages. I will have to try it with the preset jpdennis posted above. :)

That preset is for a Variax. Unfortunately even if you changed the input to Multi or Guitar it appears that it might add some modulation and reverb but would have no way of doubling the bottom strings to an octave and the top to unison.

I would go ahead and apply the new 2.52 Editor/firmware upgrade. Don't try to download the Flash(firmware) file separately. Get a backup if you can and then uninstall all the Helix software. Then download and install HX Edit 2.52 version for the Helix floor. You can then use the Updater to update to the latest 2.52 firmware. If the Updater is not recognizing your device you can scroll down and use the reset options here to try and get the device back to as state where it is being recognized. Also all the usual tips about trying different USB ports and of course rebooting the PC. https://helixhelp.com/reset-options/

Definitely think those would be a candidate for loading up to CustomTone.

You can erase the original loop by hitting Stop (not Out/In Overdub). Then hit record again (round icon) and you will be recording a fresh loop.

Might be what you meant but just in case, you have to release the buttons after it enters the reset mode. Btw, try plugging into USB and launching the Updater after you try each reset option. Some people have been able to reapply firmware even when their device did not appear to be in a state where that was possible.

That would make the M20d mixer in particular a great deal. That mixer originally retailed for $2,000 US. Update: Sweetwater has them for $999, might be easier to buy in the US if you live in the US by the time you are done with currency conversion, shipping, taxes, and whatnot. https://www.sweetwater.com/store/detail/SSM20D--line-6-stagescape-m20d-touchscreen-digital-mixer?gclid=EAIaIQobChMI4dWmzui62QIVCVYNCh1PtA-tEAQYASABEgLBPvD_BwE

Hope these prices come to the US, they are outstanding! For anyone in Europe who has ever felt slighted by Line6 US pricing, this is a prime opportunity. Prices like this are not currently available in the US. Maybe it is a closeout sale?

They weren't really impacting me at the moment either. Gonna upgrade anyway. Never could resist a new version of software/firmware. :)

Looks like a new 2.52 version of HX Edit and a new 2.52 firmware has been released.with some bug fixes. A really fast response, thank you Line6! Would suggest to anyone upgrading to follow this procedure and of course Line6's latest installation instructions: Get backups with your current version of HX Edit just in case. I personally go overboard and get an HX Edit full backup, as well as backing up my IRs, a bundle, separate setlists, and separate presets. However the new HX Edit software only actually marginally requires the full HX Edit backup - if you don't care about updating the Factory and Template setlists to the latest it will actually do an update in place retaining all the old setlists. So theoretically you can upgrade from 2.51 to 2.52 without a backup but I still feel better having having them(highly recommended at least get the full HX Edit backup, it would be foolhardy not to). Btw, the onscreen instructions when you run the Updater also say to get backups with the HX 2.52 editor as well before upgrading the firmware. I actually exited the Updater when I saw this and brought up the 2.52 editor and got a backup before returning to the Line6 Updater for the firmware update. Don't download the Flash(firmware) file or Line6 Updater directly. Instead download and install the correct version of HX Edit 2.52 for your device which will unpack the Editor, Updter, and driver for you. Use the 'Line6 Updater' to upgrade to the 2.52 firmware. Click on the initial screen of the Updater which will show a picture of your device with your current version of your firmware, not the new version. This assumes your device is connected via USB to compatible hardware with a supported OS . Make sure you don't have the Editor and the Updater up at the same time. After you click through the initial screen the Updater will then give you a choice of the new 2.52 firmware. Just point and click and let the Updater walk you through the firmware upgrade. Follow firmware release instructions provided by Line6.

I think contacting Line6 is a fine idea. Having run into this multiple times they can probably walk you through the recovery procedure to get this back onto a Floor version of the firmware. Short of getting Line6 support my suggestion would be the following. Can the Updater see your Helix? If so, download the latest 2.50 Flash(firmware) file for the Helix Floor version and the latest HX Edit 2.51 version. Install HX Edit 2.51, bring up the Line6 Updater and then use the manual firmware update procedure and point it to Floor version the Flash(firmware) file you just downloaded on your local machine. If that works you should be able to use your new Editor(2.51) and the Updater normally going forward. This may not be what happened in your case but I think one of the ways this occurs is that people try to do an update by downloading the Flash(firmware) file as described above. Again going forward you do not need to ever download a Flash(firmware) file in the normal upgrade process; instead download and install HX Edit. Some of the only reasons to download firmware directly are special circumstances like being seemingly being stuck on a rack version of the firmware such as happened here, a bad internet connection where you need to have the file locally for the duration of the upgrade, or for archiving processes. The safest way to upgrade your firmware is always to download and install the version of HX Edit intended for your device and let it unpack the Updater, Editor, and driver for you. When you use the Updater from the HX Edit package it will automatically find the correct versions of the firmware for your device and allow you to select from them. Downloading a firmware file yourself is generally a bad idea and a recipe for inadvertently getting the wrong firmware version. Again, not saying that is what happened here but it is worth mentioning as I have seen so many posts from users who have done this.

I wonder if the Behringer model is basically the same thing as the Ebtech for a fraction of the price? I only ask because I got a Behringer cable tester a while back that was literally exactly the same as the Ebtech at 1/3 the price. They were either the same device rebranded or a perfect job of reverse engineering. Here is the link to the "Behringer Hum Destroyer": https://www.sweetwater.com/store/detail/HD400?gclid=EAIaIQobChMIxPri4Jm32QIVyIizCh0FFwm6EAQYASABEgITKfD_BwE

This might require opening a ticket with Line6 if the joystick is physically failing. If the joystick just started acting up after the latest upgrade that is awfully coincidental although not necessarily cause and effect. It might be worth taking yet another run at the firmware upgrade. I would back everything up, uninstall all the Helix software, download and install HX Edit 2.51 one more time, and then use the Updater to update to the 2.50 firmware again. If that does not work an interesting experiment might be to revert back to a prior Editor & firmware version and see if the joystick comes back. Good luck with this!

Ah, you live in NZ, complicates things a bit. Given how many Helices have been sold I have seen relatively few complaints about the joystick going bad, sorry you had to be one of them. The joystick seems to be faring better overall than I originally expected. It has always been my practice to use HX Edit where possible to extend the lifespan of all the controls on the Helix. Some users will always remain strictly hands(or feet) on though. I still think the joystick is the most vulnerable part on the Helix and personally I hope they come up with something more flush to the chassis in the next version. They did use high quality parts however overall on the Helix. It is a beast! Just my two-cents worth. I have no doubt others will disagree. Btw, if this failure started exactly after you updated the Helix I would personally back everything up, make one more attempt to uninstall all Helix software on your computer, download a fresh copy of HX Edit 2.51 again, and then reinstall and run the Updater and update the firmware to 2.50 one more time. If this started only after the upgrade that is awfully coincidental although not necessarily cause and effect. If that does not work and you have all the time in the world an interesting experiment might also be to back it down to a previous firmware version where the joystick still worked and see if it starts working again.

Bummer! I would open a ticket with Line6 immediately and then make sure i had some presets ready to go for this weekend. You can use HX Edit in the meantime to modify presets. After this weekend you can try to get them the Helix as soon as possible. They usually have very rapid turnaround times and may be able to accommodate you if you let them know when you need to have it back by for the next gig if they receive it in time to do the work.

Short of something being stuck beneath the joystick preventing it from being depressed properly this sounds like it could be a hardware problem with the joystick control. You may want to open up a ticket with Line6 for this. Does this happen on other blocks such as effects or only on the amp models? Do other operations such as selecting a setlist with the 'Preset' button and then rotating and depressing the joystick to select the preset still work? If not that might point even more strongly to a possible hardware issue. Btw, quite possibly totally unrelated in your case but worth mentioning for others trying to avoid a problem with the joystick. If you pack the Helix in a case of some sort make sure the padding does not press down too hard on the joystick or you can end up damaging it.

Excellent and summed up well, sounds like you got it, pull down the split and you get an additional Input block, pull down the merge and you get an additional Output block. :)

This is correct and just wanted to add that the Auto setting on the impedance only uses the first block in your signal chain to determine the impedance, whether it is bypassed or not. If you want a different impedance then that dictated by the first block you can assign the impedance to change in each snapshot or assign the Impedance parameter to a stomp switch.