rd2rk

Considering that they acknowledged the problem 2 yrs ago, you're likely right about it being a hardware issue. One bad chip spoils the board! :rolleyes: What happens, though, if they admit it? Odds are it's not something that your local tech can just, you know, take out the bad chip and solder in a new one.

For the past 2 years......DOH! BAD ME! BE POSITIVE!

Opened a support ticket, with link and excerpts from this thread. Here's hoping......

I don't have an RC505, but MIDI is MIDI. I had a quick look at the manual, and it seems to have been written by someone who never actually USED MIDI. Not unusual. Here's how it MIGHT relate to how the Helix handles MIDI. Terminology: By "Channel" I assume you mean 'Track" By "Note" I assume you mean CC Value (vs CC#) By "Switch" you could mean either a switch that loads a preset, or a "Stomp" switch that sends a CC# and Value from within a preset When you load a preset, Helix will send CC messages assigned to Instant Commands (the lightning bolt), and any TOGGLING CCs assigned to Stomp switches. To send non-toggling CCs at preset load, assign them to Instant Commands. If you want to send non-toggling CCs from WITHIN a preset, assign them to stomps. The RC manual seems to indicate that the RC doesn't care about CC Values except when setting Levels. Which means that ANY value received on an assigned CC will reverse the state from it's previous state. But the author could be assuming that the Value will be either 000 or 127 without bothering to specify (author assumes that OF COURSE! Any fool knows that!). I've seen that before. Hope that helps. If not, tell me what SPECIFIC messages you used on the other devices and I'll try and see if I can figure it out.

The biggest problem with 4cm is lack of understanding of how and when to use it. If you like the sound of your tube amp and just want to use Helix effects with your current amp and 4cm, save yourself some bucks and get the new HX FX unit. If you want your current tube amp to sound like some other kind of amp, then see above for cruisinon2's comments (frfr is the way to go!).

Thanks Doug! I think this has been shuffled by L6 because so few people really use it. Maybe, if we keep up the pressure from all angles, they'll fix it. Think I'll head over to the Gear Page and post a link to this topic. I know that various L6 folks monitor the Helix thread there, maybe they'll have some info on the subject.

Yep, still happening in 2.50. This might be a good time for DI or one of the other L6 gurus to look into this for us.....

Google "MIDI Basics". Here's one result: http://tweakheadz.com/how-to-get-started-with-midi-and-the-difference-between-midi-and-audio-is-explained-along-with-many-other-core-concepts-for-building-a-home-recording-studio/ Could be TMI there. Here's the basic basics: Channels There are 16 MIDI channels. Channels allow you to send messages to specific devices in a MIDI setup. For instance, you could have your KPA "listening" on channel 1, a synth on channel 2 and another synth on channel 3. By using "Instant Commands" in the Helix Command Center, you could select a different preset (voice) on each by assigning different PC (Program Change) or CC (Continuous Controller) messages as needed. Channel 1=PC#032;Channel 2 = PC#079; Channel 3 = PC#002; etc. Program Change Used to select a specific preset or voice on the device listening on that channel. There are 128 PC#s available. Some devices respond to PC#s 001-128, some respond to PC#s 000-127. Helix/KPA uses 000-127. Continuous Controller Generally used to turn something on or off in a device preset, and/or to assign a value. CC#s and values range from 000-127. For instance, a specific CC# could turn a reverb on/off (usually, a CC VALUE of >064=ON and <64=OFF). A MIDI expression pedal might be assigned to a volume control with a certain CC#, and send values of minimum 000 to maximum 127. The KPA can use either PC#s OR CC#s to select presets, depending on whether you're in browse mode or performance mode. The Helix, by default, sends a PC# on the "Base" channel when you select a preset. 01A sends PC# 000; 02C sends PC#006. You can turn this behavior off in GLOBALS/MIDI, MIDI PC SEND, in which case only the PC/CC#s assigned to Instant Commands will be sent (and CC#61, don't ask why, nobody knows). Helix will also, when selecting a preset automatically send any toggling CC assigned to a button (not normal CC or NOTEs). At this time, there's no way to turn that behavior off, though that capability has been requested on Ideascale. There ya go, that's the basic basics as applies to the Helix/KPA. There's lots more, especially when you get into Synths (the TMI I spoke of), but this should get you started. HAVE FUN!

