Search the Community

Using HX Stomp, there are black boxes touching some shortcuts. Also when we are selecting category in the effects list, and we touch the fs1 or fs2 sensor, we got a black box on the screen, and covers a part of the display. Also when you enter in the tuner option and you touch fs1 and fs2 sensors, you got a question 'swap fs1 and fs2' and with any option you select, this pop up stay there mixing with the tuner screen

Twice this week my Helix Rack and Control froze and wouldn't change presets. Once during a rehearsal, and last night during a performance. Only thing that fixed it was powering off and then on. Not sure if it was same preset that froze or not. But I do know that the rack and control both read different presets. Signal was still coming through so I was able to finish song, but why would it be freezing like that? I'm on latest firmware. I have 2 Helix Mission expression pedals plugged in to control. Any Ideas? I'm using all tones I've created and maybe 1 or 2 custom patches from other people, with IR's. I've read about the "rebuild all presets" feature but not sure what that does or if it would fix this particular bug. Thanks

so I recently got a hx stomp, tried it out, everything was working fine and it was dead silent, then I updated to the new firmware and all of a sudden got this buzz noise (its attachedto this post). it goes away after some time, but comes back. I also tried different power supplies and outlets , its always the same result, does anybody else have this problem, it seems like a software issue, since it was working fine before doing the update. hx stomp buzz.mp3

What Expression Pedal works with Line6 HX Effects? I like to work with effects from 0% till 100% without any isues The Line6 EX-1 ? The Roland EV-5 Expression Pedal doesn’t do the job apparently, goes to 60%, no matter what I do. Never had problems with the classic Line6 Delay Pedal with the same Roland EV-5 Pedal is there a bug in the Line6 HX Effects about the expressionpedal topic? Seems there are more people to suffer with this topic.

I think the HX Effects 'Snapshot Mode' "Latch" option in Global Settings is not working correctly. EG: When 'Preset Mode' is set to "Latch", changing Presets keeps you in 'Preset Mode' -GOOD when 'Preset Mode' is set to "Moment", changing Presets pushes you into 'Stomp Mode' -GOOD! when 'Snapshot Mode' is set to "Latch" and 'Preset Mode' is set to "Latch", changing Snapshots keeps you in 'Snapshot Mode' -GREAT! BUT when 'Snapshot Mode' is set to "Latch" and 'Preset Mode' is set to "Moment", changing Snapshots pushes you into 'Stomp Mode' -ERGH! WRONG. BAD MULTI-EFFECTS BAD! :P This is wrong. 'Snapshot' Mode' set to "Latch", should remain in Snapshot Mode, regardless of what 'Preset Mode' is set to. I want the HX Effects to dive into Stomp Mode after I select a Preset, so I set Preset Mode to Moment. But I want Snapshot Mode to remain visible when I'm using them, which I can't do.

After over 10 hours of installing and reinstalling I finally managed to get the USB Driver to install and run. Problem: Workbench installs fine Line 6 Monkey installs and updates fine but reports no USB Driver Windows Device Manager reports corrupted or incompatible driver when usb interface is plugged in The solution: Click Start, Type Core, Select Core Isolation and run, turn off the Memory Integrity then reboot. The driver then miraculously functions fine. Line 6, please pin this somewhere as it was incredibly hard to find a solution and please see if the issue can be addressed.

When I try to set a tap tempo for an effect (say dotted 1/8 on a digital delay), I can't edit that value in hd edit and save it - as soon as I leave the patch and come back, it goes back to the previous value. I've tried to update my pod with the latest line6 updater (1.14), and it doesn't show up in the app, so I can't do that, but I am running what appears to be the latest version of it (2.26) and the latest firmware (2.62). If I change it on the device, then save it (from hd edit), then it saves. But it's kind of a pain to get the tempo exactly right that way. :/

There seems to be an issue with the Firehawk Remote App for iOS (iPhones). I am part of a Facebook group that is trying to share tones using the link that the Firehawk Remote App provides. We can all share tones via link, but it seems only Android devices can actually load the tone. The problem is that iOS devices seem to have an issue loading and go to the 1A preset. Can we have some Line6 assistance here? Thanks!

Hi, i have a new Helix HX and have a strange behaviour. I have Windows10 (newest Patchlevel) on my Surface Pro 4, Helix HX Firmware 2.60 and HX Edit 2.60. I did a firmware update on 2.60 and after the Update i do a factory reset. I build a preset (on PC) that fits 90% of things i need. Finetuning is done on my HX without a Notebook. Now thte Problems beginn (my Support ticket): So guys, any ideas? I put my Preset in the Attachements, 2 Pictures from the Device and the signal flow and one short video clip from HX Edit... Void Obelisk_090718.hlx

