rd2rk

Set FS1 to PRESS/HOLD in all 3 Snapshots. In SS1, make FS1 PRESS = SS2. In SS2, make FS1 PRESS = SS1. In BOTH snapshots 1/2 make FS1 HOLD = SS3. In SS3 set FS1 PRESS = SS1; FS1 HOLD = SS2. One switch controls it all in all 3 snapshots. DON"T use a separate switch to perform the toggle within the snapshots. SS1 A=ON;B=OFF SS2 A=OFF;B=ON SS3 BOTH OFF Example attached. FS 3way Toggle.hlx

Use Snapshots wisely. Use MIDI. Assign switches on a basic MIDI controller to the simple ON/OFF functions and use the Helix switches for the more complex stuff. Don't make every preset a "kitchen sink".

Same way you toggle any pair of effects. Assign them both to the same FS, then SAVE the preset with one ON and the other OFF.

What's all that "System Exclusive" stuff? All you should be seeing is PROGRAM CHANGE (Channel 1): 48. If all that stuff is hitting the HXS, who knows what it's doing? It's possible to overwhelm a MIDI device with extraneous noise messages.

Working fine for me. If USB MIDI is ON and MIDI PC Rx is set to USB, and both the MC3 and HXS are set to MIDI Channel 1, connect the MC3 USB to your computer and use a MIDI MONITOR to see what's being sent. If you don't have a MIDI Monitor, you can use this free web based monitor: Disaster Area Designs MIDI Monitor

Since the factory reset didn't work, try re-installing the FW. If that doesn't work, contact support. This is a known issue and they may have a solution, even though it's out of warranty.

Messed with this on my HXS. It appears that the NAME and COLOR are linked to the FS itself. Using a FS to toggle FX you get a choice of DIM or BRIGHT and one name. That's it. I also tried using a snapshot, but the color and name always reflect that of the destination snapshot, not the current snapshot. You could name them opposite of what they are - the Simple Delay snapshot named Vintage Delay and vice versa, which would get the labels right (current effect), but you still need to use two colors - you can't get the same color DIM/BRIGHT. EDIT - the way I get around this is to use a toggling FS with the label as either/or - VINTAGE/SIMPLE - Vintage would be DIM/SIMPLE would be LIT. You're still stuck with one color though.

Not AFAIK, and it changes with each FW release.

Guitar>HXS>pre NAM processing>SPLIT A/B PAN B100>USB 3/4>DAW/NAM/HX NATIVE>USB 1/2>HXS Main Outs The SPLIT/B100 PAN prevents the pre signal hitting the Main Outs until after the DAW/NAM NATIVE (or other ITB post processing for reverb etc). Fewer conversions, less latency. Here's the preset as example. Been doing this with plugins for years. Still too much latency, but after a while you'll realize that whatever ITB amps you're doing this to be able to use aren't all that much better than the HXS amps, and with captures you're just letting someone else create your sound. Maybe that's just me, whatever floats yer boat etc.. Plugins w_FX.hlx

To do this you need to use a snapshot. EX: In SS1, set an IC (Instant Command) to EXT AMP and the state you want when the preset loads. For this example I set it to NONE which should load CH1. Set a FS to SNAPSHOT 2. In SS2, set the IC you used on SS! to EXT AMP RING. This should switch to CH2. When using an IC for EXT AMP you don't get the LATCHING/MOMENTARY option, LATCHING is the default. Set the FS to go to whatever SS you want to go to from SS2. The easiest way to do this would be in SS1 PRESS = NEXT; SS2 PRESS = PREV. However, if you want to go to another SS, either with that FS or another, just be sure that the IC in that SS is set to either EXT AMP NONE or RING. To test this, attach a continuity tester to the RING and SLEEVE of a TRS cable and toggle the FS. I've attached the example preset I created for testing. It was created on a Helix Floor but should load on your HXFX. micogit.hlx

Android. No standardization between makers/models. One works, another not. Contact support or look for a cheap used iPhone or iPad.

In order to use MIDI over USB you need a "HOST" device - an intermediary that translates data for USB transmission. This can be a regular computer, an iPad or even an iPhone - Androids probably work too, but I don't own one so I can't say. There are also dedicated HW HOST devices such as this: Amazon.com: CME H2MIDI Pro Compact USB Host MIDI Interface | Router, Filter, Mapper, 32-Bit Processor, Dual Power Mode, Minimal Size, For Guitarists & Producer : Musical Instruments The CME is plug'n'play. You'll need a USB A>USB C cable. For a computer or iThingy you'd need a program/app that routes the signal from one device to another. On my iPad I use AUM, on my computer I use MIDI-OX, but most any DAW will also work. If you've got an older iThingy you might need a USB A>Lightning cable. On your HXFX, Go to GLOBAL SETTINGS and in MIDI/TEMPO enable USB MIDI. ASSUMING that the Valeton is capable (I didn't read the manual) you should be good to go.

Unlike some other devices, the Helix Floor/LT/Rack allow any preset to be placed in any slot. There are 8 "Setlists" which are simply "BANKS" of 128 presets. Backup the Factory setlists if you think you might need those presets, then copy a BLANK SETLIST over the FACTORY setlists and you've got 1024 (8*128) potential preset locations to use any way you like. If you need to quickly get from a preset in SETLIST 1 to a preset in some other setlist, use MIDI.

