rd2rk

Not going to happen. Helix is nearing EOL and any future updates will be minor. You can run NAM on iOS or Android and use Helix for pre/post FX, so why should L6 waste resources porting NAM to Helix? Stadium is the future for L6, and Proxy is the L6 answer to ToneX/KPA/NAM/QC, XYZBTGPP-- etc. Staying AHEAD of their competitors.

WARNING! ZOMBIE THREAD! BUT...FWIW - That only affects the blinking of the LED. Tapping to set the actual tempo is still active. Always. Having your Helix for 3 hours is relevant, how?

Are all of your computers Windows 11? A recent update (maybe several) caused the problem. On one of my W11 boxes the problem was caused by a ".net Framework" update (KB5092427). Rolling back to a restore point previous to that update and preventing Windows Update from reinstalling it fixed the problem. On another W11 box I didn't have a similar restore point and simply uninstalling (KB5092427) didn't fix it. On my last remaining W10 box it's not an issue, USB MIDI works fine.

Page 44 of the user manual. It's really that simple. It's a very basic looper, not really intended for performance, more like a scratch pad for ideas or jamming with yourself. One track + overdubs. You can't save a loop. When you leave the preset or shut down the unit, that's it, it's gone!

The post you're replying to is 5yrs old, so that person might not still be around. If you're using a Helix AMP in your signal chain, then you can simply go direct to the physical amp's RETURN, running your rig the same way you'd use a traditional rig. However, this bypasses the physical amp's preamp section. Without some kind of an amp in the Helix signal chain, it probably won't sound all that great. So, if your goal is to simplify your setup, you can use Helix as either a traditional pedalboard with all effects into the physical amp's INPUT or as a traditional pedalboard with AIAB into the physical amp's RETURN. If you run 4cm you can choose, on the fly, to use either the physical amp's preamp or a Helix amp simply by assigning both the Helix amp and the FX S/R Block to the same FS. If you SAVE the preset with one ON and the other BYPASSED then each time you hit the FS you'll TOGGLE between the physical amp and the Helix amp. You can also use SNAPSHOTS for this, allowing you to change other parameters/devices at the same time from a single FS. You can even, DSP allowing, use multiple Helix amps for even more virtual "amp channels". You can place some FX (like OD, DIST, MODS) BEFORE the amps and some (like time based FX) AFTER the amps and the whole shebang will output through the physical amp's power amp and speaker. This is also convenient if you want to route the signal to FOH using an IR. One of the advantages of Helix is millions of options, but if you want SIMPLE you can do that, too.

FTFY. You heard wrong.

I compared a couple of the other OD's including the MOD version and I see what you mean. I've never used a DS1 IRL, so I don't know if this is normal. The only way I see to know is to get a DS1 and test it ITRW. If you have GC near you it will likely have a BOSS demo station - most of them do - and you could use that to test one out. If you're in the US you could also call support and ask them about it. Good Luck!

The art of "Gain Staging". Generally speaking, when you add gain (level) sufficient to push an amp or effect circuit past it's "clean headroom" level, the circuit "compresses" - the output volume lowers. Different overdrive/distortion circuits work differently with different amps/effects depending upon the amp/effect circuit's available "clean headroom" in relation to the pedal's output. If you like the sound of a certain overdrive into a certain amp but want a volume boost when you kick in the overdrive, place a GAIN block AFTER the amp and tie the pedal and GAIN block to a single FS. You can also use the amp's CHANNEL VOLUME the same way. Be aware that the added volume boost after the amp will affect every effect downstream of the boost. You may need to place the boost farther down the signal chain to avoid that. The art of "Gain Staging". IOW - it's not a bug, it's just the way things work. Not every pedal sounds good with every amp.

Instrument.

Ah! Didn't see that the "PEDAL" jack doubles as TRS MIDI. Once upon a time there were brick'n'mortar stores with knowledgeable staff where you could try this stuff out before buying.

If MIDI over USB works from your computer, then it's not the HXS. If you can return the C+, do it and get an Ampero Control. It's virtually the same device but with standard DIN plugs, Work first time/every time. Also has USB (no HOST mode) and BT if you must. I don't BT, but use USB when controlling plugins.

I've had a quick look at the Broken Arrow and the Unity6 product pages. It looks like you need one of these: Amazon.com: Cable Matters 5-PIN DIN MIDI Splitter Cable (Dual MIDI Cable) - 0.5 Meters / 1.6 Feet : Musical Instruments Connect the single DIN to the UNITY6 MIDI OUT and connect one of the Splits to the TRS adapter cable going to the Broken Arrow and the other to the HX ONE. If the UNITY6 is sending HX ONE commands on Channel 4 and the HX ONE is configured to listen on Channel 4, then it should work. Likewise for the Broken Arrow on Channel 1.