Hey all, Recently, I was noticing some odd behavior with my HX footswitches during live use. If I went to engage an effect by stomping on the footswitch, it would turn on, but after maybe 1-2 seconds, it would bring up the screen that allows you to edit parameters of that selected effect, and I would have to press the MODE/EXIT button to return to the stompbox layout. This would happen intermittently, but eventually, I got fed up and checked to see if I was behind a firmware update, and I was. Without issue, I upgraded both the HX Edit software AND the HX firmware to the latest version. I did not see my specific issue listed on the bug fixes, but I was still hopeful it would resolve my issue. At first, it seemed like the update did the trick, but after a little more fiddling with my setup, a new problem arose, but still quite similar to what was happening before. This time, though, instead of bringing up the screen to edit effect parameters, it acts as if I am soft-touching two effects to engage the "swap footswitches" feature. See the video below, demonstrating the issue. As you can see, I'm not using the soft-touch feature at all - simply turning effects on and off in "stompbox" mode with a normal pressure used in a live setting. My brother also has an HX and I showed him the problem, and we could not replicate the problem with his unit in the same signal chain, same room, same power, etc. Do I have a faulty unit? In the meantime, or regardless, is there some way to disable the soft-touch feature on the HX? Honestly, after using the unit for the past 2-3 months, I have never really used the soft-touch features. Thanks for any advice or support, folks.

So i have recently have had a strange bug. When i am gaming, when ever i join a party or someone joins my party my mic audio makes it sound way deeper than it was. It's like a switch almost. The instant someone joins or i join them it just make me sound like i have a "voice changer" on. If anyone can help me with this that would be great, but i just find it quite odd none the less.

Long time listener, first time caller. I picked up the HXFX recently, getting modern after some years with an HD500, and I'm happy with my decision. Today, though, I picked up a cheap M-Audio expression pedal. When I tested it in store, it seemed to be working fine - the polarity was reversed, even when I flicked that little switch on the back, but I can deal with that by flipping the min and max. What I can't deal with is the fact that switching presets renders the expression pedal totally useless! The only way to get it working again is to turn the unit off and on again - not ideal. There were loads of opinions about which expression pedal to get and plenty of it was over my head. Does anybody know why this pedal isn't working? Can anybody recommend a better one that works consistently? I've got gigs! Thanks, team!

There's a bug with my firehawk in which the tuner toggles out without me pressing any button on the firehawk. Is this a software problem? Can I get some help? I'm using the latest flash firmware too. V1.30.00

I put a Wah (Fassel effect) block in my chain. I have the block to be controlled by EXP 1, using a Mission (EP1-L6). When I pull the Wah back to heel position, the Wah effect turns on, but as soon as I rock forward the Wah turns off? These are my settings within the block: Switch > EXP 1 Position > 0% Wait > 1000ms Midi Bypass > Off Anybody else experiencing this issue? Is this a bug with 2.50?

Title says it all The HX effects buzzes loudly when the usb is plugged in and goes away as soon as it is unplugged. Which would make editing basically useless once that is available. Anyone else having this problem? Or do i need to open a support ticket?

On my iPad the test tones in the upper right corner doesn't give the option to choose a riff. I have tested anything, even clicking positions out of the regular focus. On my iPhone everything works fine. Can someone please proof this behavior?

Hey Everyone, I just got a new laptop and have tried editing my helix on the editor but I am having an issue with display/response. If I hover my mouse over a preset name and click on it it actually selects the preset above the one I’m trying to select. This happens on everything on the screen and has become a huge pain to use. I have tried changing resolution of screen and even compatibility mode in the application preferences but nothing has worked. Anyone out there know a fix? Thanks in advanced

I want to ask if someone can verify that the following happens on their Helix as it does on mine before I file a bug report. I searched for this before creating this topic, if it's a dupe I'm excusing myself beforehand. I use Firmware 2.21 . I recommend using a DAW or method B to make sure there's no additional noises coming from pickups, cables etc. Symptom: Both the SV Beast Nrm and Brt models exhibit a clicking noise after sound was processed if the "Sag" parameter is set to a value of 0.6 or greater. Steps to reproduce: 1. Create a patch with just an SV Beast Amp in it. Set the "Sag" to a value equal or greater than 0.6, the other controls don't seem to have an influence. Set the input block to something quiet, e.g. USB. Method A: 2. Connect the Helix to a DAW and use a routing with sound only going in and out via USB (Reamping). 3. Monitor the Helix' main output (Channels 1&2), e.g. by arming a track for recording. 4. Play anything for any amount of time, then stop playback. Method B: 2. Set the "Hum" value to anything that produces an audible sound, then move it rapidly to 0. For both methods, there should be a crackling noise following that sounds like static discharge going through a lowpass filter. For "Sag" settings of 0.5 or less, I could not reproduce the symptom. If someone can confirm this, I will file a bug report, otherwise I'll scratch my head. With a confused face.

