Leaderboard

To the user group as a whole. (A small rant) The intent of this group is to help each other. Sarcastic, inflated, offhanded comment do not help anyone. I've been a member of the line 6 forum for 13 years. I stopped using it for years because of this problem and because of just a few people. Now that I've purchased the Helix floor, I've been using the forum again. The Helix, to my admission it is very powerful and can be confusing and I needed guidance. We all have question and get confused by the equipment, processes, and programs. Some of us have more experience with PC, some with other skills. So if someone asks a question that has already been asked (or we think is stupid) then politely point them to the correct thread. I teach Mainframe Security for a living and the only stupid question is the one that isn't asked. If they are confused about something help them in a nice way. Trashing and trashing is not helping anyone. Some people learn by reading, some by seeing and doing. Some lucky few can do both. As much as I like Line 6, we paid for the hardware and software. We should expect Line 6 to fix problems when we discovered and reported by proper means. We also have to understand Line 6 has to collect, research, test, prioritized, correct, and build a new modification release. If the software release for the Helix was crashing, Line 6 would be freaking out to create a fix. So we have to have a little patients. Also Line 6 does use these sites to their benefit. This reduces the need for Line 6 to staff their help desk. Software can and does have problem. The number of defects after a software release reflects on the degree of testing done before being released. Also a very important point, there are so many ways to use and stress the Helix as per hardware / operating software. Due to this versatility, we can and do create new creative ways to create bugs. In some ways we're spoiled. In the old days we had had 5 stop boxes if you were lucky and rich. Vol, Compress/Distortion, Flanger, Chorus, Delay/Reverb. We spent more time playing the instrument. Now our processors are so powerful and many of us are geeks we seem to be spending more time playing our processors. (one thing to remember is "everyone has an A$$, but you don't have to be one" Have fun, Playing, tweaking, do both, be nice and help each other out. Happy holidays and stay safe.

What you haven't mentioned is trying any other guitars besides the Variax to see if the problem persists... in two seconds you'll know if the Helix is the problem, or not. Variax guitars are this close to being too complicated to get out of their own way, and notorious for sudden odd behavior, particularly piezo failures, which is especially likely if the problem occurrs (or is most noticeable) on only a couple of strings. Plug in something else and see what happens... I'd bet money that this is a Variax problem, and has nothing to do with the Helix.

Horizon Drive -> Solo Lead OD -> York MES 212 V30 = end of quest for metal tone. ...for now...

Not sure what happened to the link, but you can download Line 6 Updater here: https://line6.com/software/ Just leave the first pulldown blank and select Line 6 Updater from the middle one.

Glad it’s sorted out. Enjoy!

You need to update HX Edit to v3.0. Seems you updated HX Edit to v2.92 after updating your HXS firmware to v3.0. That's the problem - they need to both be at v3.0.

It might, and it might not. Variaxes are weird instruments. Data is being transferred in both directions via the VDI, and there's complicated switching within the guitar itself between the mag pickups and modeling engine, A/D and D/A conversions happening all over the place, and the hiccup could be anywhere. And none of that crap goes on with a normal guitar. It is conceivable that whatever it is, is originating in the guitar itself, or that it's some odd communication problem between the Variax and Helix. I'm not saying that this is definitely the case... merely that it's a possibility. And until it's ruled out, a possibility it remains. If I'm wrong, so be it...but plugging in something else is free to test, take two seconds, and it just might save you the headache of trying to fix something that ain't broke.

Hello, my first post here. THANK YOU VERY VERY MUCH Just came across the same problem. SD-Card removing fixed my launching problem with 3.0 HX Edit. So, . .. ... PLEASE PLEASE FIX THIS HX Effects is such a wonderful thing, best wishes, Thorsten

Yep, seems that 3.0 fixed it for me too.

So, Helix Native 3.0, first time load just fixed ALL of them. I have access to all my old presets again. Definitely a strange upgrade problem somewhere on a previous update.

Maybe. Just because it hasn't happened since, doesn't mean it'll never happen again. I know, kinda sux not being able to nail down a problem with absolute certainty. Such is the nature of complex systems. That's why I said to open a support ticket. They get paid to deal with the unexplainable weirdness.