"Performance" is not a term that's used in relation to the footswitch actions in the Helix series. Noe of what you're saying makes any sense at all. Maybe a specific explanation of what actually occurs when you press a "not highlighted" switch? Your video link doesn't work, so... EDIT: If you have the preset on your LT, attach it to your reply.

There's no new version of the HXS, and no announced plans for one. The Stadium is $1800-$2200 depending on the model, and not as small as the HXS. Thru latency with HXS is <>3.5ms. If your only criteria is NAM, then HR might be the way to go, but I have to wonder how you're measuring the HXS/iPad latency? I can't feel the difference 3-4ms makes, but some people are just more sensitive to latency than others.

This is a user-to-user support forum. Nobody from L6 hangs out here. Also, the Helix/HX series is nearing EOL with the new Stadium series release, so it's not likely that any major changes are going to be implemented. That said, both ToneX and NAM apps have very nice post processing FX (modulation, delay, reverb) and I really don't think you'd gain much using the equivalent HX FX. TBH, your best bet for ToneX is to look for a good deal on an OG ToneX Pedal (the big one). That's what I use, in the HXS FX Loop. There should be lots available now that the ToneX Board has been released. As for NAM, Genome runs GREAT on my iPad and has great FX.

Use HX Edit to back up your Presets. then perform a Factory Reset. Line 6 Device Factory Reset Procedures | Line 6 Knowledge Base If that doesn't work, contact support.

I've found the same. It's all good! If it SOUNDS good, it IS good!

What you're missing is that in order to remove the physical amp's preamp section from the signal chain you need to BYPASS the FX Loop Block. For instance, to compare the HELIX AMP MODEL to the PHYSICAL amp you assign both the MODEL's Bypass and the FX LOOP BLOCK's Bypass to the same FS, then SAVE the preset with one ACTIVE and the other BYPASSED. When you press the FS it TOGGLES between the MODEL and the PHYSICAL AMP. Three things to keep in mind: The FULL amp model contains a simulation of the PHYSICAL amp's POWER AMP. That means that you're putting a SIMULATED power amp through the PHYSICAL power amp. An AIAB contains ONLY the preamp section or includes a modified version of the power amp for flavor. The Helix PRE-AMP versions have significantly less OUTPUT LEVEL than the FULL versions. The SPEAKER IMPEDANCE CURVE (the modeled interaction between the PHYSICAL POWER AMP and the PHYSICAL SPEAKER) is contained in the POWER AMP section of the FULL MODEL. This affects FEEL, and is, again, doubled into a physical amp's RETURN. It might be weird, or you might like it. Just something to consider. IOW - to emulate how an AIAB pedal works with a physical amp, you would place a Helix PRE-AMP version BEFORE the FX Loop and Helix FULL amp. You then use a FS to TOGGLE between the physical pre-amp and the full Helix amp model to compare how each sounds with the modeled pre-amp, which is functioning as an AIAB pedal would ITRW. NOTE that it doesn't matter in this scenario whether the Helix FULL AMP is before or after the FX Loop Block, as they will never both be active at the same time. FWIW - I've tried this and didn't like it. The Helix pre-amps just don't do the AIAB thing well. IMO. But then, the couple of RW AIAB pedals I've tried sucked too. As always, YMMV. The sound that you're after only exists in one place, your head, so nobody can hear it but you!

I don't get this statement. If you can't remove your amp's preamp section from the signal chain, you're doing 4cm wrong. Describe your wiring and attach an example preset that demonstrates this "fact".

IDK about Logic, but in Reaper it opens to the last preset loaded, even if it's been modified but not saved, which I like.

W11 - WINDOWS !! AES/EBU - The digital interface between Helix and Powercab that allows (relatively vs MIDI) simple per preset configuration of the Powercab. That HW interface is not included on the Stadium. The D10 box replaces it so that the digital per preset configuration ability of Helix is restored. In the meantime, you can do the same thing with MIDI, but MIDI frightens people. Since Stadium also dropped the VARIAX connector, that is also restored by the D10.

My guess is a W11 problem. Are you connected via a USB HUB? Using a long cable? Maybe try a different cable? W11 is very picky about cables. Also, AES/EBU won't work with Stadium until the D10 box is released.

EOL is a two step process. First the mfr stops development, focusing their resources on new products. Then, when sales drop below where it's profitable to build it, they stop production. It may or may not be a Law of Nature, but it IS a Law of Business.

If I'm understanding you, you can't use Helix as an Audio Interface because the Helix ASIO driver is incompatible with your ARM based laptop? If that is the case, you have two options. Well, 3 if you want to try ASIO4ALL, but it sucks and you won't like the latency. assuming it works, not likely. 1 - Sell the ARM based laptop and get a proper x86 laptop. I know, money is tight and why would anybody want to buy it? IDK, I wouldn't, but you did.... 2 - Look for an Audio Interface with an ARM compatible ASIO Driver. According to the Focusrite website, the 4th Gen Scarlett interfaces are ARM64 compatible. Scarlett interfaces are excellent for home use and much more affordable than many "PRO" interfaces such as RME, and higher quality than cheaper options like Behringer. I've been using a 2nd Gen Scarlett 18i20 for ages. You can use Helix as a MIDI CONTROLLER with Native, but that won't help if you can't get audio into your laptop. You don't need MIDI DIN ports on the interface as Reaper can bring in MIDI over USB. I THINK the L6 MIDI driver should be compatible (it's "Class Compatible" and works fine with my iPad), but you might want to open a support ticket and ask.