Very sorry for the long post, but I truly feel it's necessary... Some might already know me from The Gear Page and it's been pointed out that maybe I should post this here in order to have a bigger impact, I'd reach more people really invested in making Helix better. Recently a couple of threads about Fuzz and Input Impedance came up, it seems a good time to push this idea forward and greatly improve our experience while playing w/ Helix. I'm a big fuzz fan. When I started getting heavy into dial in my tones, I found this problem... I dialed my Plexi tone, sounded great, then I added a fuzz face model in front of it, again it sounded great, but when I turned it off, the tone of the amp alone was gone, it sounded muffled. After asking around and some research I found that the culprit was the input impedance, more specifically, the auto setting. Input impedance influences tone and feel, it has to do with the interaction of you guitar signal and the first thing it hits on your pedalboard. To make a pedal behave on a modeler like its "real" counterpart, units use analog circuits to mimic the different input impedances you'd find in a regular pedalboard or amp. For example, usually amps have an input impedance of 1M, but if you put a fuzz in front of it, they usually have an input impedance around 10k, and that's what the guitar will see. A lot of people get confused and say that "well, if you bypass the fuzz, the input impedance is the same", but that's not exactly right. We have basically true bypass and buffered bypass, true bypass acts like there's nothing really there, signal goes straight through; buffered bypass makes the signal go through a buffer, and a buffer itself is actually an amp, and in this case the input impedance will be whatever the input bypass of the buffer is. We will ignore the buffered one. A buffer serves the sole purpose of avoiding signal degradation caused by long running cables - and it doesn't come without its own short comings, anyone that has triad a fuzz face after a buffer knows it - but because inside a modeler it doesn't happen, we can think Helix as a kind of paradise where there's no place for Bob Bradshaw, LA Sound Design, Gig Rig, Pete Cornish and a bunch of other companies, whose sole purpose is to make sure your guitar still sounds like your guitar after going through a metric ton of cables and gear. We'll assume everything is true bypass, because, as we don't have to worry about signal loss through cables, that's the best option, no question about it. Back to input impedance. Everything being true bypass, that means it's going straight through, so the input impedance the guitar sees is of whatever is the first block that's actually on! Going back to my example. In this ideal world, what should happen when I bypassed my fuzz? Signal would go straight through and would see the input impedance of the amp! Turn the Fuzz on and it sees the input impedance of the Fuzz Face! Nice!... Except it's not what happens in Helix. The auto setting doesn't search for the first active block, it goes for the first one, being on OR off. That's why it sounds different! When I turn the Fuzz off, Helix isn't changing the input impedance, so the guitar still sees the low input impedance of the Fuzz Face, making the amp sound just muddy, muffled. Tha auto setting as it works right now is doing pretty much nothing useful. Why? Because what it does is fixing the input impedance to whatever effect is first. If you have a compressor first, impedance will be fixed at 1M, as long as you don't change the signal path, specifically the very first effect, impedance won't change. But nobody changes the signal path while playing, so it's not really useful. Takes away the guess work to find the input impedance of the first effect, but by fixing it, makes everything that goes after have the same input impedance, making the models not nearly as accurate as they could be if the input impedance was set properly. Fixes? Two main ones are usually proposed. After a few FW updates since release the input impedance went from a global preset to the input part of every preset, great! It also can be assigned to footswitches?! GREAT! But it only works for very simple cases. It would for just fuzz-amp. I'd assign the input impedance to the footswitch that turned the fuzz on and off and make it change the input impedance from 10k to 1M. Good! But it doesn't work that great when you put just another pedal in. Let's have Fuzz-Tubescreamer-Amp, all three input impedances are different; when playing the amp it would be 1M, turning the Fuzz on would make it 10k, but now if I turn the Tubescreamer the impedance should not change, but if we assign the input impedance change to its footswitch, it will do just that. But then snapshots came and had to be it, right! Not exactly. By itself it works, but it's extremely limiting and you take in consideration the combinations of pedals I could have using the stomp mode. I'd need 4 snapshots to deal with the fuzz-ts-amp case and set the impedance accordingly, that's not really practical - and the stomp mode is still crippled. Isn't there a definitive fix? You guessed, fix the auto setting of the input impedance. If after everything I said you don't believe me, here's what the competition has to say about this: From http://community.avid.com/blogs/avid/archive/2010/04/06/the-truth-about-true-z.aspx (and a great read if you want to understand what input impedance actually does. Spoiler, it's not about bypass) "Typical guitar modeling processors have a fixed input impedance, which can limit the accuracy of the modeling. Eleven Rack's True-Z circuitry is designed to solve this problem by automatically changing the input impedance to closely match the impedance of the first active effect in the Eleven Rack signal chain." From http://www.fractalaudio.com/downloads/manuals/axe-fx-2/Axe-Fx-II-Owners-Manual.pdf "The Axe-Fx II recreates this effect by switching various (real) resistors and a capacitor in and out of the signal path. In Auto mode, the impedance is automatically set based on the first active effect the input "sees." Normally you will want to leave this on AUTO..." Here's the link to the ideascale where I proposed the auto setting fix: https://line6.ideascale.com/a/idea-v2/862873 Vote up!