I am using a Windows 10 Enterprise OS system. After years of updating with out any failure this finally happened to me yesterday. I do not use usb hubs, I do have the connection on the usb port closest to the power supply, etc. However without any previous updating issues up to and including v 2.92, I have been using a usb extender cable for ease of access due to how my desk area is setup & the metal box is set in a desk cubby hole... yep. I am lazy that way. My solution was to remove all the remnants of the 2.92 install and the 1.92 & 1.93 drivers; then i installed HX Edit v3.00 fresh. Then I rebooted my machine and after the third time of following the instructions I am quoting from datacommando's post it worked perfectly using HX Edit itself. Looks like I am going to stop using the usb extension in the future. Of course once my re-fi closes on my current home and I purchase our retirement home in Tennessee I will be buying a new laptop as my old one of 12 years finally bit it; its true. Happy trails all. And hopefully this thread has now covered about every issue new (and some of us older) users have ran into. Dennis

Yes. If you want to switch from a preset that uses a cab/IR on the "Flat" setting to a preset without cab/IR that uses the Jarvis (Jensen) you'll need to walk over to the PC112 and change it manually.

This is the solution, thanks!

Wrong forum. This is where you go if you're serious about suggestions for changes and improvements: https://line6.ideascale.com/a/index Before posting a new idea, please search to see if it's already been proposed. If 100 people vote on the same idea presented 20 different ways, it looks like only 5 people care about it! Also, post your ideas one at a time. I for one NEVER vote for multple combined suggestions.

Hi guys, @samrichardsam You could download the version 3 Firmware "Flash Memory" to you Mac and use the Updater to perform a Local File Install - just point it at the Firmware file, click "Update" and let it get on with it. See "Choose File" button in your Updater screen shot. Otherwise - read on! @marcofiorini No need to report to Line 6, because so far, everyone that I have pointed to this information has managed to successfully perform and update to version 3 of the Firmware. This is the official Line 6 word on how to fix a failed install which was posted in the Knowledge Base section of these forums. IMPORTANT! In the unlikely event that your update fails, please follow the steps below: Unplug the USB cable from both the back of your Helix and the computer. Turn your Helix/HX device off and on. Reconnect the USB cable to your Helix/HX device and the computer. Download, install, and launch the latest version of Line 6 Updater. In a failure state, the device will not connect to HX Edit. Line 6 Updater for macOS: https://line6.com/software/readeula.html?rid=9831 Line 6 Updater for Windows: https://line6.com/software/readeula.html?rid=9832 Select your device and try updating to the latest firmware again. If the device does not show up in Line 6 Updater after these steps, try a different USB cable and/or USB port. If it still doesn't show up, try a different computer. The full update process is described here. Hope this helps/makes sense

That's not a good yardstick...be it modeled or a real amp, I wouldn't expect any acoustic guitar to sound anything even remotely pleasing through a Plexi. Plug that Taylor into anything but a dedicated acoustic amp, direct to a PA, or a patch designed specifically for an acoustic tone monitored through some kind of FRFR output, and you'll get that same thin, craptastic sound. You've tried one guitar that relies entirely on fancy tech to function, making it prone to weird quirks and problems, and an acoustic. If you really want to troubleshoot this effectively, you need to beg, borrow, or steal a "normal" fully functioning electric guitar and see what happens. Otherwise there's a good chance that you're chasing a problem that doesn't exist.

Just did a quick test with some wires connecting the 2 MIDI ports, and it does indeed work, in case anyone else is curious.

Cool, thanks! I'll have to buy a MIDI cable, then. Have a nice day!

Looks to me like there might be a problem with the Line6 driver. I would uninstall HX Edit and download and reinstall HX Edit 3.0 leaving all the checkboxes checked. This will reinstall the Line6 driver. Then try either updating the firmware from within HX Edit (click through the link with the icon at the bottom of HX Edit), or try again with Updater and see if it is recognizing your device. Also try swapping your USB connection and cable as well as rebooting your computer. Btw, make sure you don't have HX Edit and the Updater on at the same time.

