|
Using MIDI CCs in Pro Tools: Part 2
This week we continue our discussion of MIDI CC data inside Pro Tools, taking a look at a more advanced example of manual CC mapping with Xpand and graphical editing of CC data using the edit window. If you missed last weeks article on MIDI CC basics in Pro Tools be sure to check it out before you proceed.
Manual CC Assignment
Last week I showed you how to easily map controls on your MIDI controller to nearly any parameter using the CC “learn” function in Xpand and other virtual instruments. This method is fine for most workflows that require minimal CC manipulation, but sometimes we want a bit more control over which CCs correspond to a specific set of parameters.
Just like last week’s example, I have created a new stereo instrument track and inserted the Xpand plug-in. This time I have loaded up an electric piano patch and added a lo-fi delay using Xpand’s built in effects. My goal is to assign MIDI CC50 to the FX2 parameter (the delay FX send) in Xpand so I am able to tweak the amount of delay from my MIDI controller.
First things first, I need to know that one of the knobs on my MIDI controller is assigned to MIDI CC50. To do this I have two options: I can either assign the knob of my choice using my controllers on board controls or use a software editor designed specifically for my MIDI controller. On board assignment is the most convenient but can often involve a tricky combination of buttons that is not always obvious without the manual in front of you. Refer to you keyboard or MIDI controller’s user’s guide for instructions on assigning specific CC values to knobs or faders on your controller. Again for most people, using the CC “learn” function (if available) is often the most efficient way to map controls.
Tip: Many MIDI controllers ship with editing software (like M-Audio’s Enigma editor) that allows users to easily map their keyboard’s knobs and faders and save complex set-ups into user “scenes.” These scenes can be pre-setup to control specific virtual instruments or software and recalled with the press of a button, saving you the trouble of remapping frequently used set-ups. It is quite common for manufactures to ship pre-programmed scenes ready to use with popular software packages like Abelton Live and Propellerhead’s Reason. Check out your specific MIDI controller’s users manual to learn about these features.
Now that I have configured my MIDI Controller and I know that I have data coming in on CC50, I can now tell Xpand to route that data to the delay send parameter. Right clicking on the FX2 parameter, I choose Assign > CC50. Once the parameter has been assigned, Xpand will show the parameter’s name next to its CC number. In this case I have assigned Part A FX 2 Send to CC50.
Making sure that the instrument track is record enabled, I can now control and automate the delay send parameter using CC50 messages from my MIDI keyboard.
Note: Some older virtual instruments and hardware gear only support fixed CC mappings. For example MIDI CC #42 may always correspond to filter resonance. In this situation we are forced to integrate CC control on the MIDI controller’s end, assigning a specific continuous controller number to a knob or fader via the MIDI controllers onboard controllers or through special editing software.
Editing CC Data
Once you have gone through an initial pass of controller automation sometimes it is nice to clean it up graphically via the edit window. You can also use this method from the start to “draw” in complex controller data, without the use of a keyboard controller.
To view a graph of CC50, click on the Xpand track’s view selector and choose Controllers > Add / Remove Controllers.
After adding CC50 I can now view its graph in the edit window. Note: Controllers that have CC data written into the region will automatically be added to the list of available controllers in the track view selector and do not need to be added manually.
You can edit the graph’s break points using the pencil and grabber tools to draw in and manipulate controller data. CC data can also be copied, pasted, and duplicated much like audio, allowing you to take a very complex idea and repeat it over and over again. Since the MIDI protocol is 8-bit, when zoomed in controller graphs appear “stepped” allowing only 127 discrete values.
MIDI CC vs Pro Tools automation
Continuous Controller data differs from Pro Tools automation data in that it is stored within the MIDI region itself, as opposed to the track. This means that the CC data will travel along with the note data in a standard MIDI file, making it very portable. Continuous Controllers are recorded simultaneously along with other incoming MIDI events in the Pro Tools sequencer.
In our Xpand example, the MIDI CC messages that were mapped to the parameter FX2 (a delay send) would be recorded along with any other incoming MIDI data and stored within a MIDI region. Because the CC messages were mapped inside a specific instrument plug-in, the data within that midi region will only have context when played back with the exact same Xpand instrument unless the same CC values are mapped to a similar parameter in another instrument.
Because the controller data is tied to the MIDI region, Virtual instruments are the only types of plug-ins that support MIDI controller mapping in Pro Tools. Unfortunately unlike some of the other DAWs on the market, MIDI CCs wont work with your favorite EQ or Delay plug-in and you can’t use MIDI CCs to control Pro Tools mixer elements like volume, pan, and sends. If you want to tweak your plug-ins or the mixer with tactile control you will need to use a Pro Tools compatible control surface, see my article on control surfaces for more info.
Since MIDI is an 8-bit protocol, CC data is not ideal for controlling or automating very fine parameter changes. Pro Tools automation offers much higher resolution then MIDI CC and is ideal for parameters that need extra detail.
Pro Tools tidbits:
• Digidesign announced the new 003 and 003-rack hardware line along with new Ignition Pack 2 and Ignition Pack 2 Pro bundles.
If you have a Pro Tools related question that you would like me to take a shot at answering or have any feedback, please send it to brian@audioMIDI.com. I will do my best to select the questions that seem to stump the most people.
As always, stay tuned to the audioMIDI.com eNews for the latest reviews and new product info.
| 
