rd2rk

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!

Sorry 'bout that! The question really does get asked so many times, usually wrapped in negativity, that I get a bit tired of typing the same thing over and over.

For the 327,743rd time here and on every other Helix forum, NO! There WILL be updates! Go to the Gear Page>Digital and Modeling Form and search for posts by @DigitalIgloo, (Eric Klein - Line 6 Chief Product Design Architect). He also posts in most every other Line 6 product related forum - Facebook etc. Will there be MAJOR improvements/additions? Probably not. But unless he's lying, there WILL be updates.

Try it both ways and use the solution that sounds best. If the preamp with Channel Volume maxxed is too quiet, follow it with a GAIN Block. You can then use Snapshots to control the amount of gain sent to the Amp1. Once you've got 4cm set up, you can toggle the HX preamp and Amp1 preamp for comparison by saving the Preamp/Amp/Gain Block bypass ON and the FX Loop Bypass OFF. If you assign them all to the same FS, each time you hit the assigned FS they'll toggle - HX Pre/Amp/Gain ON with FX Loop OFF bypasses the Amp1 "Voice" and vice versa.

Computers. Can't live with them, hitting them with a stick is satisfying but expensive.

I have Reaper and Helix installed on two different W11 machines, one upgraded from W10, no problems. What processor is in your computer? Mine are both i7, different gens (7 & 11). I've read of people with other processors having problems. Assuming you've got an Intel processor, try installing one of the other FREE DAWs such as LIVE Intro, see if you still have problems. Maybe Reaper somehow got corrupted?

IDK how you reinstalled the drivers, but if you re-install the latest version of HX Edit (download it - v3.82), that is the correct way. You MAY have to uninstall all L6 drivers, reboot and try again if re-installing HX Edit alone fails to solve the problem. Sometimes having multiple old versions installed can cause issues.

It doesn't matter what you think you see in the preset. The only thing that matters is what is actually being sent. Here's a simple FREE monitor: MIDIView - Free MIDI Monitor tool for Win & Mac Here's an online monitor: Disaster Area Designs MIDI Monitor

Load a MIDI Monitor program so that you can see what EXACTLY is being sent. Using the preset that works, note (on paper) the messages being sent by each Snapshot. Do the same with the preset that doesn't work. This procedure will show you where the problem lies.

Sometimes a preset can become "corrupt". No cure but to overwrite it and start over.

1 - Reboot 2 - Factory reset 3 - Open a support ticket

Gain pedals are inherently noisy. The HX FX Loop adds a small amount of noise. The inherently noisy gain pedal amplifies that noise. Put gain pedals between the guitar and Helix. If you MUST put a gain pedal in an FX Loop, use a Helix FS or Snapshot to bypass the FX Loop, rather than the pedal FS.