I'd like to help you, but I can't help if you ignore my questions. Have you used a MIDI Monitor to verify that your MIDI Controller (Unity6) it is actually sending what you think it is sending?

What MIDI Controller are you using? Have you used a MIDI Monitor to verify that it is actually sending what you think it is sending?

No.

Back up all of your presets. Perform a complete Factory Reset. Restore your presets. If that doesn't fix it, reinstall the Firmware. Restore your presets. If that doesn't fix it, contact support.

Yes, that's the way it works, regardless of method or buffer settings, both in NATIVE and on the actual hardware. It's the amount of time it takes to UNLOAD one preset from memory and then LOAD the new one. Snapshots are virtually instantaneous because there's no UNLOAD/LOAD process, just parameter changes within the preset.

Your RETURN and AUX paths are both routed to Path 2A - those Output Blocks are what I refer to as the "middle". That's where they mix, and the MIC path enters 2A at the end just before the final output block (MULTI), bypassing the FX that the RETURN and AUX paths share.

Just re-assign the level of that output to FS9 with the opposite MIN/MAX settings - it'll look just like the original preset's settings for FS9. The MIC Path will continue to work because you're cutting the AUX signal in the middle, not at the final output. I've attached a modded version. Unless I've missed something, that should work. MartinJ28 2o Vx2.hlx

Thanks for the link @russ5254. I was hoping that you'd found some magical way to just "make it work" like every VST2 plugin. I don't use plugins live - too many potential problems with computers - but computers and plugins are how I got into amp sims in the first place (back in the stone age) and I still use them for variety and fun at home. Running Helix amps through THU Supercabs and Breverbs gets some great sounds! Live I prefer dedicated HW - Helix Floor with HX Stomp as backup.

The problem you've described is not a real thing - I've had my Catalyst since first release. No problem with sustain at all. It's true that analog gain pedals sometimes don't play well with solid state amps, but I highly doubt that this is the problem. Contact support, maybe it's defective.

I can't find that here or in Helix Native. A link would be helpful...

I wasn't clear from your signal flow description what was going on, but if you cleared up the clipping and it's all working, RESPECT!

I had a look at the SYN2/M50 Manuals. If I understand what I'm seeing, the M50 has two channels and you're using the Syn2 to add channels? Or are you using the SYN2 to BYPASS the M50 channels, using the M50 purely as a power amp/speaker? Using the M50 as power amp/speaker the routing should be: Guitar>HX INPUT>HX FX Loop SEND 1 (INSTRUMENT LEVEL)>SYN2 INPUT> Syn2 FX Loop SEND (PEDAL LEVEL)>HX FX Loop RETURN 1 (INSTRUMENT LEVEL) HX Main Output (INSTRUMENT LEVEL)>SYN2 FX Loop RETURN (PEDAL LEVEL) SYN2 MAIN Output (LINE LEVEL?>M50 RETURN (LINE LEVEL) This is simplest 4cm. If you're using the SYN2 to ADD channels to the M50, then it could be much more complicated depending upon whether or not the SYN2 FX Loop is BYPASSED when the preamps are BYPASSED.

In the beginning is the INPUT. At the end is the MAIN OUTPUT. In between is the FX LOOP BLOCK - SEND routes (SENDS) the signal from the FX which are placed BEFORE to the amp's INPUT (usually GAIN and MOD FX) - just like on a physical pedal board ITRW. The amp's effected PREAMP signal then passes back (RETURNS) to the HXFX RETURN to be processed by the FX placed in the AMP's FX Loop (usually MOD and time-based FX such as REVERB/DELAY) - just like ITRW. The MAIN OUTPUT then routes the further effected signal to the amp's POWER AMP and SPEAKER via the AMP's RETURN - just like ITRW. Without the FX Loop Block the signal passes from the BEGINNING to the END - INPUT to MAIN OUTPUT. That's 4cm - Four Cable Method. Both the SEND and the MAIN OUTPUT are OUTPUTS - the terms SEND and MAIN are intended to differentiate the actual intended design functions. If you want the HXFX IN the AMP's FX Loop, then you plug your guitar into the AMP's Input and route the AMP's SEND to the HXFX INPUT and the HXFX MAIN OUTPUT to the AMP's RETURN. Just like using traditional serial FX in an AMP's FX Loop ITRW. Using names that reflect the intended functions must have somehow seemed logical to somebody. Makes sense to me!