rd2rk

https://line6.com/allure/ Don't worry if you're already signed up, just put in your email and it'll download.

Globals/Preferences/PresetModeSwitches=Stomp/Snap Use CommandCenter to assign MIDI to switches 2-5. You'll need to set commands in each preset in which you want this functionality.

It isn't going to sound good with chords because it's not polyphonic, it's monophonic - tracks one note at a time.

Check this article: http://www.harmonycentral.com/articles/keyboardaftertouch Cubase may have a similar aftertouch filter. It sounds like the problem is in how Cubase deals with the incoming messages. When you select a preset manually on Helix, by default Helix sends CC#61. I've asked in a couple of places about this (including support), but no one has yet been able explain it's purpose. It's possible that Cubase interprets it as aftertouch? In this list of midi commands: http://www.nortonmusic.com/midi_cc.html the author says: "46-63 may be in use as the LSB for controllers 14-31 in some devices, but I have not seen one yet"

If you're looking for a good metal tone from the factory presets, you may be disappointed. However, Helix contains pretty much all of the amps from which the metal genre was created. Load up any of the high gain models, throw a Scream 808 in front of it and there ya go. Add one of the EQs for fine tuning. Just like the real world. Metal heads argue endlessly over which real-world amp is best for djent or doom or Swedish black doom death metal or whatever. It's all very subjective. Don't believe what anybody says, try it yourself. If you feel that you absolutely need presets, there's Customtone for free. If you've still got a few bucks left, Fremen has great sounding (to me) heavy presets. Worst comes to worst, as surfsup said, you can always return it.

Put this on Ideascale, I'll vote for it!

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!