rd2rk

Worst user manual ever. Although the footswitch jack LOOKS like 5 pin MIDI, I wouldn't count on it. As far as I can tell, PRS considers this "Need to know" info and, as the purchaser of their product YOU DON'T NEED TO KNOW! You should call them, they're much nicer on the phone (I have 2 PRS guitars). Otherwise, unless someone else here knows from experience, I would heed this warning from the manual: Footswitch Jack: Connect the included footswitch to control channel switching and the eff ects loop bypass function. When using the footswitch, select the clean channel on the amplifier front panel for proper function. Only use the included footswitch. Connection of an improper footswitch may result in damage to the amplifier.

When I got my Helix, I was looking through the Templates and found the DAW REMOTE (MMC). This is what the "START" message looks like in MIDIOX - SYSX: 240 127 127 6 2 247 When it did nothing in SONAR, I went looking around for info on how MMC works. I found this: "Sysex messages do not support MIDI channel numbers, so the model and unit number are necessary in order to target a specific synth in a MIDI chain that contains multiple synths from the same manufacturer." And this: "MMC Message Format[edit] An MMC message is either an MMC command (Sub-ID#1=06) or an MMC response (Sub-ID#1=07). As a SysEx message it is formatted (all numbers hexadecimal): F0 7F <Device-ID> <06|07> [<Sub-ID#2> [<parameters>]] F7 Device-ID: MMC device's ID#; value 00-7F (7F = all devices); AKA "channel number" Sub-ID#1: 06 = command Sub-ID#2: 01 Stop 02 Play 03 Deferred Play (play after no longer busy) 04 Fast Forward 05 Rewind 06 Record Strobe (AKA [[Punch in/out|Punch In]]) 07 Record Exit (AKA [[Punch out (music)|Punch out]]) 08 Record Pause 09 Pause (pause playback) 0A Eject (disengage media container from MMC device) 0B Chase 0D MMC Reset (to default/startup state) 40 Write (AKA Record Ready, AKA Arm Tracks) parameters: <length1> 4F <length2> <track-bitmap-bytes> 44 Goto (AKA Locate) parameters: <length>=06 01 <hours> <minutes> <seconds> <frames> <subframes> 47 Shuttle parameters: <length>=03 <sh> <sm> <sl> (MIDI Standard Speed codes) Sub-ID#1: 07 = response Sub-ID#2: response state parameters: values detailing response state" ----------------------------------------------Looks like Greek to me! I tried contacting L6 support about using this template, but I got the impression that they didn't want to get into it. I wound up using CC#s to control the transport in Ableton and the built-in ACT controller functions (which use CC#s) in SONAR. I suggest you look for similar functions in DP9. If someone from L6 knows how to use the DAW REMOTE (MMC) template, I hope they'll chime in here.......

And YES, MMC is sent from the Helix over USB.

Do you have a MIDI monitor? If you're on a PC, get MIDIOX (it's free). There's something for MAC, but I don't know what it's called. There's also a VST MIDI Monitor. Once you have a monitor, see EXACTLY what the Helix is sending, that way you can tell the MOTU guys YES it's sending and exactly WHAT it's sending.

The FX LOOP Block is in the SEND/RETURN Category. Be sure to choose the one for the ins/outs you're using.

You need to add an FX LOOP Block between the FX that you want BEFORE the Mesa Preamp, and the FX you want AFTER the Preamp but BEFORE the Poweramp.

Assuming that you have already configured dp9 to recognize the helix as both audio and midi device, look in dp9's configuration pages for a way to enable mmc. If you can't find it, try their support/FAQs/forum.

Might be helpful to name your DAW. Mine, Sonar Platinum, is not compatible with mmc, although older versions were.

Like I said above: "All the opinions you get on all the forums you ask on will just serve to confuse the issue. Let your own ears make the choice by REAL WORLD COMPARISON!" My quality is your trash. It's entirely subjective.

DON'T SELL YOUR PEDAL BOARD! Is this better than that? Ask anywhere, you'll get 1,000 different answers. BUY A HELIX! Buy it from Sweetwater or GC or anywhere that gives you 30 to 45 days to check it out. COMPARE IT to your pedal board. Which one (or parts of each) sounds better to YOUR EARS? You might end up selling the pedal board. You might return the Helix. You might keep bits from your pedal board to use WITH the Helix and sell the rest. All the opinions you get on all the forums you ask on will just serve to confuse the issue. Let your own ears make the choice by REAL WORLD COMPARISON!

To use it in an FX Loop you'd need to add a loop block to every preset. Why not use it like you always have? Guitar->Wah->Helix That's how I use my 535Q, and it sounds great! Only time you need a loop is if you want your CAE after other, Helix FX, or combined with other external FX in a one-button-to-activate the chain type configuration.

IF you have the UNO chip THEN the following SHOULD work: FCB configured to show PC#s starting at 001 NO PC REPEATS OFF On the pedal you want to use: PC1 BLANK PC5 023 Preset CC1 CC#032 VALUE 001 STOMP1 CC1 CC#069 VALUES (both) 000 In the STOMPS column of the preset, set STOMP 1 to ON This should send CC#32 (BANK CHANGE) with a value of 001 to select setlist 2 PC#023 to select preset 23 CC#069 value 000 to select snapshot 1 According to the manual, that should work. It doesn't. I suspect that it's because of the timing of the messages, the Helix probably needs a pause between messages. You can't do that with the FCB, even with UNO. You can't do any of that with the stock FCB chip. You MIGHT be able to get this to work by routing the MIDI thru a PC running BOME MIDI Translator or some such.

