Avoid certain cc's when assigning pads for Remote or Devices

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
regretfullySaid
Posts: 8913
Joined: Thu Apr 22, 2010 5:50 pm

Avoid certain cc's when assigning pads for Remote or Devices

Post by regretfullySaid » Sat May 28, 2011 12:35 am

Hi!

I want to assign cc's to PadKontrol scenes 9-16 for either Remote controls (not global) or Device controls.
Are there some cc's that I must avoid (like ones with MSB)? I was hoping I could keep it simple and have it go through 0-127 and keep them all on one channel but I don't think that's a possibility. It's a pain in the ass to refer to the standard midi cc chart to find out which ones I should questionably avoid. Follow?
ImageImage

yur2die4
Posts: 7333
Joined: Sat Oct 03, 2009 3:02 am
Location: Menasha, Wisconsin
Contact:

Re: Avoid certain cc's when assigning pads for Remote or Devices

Post by yur2die4 » Sat May 28, 2011 1:21 am

Do you use vst's?

Ableton Live itself won't act out whenever you use a common CC#.

vst's are usually programmed with those CC#'s in mind so that people's layouts on their keyboards can be predictable. This is also true with hardware synths.

If you assign something from your padKontrol in Ableton Live, then Ableton Live will basically just override any sending of that CC#, and you won't have to worry about it conflicting with anything else.

If you do use another device which uses common CC#'s and expect to use it to interact with external gear or a vst, just make sure it is a channel different from that which you set the padKontrol to :)

regretfullySaid
Posts: 8913
Joined: Thu Apr 22, 2010 5:50 pm

Re: Avoid certain cc's when assigning pads for Remote or Devices

Post by regretfullySaid » Sat May 28, 2011 1:59 am

Ableton Live itself won't act out whenever you use a common CC#.
That's the answer I was hoping for. I figured that was the case, but wanted to make sure. I want to make sure messages don't conflict if Live had native settings attached to transport or global controls.

Other than that, the rest is preaching to the choir:) It's kind of funny you answered because a lot of times when someone else is asking a question and I'm about to answer I find that you answered first with the same answer (regarding techniques, not solid rtfm stuff):p

I'm keeping my vsts on lower midi channels and cc controls on higher midi channels so nothing clashes.
Specifically, I have pK Scenes 1-8 as midi notes for all of the notes in the drum rack (exactly 128 notes:))
Then, I think I'm going to split Scenes 9-16 in half; 4 scenes will be for NativeKontrol X-Controls (Clyphx) and the other 4 scenes will be general purpose ccs for Device Racks.

So, I was hoping I could make it easier to go through the 8 scenes and just assign cc's 0-127 sequentially (btw it's faster to make settings from the pK itself than using the editor) and have them on the same channel for the sake of organization. I just wanted to make sure none of this will affect any native Live settings. Thanks:)

Cool. So yeah; I have Scenes 1-8 on CH.10 for Drum Rack and Scenes 9-16 CC.0-127 on CH.15. No problems.

If anyone wants the scene set for their pK you can download it here:)
Last edited by regretfullySaid on Sat May 28, 2011 10:20 pm, edited 2 times in total.
ImageImage

yur2die4
Posts: 7333
Joined: Sat Oct 03, 2009 3:02 am
Location: Menasha, Wisconsin
Contact:

Re: Avoid certain cc's when assigning pads for Remote or Devices

Post by yur2die4 » Sat May 28, 2011 5:55 am

The only basic CC I've not been able to map on Live is the Program Change. agh.

Locked