Has anyone been experiencing the problem I’m having? I've had this problem since purchasing the unit with it hanging for seemingly no reason and at odd times. I updated the firmware whilst following all of the instruction and holding my mouth in the right position and all that. After the update it seems to work for a while and now it hangs several times a playing session. The scenario goes like this: I’m playing along having a good ole time and I go to change a preset or parameter and all the controls are inoperative. Only solution I’ve found so far is to power cycle the unit. Luckily I haven't had this issue live because I’m not playing live at the moment. If I were playing live I would not count on this unit as of right now. I love the sounds and ease of use otherwise! I like this unit way better than the Axe FX for ease of use but not for reliability. The Axe FX was solid as a rock in terms of glitch free. Anyone else having this issue?

Is anyone else experiencing this issue? I'm on a patch and then change to another patch and the unit hangs. The sound still works but all of the buttons are inoperable and the helix control floor unit does nothing. I had the same problem in 2.10 but now it's worse. Not Going to take this thing live with this kind of stuff happening. I had heard that Pete Thorn went back to his pedal board setup alone without the Helix. I wonder if it was because of little issues like this. Anyone else experiencing the same problems?

Hello everybody! I'm having a strange issue with recording to my PC using the POD X3 Live with Asio (both ASIO4ALL and X3 Live ASIO) plugged in directly to it. When I record every sound, including clean/distorted/chorus etc, I got a very dirty sound which isn't what I'm hearing from my headphones. It's a low dirty/crackling sound but it's there and I hate that. On distortion it gets even worse. I thought it was a problem of drivers or firmwares, so I downloaded the Line6 Monkey tool to upgrade software stuff but it was everything up to date. So I tried to mess around with ASIO's settings but nothing worked. I recorded a clip and I'm attaching that to this post, so you can hear what I'm talking about. My PC specs are: -AMD A8-3850 -8GBs of DDR3 RAM Of course every driver was installed, reinstalled and updated to the latest version. What can I do to fix this? In previouses recordings I've never had that! Sorry for my bad english but I'm italian, I hope I said everything quite clear :P untitled.mp3

Hi, Whenever I adjust certain settings on the pod, the little bar thing adjusts up and down but I don't get numbers to show the amounts. Things like Gain/Distorion on the pedals work, but the Low Cut on the amp settings does not show me the frequency and there are various other controls that don't show a number when adjusting the control, it just shows the bar going up and down. It used to show it ages ago, but for a long time now it's not visible. Is there a fix? Anyone else experienced this?

Once I updated my Macbook Pro late 2013 to MacOS Sierra 10.12 the UX2 usb audio interface crashes the computer. Everytime I plug in the ux2 interface, the computer immediately restarts and gives the error message (white text on black background). I have tried both of my Mac's usb slots, tried taking everything off of the interface (monitors etc.) and tried it with and without power cable on my computer. Also, when I try to start my computer while the UX2 is plugged in, the Mac's starting screen has some white error messages and then the computer restarts. Nothing helps. So atm I CAN'T USE THE INTERFACE AT ALL. Pod Farm software doesn't seem to have any problems. Please tell me if you've had these problems or you can help.

Is it me or is this so "hard"? I don't know much about the Maestro® Echoplex EP-3 that the tape delay is based on but the Transistor tape delay can't do the trick below. And some pedals do an OK job at. The real thing. A mod of Univox EC-80A Fractal does a respectable job. Not great but controllable: Unlike the transistor tape delay (apparently) the new "vintage" delay, inspiration unknown to me does some pitch changing when changing the Speed. But it's very chaotic. Why don't either one of these work as they probably should in this respect? Would we need to have to have another model of a modded EC-80a for this cool effect? Or am I missing an existing capability? ALSO an Editor bug? On my 2.0.0.1 Editor the Mix parameter is missing on the Vintage delay. I think a bug?