You've got one or more corrupted presets. Backup your setlists one at a time until you identify the setlist(s) that fail, then export 5 or 10 presets at a time until you narrow it down. When you find the culprit, delete it and you should be good to go! For me it was one of the Fremen presets. I re-imported it later and it was fine, so who knows what I did to mess it up.

Good Work. Thanks!

LMAO!!!

With Windows, you can use one or the other, but not both. I've heard you can use two on a MAC (composite?), but that doesn't help you. If you'd like a long-winded discussion of the pros/cons of using one or the other, try this: http://line6.com/support/topic/31613-record-dry-signal-and-wet-signal-at-same-time-with-separate-interface/ I don't use ProTools, but in Reaper and Sonar you can go into the Options or Preferences page and choose which driver to use, and HX Edit should continue to work regardless.

Sounds nice. Thanks!

Tried downloading it, twice. Just a blank preset. Am I missing something?

Depends what version he's got. The mkIII goes for $995. There's a point where average human ears can't tell the difference between the ultra high spec pre-amps and something that gets the job done. On that level, the Helix is NOT better than the $3000 UA, RME or Antelope. And if you're recording the Helix over S/PDIF, it's digital anyway, same as over USB, the pre-amps are irrelevant. If you need 8 inputs to record your band, and you're not rich, you get what you can afford that gets the job done. I'm quite happy with my $500 2nd Gen Focusrite 18i20, (and my Helix) thank you very much! Is this the point where everybody chimes in that my ears suck, and theirs are better? Please :rolleyes: ! Oh drat! There I go being aggressive again! I'm so bad!

Peace is good, and often screwed up by language issues - Tower of Babel and all that. I am, aggressively, trying to help solve the OP's problem. If you read my last post, I hope that it comes across as a sincere attempt to summarize what EVERYONE has said into a list of options. I'm all about options, and the only thing I've been adamant about is that while the Helix is a great device, it's not necessarily the solution to everyone's needs. It's been my unfortunate experience on this and other device specific forums, that any suggestion that the device in question is less than the Holy Grail tends to bring out the torches and pitchforks. But I am fearless in my pursuit of Truth, Justice and the Perfect Jelly Donut ;) !

So, trying to sum up OP's options: You have a MAC optimized Interface and a Windows computer. Option 1 - Sell the MOTU and get a Windows compatible interface. Use ABY or send block method with your new Helix Floor. Option 2 - Sell the Windows box and get a MAC. Use ABY or send block method with your new Helix Floor. Option 3 - Unless you have the sort of I/O needs I detailed previously (see options 1/2), sell the MOTU, use the Helix Floor as interface and the send block method to record your dry track. Option 4 - Unless you have the sort of I/O needs I detailed previously (see options 1/2), sell the MOTU, sell the fancy multi fx you currently have, return the Helix Floor in exchange for a Helix Rack, Controller and Mission SP1-L6H pedal. Might put money back in your pocket. Option 5 - If you DO have the sort of I/O needs I detailed previously, use option 4 and add a Windows compatible interface. Maximum flexibility, possible financial break-even. Bottom line - You've either got to sell the Motu or get a MAC. Option 4 will likely put money back in your pocket. Option 5 will solve ALL your problems. Additional considerations - You're still using Win7. If that's because your box is too old and under-powered to use Win10, then you're going to have to get a new computer sooner or later. Factor that cost into your plans. Of course, if the computer is not the problem, and you're running Win7 because of Win10 phobia, you need more help than we can provide.... :)!

I think spikey is right. I don't see how it could be done, but I learn something new every day....

I'm not interested, but I think somebody already submitted this on Ideascale. If you can't find it, Go for it!

