dumb question re: recording control surface automation

Strauzzie · Post by **Strauzzie** » Mon Jan 21, 2008 1:32 am

So.. I must be really dense today but I just noticed something strange..

I have a Trigger Finger setup as a Control Surface in live. The problem is, whenever I am controlling a rack with the TF (signified by the ol' blue hand), it disables the ability to record the TF knob CC's into a clip in session view. What's up with that?

Has anyone else seen this?

Strauzzie · Post by **Strauzzie** » Mon Jan 21, 2008 1:45 am

welp, i think the manual answered my question for me:

"Before we explain how remote control assignments are made and implemented, let’s rst
make the distinction between MIDI remote control and a separate use of MIDI in Live: as
the input for our MIDI tracks. Let’s suppose that you are using a MIDI keyboard to play an
instrument in one of Live’s MIDI tracks. If you assign C-1 on your MIDI keyboard to a Session
View Clip Launch button, that key will cease play C-1 of your MIDI track’s instrument, as it
now belongs solely to the Clip Launch button.

MIDI keys that become part of remote control assignments can no longer be used as input
for MIDI tracks. This is a common cause of confusion that can be easily resolved by observing
the Control Bar’s MIDI indicators."

SystemCell · Post by **SystemCell** » Tue Jan 22, 2008 8:54 am

There is a workaround for this however. If you have a controller that can have multiple zones assigned to a single controller, just have the control send different midi cc's depending on what zone you have selected. Essentially with the touch of a button you can choose to have pad 1 send cc 27 or cc 34, or both. You can also correct this by changing what channel the pad is sending the midi signal on and send the same midi cc just on different channels.

craw · Post by **craw** » Tue Jan 22, 2008 9:38 am

you can't record automation directly into session clips ... it can only be recorded into the arrangement