codamedia

When a loop is set to 50%, that IS creating a parallel path. Set it to 100%, then solve the tonal difference that you are mentioning. @CraigGT provides great advice above. Make sure the LEVEL of the Loop in UNIT A is set the same as the I/O of UNIT B. Both need to be instrument, or both need to be line. IMO... I wouldn't bother with the loop at all. Why not just run one unit into the other? That would eliminate one unnecessary AD/DA conversation.

^^^ this ^^^ is my solution. It is easy, it is cheap, & it works! Simply add a 10K resistor across the open or closed output of a switch... it then mimics a Line 6 EXP in "Heel down/Toe down".

@z3albw1rr... it sounds like you have the "send/return" setup as a parallel path yet you appear to want a serial setup. Double check those "send/return" parameters to make sure you are not blending the two signals. To test this... run the HX Effects unit back to back (not in the loop). If the phasing disappears... the problem is in the loop parameters.

Most "template presets" are about the routing and/or pedal assignment, not so much the tones you might stumble on. The titles are usually self explanatory... if you don't understand what is said, maybe you just aren't familiar with that term/technology? The nuts and bolts of the template may have to be deconstructed (eg: which loop is used in the 4 cable template) but the title is still self-explanatory.

Actuators pushing on microswitches... it's not a new concept. First time I saw that was on my old ROLAND FC Controller for my GP-8 n the 80's. ROLAND/BOSS has used them ever since in their ME and GT lines. Line 6 uses the metal toggles for actuators instead of the plastic stomps BOSS always had... many have since gone to the L6 style actuators including Kemper, Fractal and BOSS. I think people just become disappointed when they open it up and realize those are still actuators, not genuine footswitches.

From that list the QSC K12 .... If you decided to make the Yammy or EV a 12, I might consider those as well for the price differences, but not the 15" versions.

Although I had recently seen the video you posted, I wasn't aware that the sensor was a wide spread problem. Thanks for pointing it out, I'll keep that in mind should my EXP die.

Compare is a handy feature when a unit provides it, but it does require a lot of reserved resources. I've always just made a copy of the preset I am working on... and reference it as required.

That was a physical problem where the bracket in the LT would break and the EXP had nothing to pivot on. That's very different from what you are describing.

Known issue? I doubt that or none of our EXP's would work. Possible hardware failure, or a misconfiguration somewhere. IMO, the easiest way to test the expression pedal is to create a blank preset and add a volume pedal block. It auto assigns everything so you can't make a mistake. If the VP works, the pedal is working. A factory reset is always a good troubleshooting technique for something failing. Make a backup then do a factory reset. Restore backups as required. Failing all of that, open a support ticket with Line 6.

I understand the reason to the fullest, but I sure wish this was an option for "power users" to engage in the global settings. I know I've upvoted a few feature requests for this.

Like the OP, I'm not a fan of the new ballistics. A true bug would effect everybody... yet my Helix LT and my Stomp don't have any issues with the ballistic update. I think this update has exposed encoders that are not 100% healthy. You'd rarely notice a glitchy encoder at the slower speeds because the jump would be so small, but at the higher speeds the jumps are huge and unmanageable. It would be nice if the ballistics were an option in global settings... so people could revert to the old ballistics without downgrading their firmware. Tier One support is always a canned response. Escalate it to Tier Two and you'll get someone that actually reads the problem and tries to understand it. Like you, I tend to troubleshoot an issue before opening the ticket. Responding to the tier one answer politely but forcefully has always worked for me to escalate the problem and actually get a solution... or a confirmation of a bug they are working on.

I've had nothing but successful updates, but why do you want to hear from me? You solved your problem... that's why support forums exist. Plus, anything mentioned here is also addressed in release notes, instructions and documentation. Isn't that a beautiful thought. We never notice how many times things work until the one time it doesn't :) I just spent 4 hours the other evening recovering from a failed OS update on a Windows computer, and I've had more than one bricked iPhone and Android over the years.

The HX Effects should be very quiet when using ins/outs, some people have problem with noise in the loops. Test the HX Effects all by itself to see if noise is there. That will tell you if the HX itself is the problem, or if it's a compatibility issue with the other effects. If the noise is only there with other effects, try changing the "last pedal" to see if that makes any difference. I'm not saying you have to change your effect order, I'm simply suggesting this for the sake of troubleshooting.

I liken that to the layout view... Helix (and almost every other modeler/multi-fx) display a layout from (input) left > right (output) Look down at a traditional pedalboard and it's almost always built (output) left < right (input) Does it matter? Certainly not to me.