Is there a send/return/loop block in the preset?

Yes. Assign a CC# & value (BIAS doesn't care what CC# or value, and it doesn't need to be a toggling value) to the toe switch, and another to the pedal (min 0 max 127). Make sure that the POD is selected as a midi device in BIAS, and that they're communicating on the same channel. Use midi learn to set up the pedal and switch, you should be good to go!

That's Redwirez. They're the ones most people say "too many choices. Apparently, not many folks read their article "Dialing in your tone with Redwirez IRs". http://www.redwirez.com/ir/DialingInYourTone.pdf

Reamping is USB. From the manual: 32. USB Helix also functions as a high quality, multi-in/out, 24-bit/96kHz audio interface for Mac® and Windows® computers, with DI, Re-amping and MIDI functionality built right in. Helix can also record to an Apple iPad (with optional Apple Camera Connection Kit). Use of a USB 2.0 or 3.0 port is required - Do not use an external USB hub. See "USB Audio" USB 1/2, USB 3/4, USB 5/6 USB 1/2, 3/4, and 5/6 can act as additional output blocks for routing paths to your computer, iPad, or iPhone (with optional Apple Camera Connection Kit). USB 7 and 8 are dedicated for re-amping, and are not available as output block destinations. See "USB Audio" for details.

Make sure the sample rate matches. The Helix defaults to 48, focusrite to 44.1. I have the 18i20, couldn't use SPDIF at either rate without noise. Went back to analog, can't tell the difference except no noise.

Nice!

Maybe I'm misunderstanding "looper mode". From the manual: "Looper Footswitch Mode Looper mode is only available if a Looper block has been assigned to a footswitch in Stomp mode. Nearly all factory presets in Helix have a Looper block assigned to a footswitch, but your custom presets may not." When selecting any preset, including new (blank) presets, Helix sends CC#61 (I verified this using MIDIOX). Since there's no Looper block in a new preset, no CC should be sent, and yet, it is! Am I missing something?

OP was asking about SPDIF. Different animal.

Agree, no audible difference, except that SPDIF added dropouts AND extraneous noise, even on a decent interface (Scarlett 18i20) and even at 44.1. I thought that there might be a latency improvement (conversions take time), but not that I could tell. Go analog!

Most ABY boxes go both ways: https://smile.amazon.com/s/ref=nb_sb_ss_i_3_3?url=search-alias%3Dmi&field-keywords=aby+box&sprefix=aby%2Caps%2C362&crid=1HFB1RG4AHS7K I have 2 of the Live wire units (<$50), passive unless you want indicator lights, then either 9v battery or adaptor. If you look down that page you'll see that there are several that look identical but for the brand names. Probably all made in the same Chinese factory. I've heard it said that they are noisy. That's nonsense. I've been using them for years, no noise. There's a higher priced Morley that is 2 into 2 and has preamps . I thought it would be useful for input balancing Strat/LP/Acoustic. THAT unit is noisy!

In Global Settings - MIDI/Tempo, set MIDI over USB to ON. You didn't mention what app you're using, but I do this in Ableton to jam along to Mp3 tracks. You just need to configure the Helix as a MIDI device and know what MIDI commands the app needs for Start/Stop.

I called up a New Preset, ran XLR Left/Mono to one input, and 1/4" Left/Mono to the other. Dead quiet unless I turned up the Alto input past halfway, then it started to get noisy. That's normal, as the Alto TS210's input rotary is actually like the Line/Mic control on a mixer as opposed to a Volume. Could be the way your interface handles the different connections?

Nobody can tell you what the levels "SHOULD" be. You'll have to experiment, as every FX addition/subtraction from the signal chain will affect the gain staging downstream. The routing I presented will allow you to duplicate the setups as close as possible, and compare them in real time. HOWEVER..... "The idea is that I can test the tones at home with headphones and hear it with the cab sim, but in a live setting, I can just take a cable from Send 1 to the Return of my amp, and hopefully the resulting sound will be much the same (slight cab differences aside)." Gain staging and final sound/tone are separate issues. Your headphone signal with cab sim will ALWAYS sound SIGNIFICANTLY different from helix preamp(or full amp)->Bugera power amp->REAL cab. Just the nature of the beast. The routing I suggested will help with GAIN STAGING issues UP TO the output to the Bugera. That final level needs to be set with the BIG KNOB if you're using the 1/4" out, or the Send Level if you're using a SEND. There's been much discussion about the lack of level indicators in the Helix, and there are a number of entries in Ideascale if you'd like to add your vote on the subject. Best workaround is to send your signal to a DAW and use the level indicators, spectrum analyzers, etc that are available in that realm. Here's a couple of links that you might find helpful: https://www.sweetwater.com/sweetcare/articles/whats-the-difference-between-mic-instrument-line-and-speaker-level-signals/ and a Google search on Gain Staging: https://www.google.com/search?q=gain+staging+effects&rlz=1C1CHFX_enUS655US656&oq=effects+gain+staging&aqs=chrome.1.69i57j0.9471j0j7&sourceid=chrome&ie=UTF-8 Maybe someone else would like to chime in on tips specific to Helix?