Let me start by saying that, I like my Helix. Much better than the HD500X, which was a major improvement over the Behringer V-Guitar that I started with. For live performance, at it's price point it can't be beat! That said, for recording, there are MANY software amp sims that sound at least as good, some better (IMO). "With Helix you have no latency at all, while monitoring" While monitoring HELIX. If you use sw amp sims, that's where the latency thing comes into play. Helix was marketed as an 8in/8out mixer. It is, sort of. An 8x8 mixer should (IMO) allow any (analog) input to be used for mics (or line), not just 1 (with at least 1 instrument input, mine has 2) , and allow routing from a DAW DIRECTLY to ALL 8 outs, without having to configure each preset for each desired routing scheme. THAT'S the kind of capability that makes a mixer "the nerve center for your entire studio". "Break out the big box only when you have to record full band at once." If rewiring your studio for each different situation works for you, go for it! For me it's an unnecessary PITA. "I can't think of any reason having 109 dB of dynamic range on an 18i20 would be any better than the 123 dB you get on the Helix" If you think you need that 123db, you got it! I (so far) don't need it. Other considerations take precedence. This thread started because OP has a VERY nice interface that he wants to use because it suits HIS needs. I've used MOTU stuff. It's great HW, and works great with a MAC. But their PC drivers are crap, poorly supported afterthoughts to attract a market segment that they don't really care about. OP's need is to be able to use his MOTU interface with Helix to record a dry track AND a Helix processed track. This was possible with the HD500 using S/PDIF. Why did L6 drop that capability in Helix? To repeat, before y'all get out your torches and pitchforks - I LIKE MY HELIX! What I'm trying to say is that, for all it's wonderfulness, Helix is NOT the end-all be-all solution for everybody's needs.

"As soon as I arm a track it recorded the track with my guitar." When you stopped the recording you saved it (a dialog box opens automatically). Yes? Since it won't play back, I'm assuming that you know it recorded because you can see the recorded waveform. Yes? In that case, I would suspect that you may have bad sectors on the hard drive (the "media"). If the track is recording (you can see the recorded waveform), and you've checked the disk for bad sectors, try the Reaper forums. If this is a common problem then someone there will know about it. I recently started using Reaper after Gibson killed Sonar (screw Henry!), did the basic setup with all defaults except for the locations of recordings (set to a different drive), and have had no problems using Helix (or Native).

The hangup is simple. WE DON'T WANT TO USE THE HELIX AS THE INTERFACE! We're not insane. We'd just rather use the BETTER INTERFACE THAT WE HAVE. This used to be possible with the HD500, by configuring S/PDIF to send the CLEAN signal. That option is no longer available. Is there another way, without configuring every preset separately for that purpose (GLOBALLY)?

I think OP is looking for the easiest way to do this. The only way I know of (as I posted above) requires each and every preset to be specially configured for that purpose. Suppose he just wants to use ready-made presets. There's a lot of them, and that method would be annoying at best. Is there a way to configure the Helix Globally to do this? Seems to me that the HD500 allowed the S/PDIF ports to be set up like this, but the Helix did away with that capability. If there's a similar GLOBAL way to do this in Helix, I would also like to know how.

When you select a preset on the Helix, it sends the corresponding midi Program Change# - 01A sends 000, 01B sends 001, etc. You probably don't want Mainstage to load that particular preset. To prevent this default behavior, in GLOBAL-MIDI/TEMPO, on Page 2, set MIDI PC SEND to OFF. Then, to make Helix send the PC# of your choice, press the preset button you want to program and, in Command Center, select the first Instant Command (the lightning bolts). Turn the knob until you see COMMAND. Set it to Bank/Prog. Make sure the Midi Channel matches the channel that Mainstage receives on. Set PROGRAM to the PC# you need. Don't sweat the other stuff unless whatever you're trying to control in Mainstage also requires a Bank Change to get you where you want to go. DON'T FORGET TO SAVE THE PRESET! Now, when you select a Helix preset, the PC# you set will instantly be sent to Mainstage, selecting the song of your choice!

We need a separate section for Helix FX!