I just want to clarify this a little... With the bigger units the options are there, but there is no real "all input" option. MULTI only includes guitar input and variax... you have to choose the others independently and no other input works on the tuner when you do unless a recent update has changed that. But yeah, I just picked up a stomp as a backup and I don't see any way to even choose a return for the tuner.

There are a few considerations when connecting two expression pedals to the Stomp with a splitter. Look to page 5 and page 42 of the manual for more details. Page 5 Page 42

If you use a DAW, turn off input monitoring... If you don't use a DAW, I suspect there are audio settings in the OS that create the same problem. To test if it's the Helix or the computer... simply unplug the USB cable. If the unwanted reverb goes away the problem is in the computer, look there to solve it not the Helix.

Well... I don't do any shows without a backup, never have, never will. Even a $50 fill in gig. I've always carried two amps, at least two guitars and several cables. I could care less if I lost an effect or two on a gig. These days two modelers instead of amps... Knock on wood, I've never needed the backup. You read about it here because this is where people come when there is a problem. What you don't read here are the thousands of views of users happily chugging along with no reason to lodge a complaint. I have read your posts about the service techs and I feel for you. That's not right, especially handing something back in worse shape than when you took it there (stripped screws and such). I also keep loading your backup whenever I can to see if I can ever duplicate that bizarre "mono/stereo" bug you are encountering. I don't disregard it... I just can't seem to repeat it - probably because I can't let my Helix sit long enough with your settings loaded. I also get your point about buying a "lemon". It's never fun when you end up with one but we have the term "lemon" because it inflicts any product and product line. You have a lemon Helix Floor... I have a lemon of a car, and a lemon of a dishwasher - both makes/models that normally get great ratings. I give the 1 star when everyone else is giving 4's and 5's. Don't get me wrong, I have my own list of dislikes with the Helix... I just don't believe it's any better or any worse than other major products in terms of reliability. The grass is not always greener on the other side.

IMO... I have no problem with the road worthiness of a Helix - and I use the lightweight LT. I'm 4+ years in with my Helix and I use it all the time (100+ shows per year). Yes, I do have a couple footswitches that need attention but after a few years I consider that general maintenance, not a catastrophe. My amps (when I used them) required service far more often than this. You gave BOSS a pass earlier in your post but FWIW, I have never owned a BOSS product that didn't use micro-switches for foot switches. Maybe the GT-1000 is different, but any product prior certainly has. I've got bags of different (Boss/Roland) microswitches in my parts bin... you can't tell me they don't fail. That's OK, I expect to do maintenance on the parts I stomp on thousands of times!

That's what I've been using for the past 4 years. It's been great. I much prefer a unit that uses AA batteries over having them built in, and I also like to be able to choose my frequency, not have a unit attempt to automate it in an ever changing environment.

It's a really easy and elegant solution... I've been doing that for too many years to count. Long before Line 6 existed let alone the Helix. FWIW, On the Helix I run a volume pedal all the time... I just drop it to heel down when I switch guitars. Much faster than waiting for the tuner to engage.

IMO... I would expect that to be intended behavior of the MIDI protocol. If an external midi device is not running (eg: song/part not being played) I'd want full control of the tempo on my Helix - so reverting back to global/snapshot/preset tempo (depending on choice) on song stop makes sense to me. If it didn't work like that, your Helix clock would always be controlled by the external device... which I think you would find very annoying.

I'd say put it on a analyzer to see what's happening... your ears and mind are biased even when you try not to be. Another option is to simply have someone else switch out the power supplies randomly so you don't know what is used... ie: a blind test. I'm not convinced you are hearing what you hear.... digital devices usually crunch numbers or they don't. But my mind is open to the possibility.

Let's keep it in context.... you bought a USED Helix where the seller told you the expression pedal DIDN'T WORK! You got lucky that it worked at all when it arrived. A bug update is not likely to fix your problem... having the expression pedal fixed is more likely to work. Don't get me wrong... I know bugs exist. But think about it.... this is being described as a hardware killing bug yet it only affects a small handful of users? The encoders mentioned here could be explained by the "encoder ballistic" change in 3.5. Not that 3.5 killed the encoders, it is simply exposed the failing ones. Your pedal is not in the same camp.... it was failing before you bought it, and the seller told you that. I'd be looking for a dirty sensor or a faulty ribbon connection. Both are quite common in electronics. The sensor in the LT is particularly exposed compared to the Helix floor... sunlight from the wrong angle will cause headaches and I know that from several shows over the past few years. If the SUN can see the sensor... dirt, dust, grime can see the sensor.