One thought is perhaps something has changed in your global settings. I know you said you already tried restoring but if you took a backup before you upgraded it might be worth trying a restore again of just your global settings from that previous backup before you started having issues . You can uncheck everything else in the restore from backup dialog box and just restore your globals. Sounds like you tried multiple guitars already so it is probably not cabling but I would make sure everything is plugged in tight including headphones and swap out cables where you can. Make sure you have a fresh battery in the Taylor. One area people have had issues is the global setting for the expression pedal changing(e.g. snapshot, preset, global) after a firmware update. This can profoundly impact a preset's sound particularly if the volume block was placed early in the signal chain. Btw, although it is located in each preset the 'Variax Settings' parameter is actually global. Unless every one of your Variax presets was the same previously, go to the Input block of any Variax preset, then go to the second parameter page and change the parameter 'Variax Settings' = "Per Preset". This will affect every other preset for your Variax and restore your custom settings in each preset for the Variax. Not sure I follow what you mean here, can you shed a little more light on your statement above - " I've reset the Helix to factory and tried importing my patches again (which is another problem as it seems that every patch is loaded exactly the same despite being saved separately with according names)". This makes it sound like you may not have successfully saved the presets you dialed in to your satisfaction previously or that they did not reload properly.

Further to my previous post: This is not a new problem. People have been reporting this since forever - I got my Floor in 2016, so at least that long. Actually, it used to be more common, and whether thru specific coding or random elimination when other things were changed, it's become less commonly reported. Also, it's not specific to the Floor, it happens on my Stomp, too, and has happened less thru the updates since I got it (Stomp is also on all day). Or it could just be my imagination that it's gotten better, and it's so random.....IOW, while it COULD be a temperature problem, it would be specific to the components in OP's box, and if it was a bad component, it would almost certainly have to have gone bad concurrent to 3.0, or he would have noticed the problem in 2.92. OP mentioned the symptom of the audio turning to noise before fizzling out. This happened on mine very early on. I sent it in for service since I was getting random noises over S/PDIF, and they replaced "a couple of boards". It never did it again. I'm with phil_m. Open a support ticket! Even if you don't have a receipt, if L6 thinks it is a manufacturing defect, they might fix it anyway. They're really good like that.

Btw, thought I would be remiss not to ask if you had tried testing this with headphones to see if the sound is lost there as well. I have had more than a few powered monitors or PA speakers exhibit this behavior where they work fine for a while and then one of the boards overheats and it cuts out. May have already but I would eliminate my monitors as a possible source of the issue.

No luck with Logic. Thanks anyway for the suggestion. I've opened a ticket with Line 6 and we'll see what happens. Cheers, Keith

All of the above is correct, but apart from line6 reading this forum or not, the request for deleting won't be take in consideration anyway I guess. First, there's no point in "deleting" blocks, like you cannot delete presets, it's not inherent from a computational point of view. And if you mean "deleting" in order to free up space for adding blocks or blocks types, well, this is a Pod, and it's quite cheap, for a reason. If they'd allowed more freedom (i.e. a second DSP) the cost would had levitate and it would have been an helix series efx, not a pod. The design of this machine is meant to be simple. If you feel like being limited by the pod go, maybe it's not the gear for you, and you should aim from a helix stomp or another hx series unit.

Jeepers, Line 6. Would you freakin' just fix legacy Workbench for your users?

I'm getting the same error message code 8312 when trying to import new presets designed for the Helix v2.50, I then updated my Helix to v2.54 and it still is not loading. The error refers to a missing model which should be included in the updates. Anyone know what else I can do. Life should not be this difficult. Thanks for any suggestions.

Back to the basics. Have you tried a different web browser? You may also want to check your browser plug-ins to see if they're up-to-date. Sounds like a browser issue to me.

well a spring reverb on an old tube amp was mono so it makes sense to have mono available

That's incredibly rude. They JUST released this firmware. There are ALWAYS bugs in new software/firmware releases - it's impossible for there not to be since customers always do things that are slightly different/unique from what the QA teams and developers test, no matter how thorough and rigorous their testing is. Give them a GOOD length of time to assemble and finalize a list of bugs with highest priority/shortest release time and then to actually solve the bugs, test all bug fixes. retest EVERYTHING since most bug fixes touch on code outside of just the single item being fixed, and then deploy it. Bug fix releases typically take a long while to come out, and they can't fix everything in every situation, specially so if they can't reproduce it. Also - please submit your bug on official channels since it's possible you are the only person who has encountered it so far... and certainly you'll be one of the first. It could even be the position of your acoustic sim pedal in the virtual pedalchain, such as before a compressor or whatever (just an example, not saying that is it or that a compressor would cause the problem).