rd2rk

Sunnyhaair - never mind, VST2 works fine in Live 9 ajaseniero - are you using the latest version of Live 9 (9.7.3)? bobruz - it's working in Sonar Platinum

Sunnyhaair - where in Preferences did you find the AU box?

We're good. Actually, I agree with you that it's much to-do about nothing. I sure can't tell the difference between loading an ir at 48/16 and loading the same ir at 96/24 and letting Helix convert . Considering what I've read and other contributions made to this discussion since it started, I believe that I can now say with absolute certainty that it is definitely better to know than not to know, even if what I now think I know is that no one REALLY knows!

Will, I've posted enough on this forum that you know I'm not a troll. As well I know that you're not one. I'm sorry if I sounded grumpy (would a smiley have made it better? :)), and I acknowledged your good intentions. So why are you attacking me? I get that you're not interested in the answer to the question, but I am, as is (I assume) the OP. Why not just step out and let someone who knows answer the question?

Thanks for telling us how to think, but we already know that you don't know. How would you know that there's something to know that isn't worth knowing?

aleclee - just re-read your reply - sounds pretty close to definitive. Can anybody confirm?

The question may be academic, but that doesn't mean it's irrelevant. OP asked for an "insider" - I read "definitive" - answer. Three people responded "I don't know, but here's my opinion". I know you mean well, but some people just want to KNOW! Does anybody KNOW?

I realize that this thread is a bit old, but I'm felling a bit dense on this subject, and need the simple definitive answer. I'm using a G10 wireless exclusively these days. My understanding is that the G10 loads the pickups at 1M, therefore it's OK to leave the default Helix setting at AUTO, as nothing else matters beyond that first device (the G10). Yes or no?

I think you're misunderstanding the difference between PC, CC and CHANNEL. You set Ableton to SEND a PC# over the MIDI CHANNEL that the Helix is set to RECEIVE on (MIDI BASE CHANNEL). You send the PC# from Ableton that corresponds to the Helix Preset that you want to load. CC# 32 is used to select the SETLIST that contains your desired Preset. The directions in the manual are a bit confusing on this issue (page 57). In the example, you send CC#32 with a VALUE of 007. Ableton would need to send: CC#32 value 007 loads setlist PC#005 loads preset CC#69 value 000 loads snapshot I haven't done this from a DAW, but when I tried it from my FCB1010 it didn't work, probably because the Helix required a pause between messages that the FCB couldn't be configured for. Ableton may allow for that, or the default time between messages might be sufficient. That is the extent of my knowledge on the subject. If someone knows more, I'd be pleased to know!

bobruz - NICE FIND! Lots of good stuff there!

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