MIDI Controller Map
MIDI Controller mapping is a TP feature that allows midi events to be mapped to controls. This allows you to control TP controls using your midi controllers and hardware. You can load/save presets for the controller map and/or save/load presets from a file. You can either map manually a message or record it from your midi hardware.
The fields of this map are:
- Type of the map, having the value "11" , which is the value for a MIDI controller. You can use any short of MIDI message but usually you 'll want the "Controller" value.
- Msg is the message of the driver, from 0 to 127. The values shown here are 0x7 , which is generally for "master volume" and 0x9 which is generally for "tempo". You can learn more on these messages by reading the MIDI specs.
- Driver is the index of the driver that will execute the map. If you specify "all" , the map is used when the message comes from any midi driver. Otherwise it is processed when it comes from the selected midi driver.
- Channel is the midi channel (1-16) to receive the event. "Any" allows all channels to send commands.
- State is the state of the map. It can be one of the following:
- Static which can only be changed from this dialog.
- Learning which can be changed dynamically. To use the learning mode, click on something and hold the mouse button (for example, the master out volume in the mixer ) and then send a message from your controller. TP will automatically map the controller you have moved to the control you have selected.
- Target is the control which this map controls, or a script command. What is available here depends on your loaded drivers, VSTS, and tracks. For more, see Scripts.
- Target Type is the type of the controller
- 0 - Slider (from 0 min to 127 max). This can be mapped to VST sliders and also Turbo Play volume controls.
- 1 - Slider (negative/positive values). This can be mapped to controls that have positive/negative values. Some MIDI hardware controllers have these controls.
- 2 - Key on (note). This can be mapped to TP menu commands, or Script and other commands (see Scripts).
- 4 - Function Call. Calls a script function (see Scripts) with parameters $type,$msg,$driver,$channel,$state,$targetype and $value.
The dialog box allows you to:
- Load defaults
- Apply "static" or "learning" to selected values.
- Save or load a mapping to a TPCMAP file. Note that the mapping is also saved in the TP project file.
- Reload the current map or discard changes.
Controller Map Presets can also be loaded from Scripts.
In case you want to generate a message with your controllers, press the "Open MIDI Mapping Explorer" button. TP will wait for your controller's messages, display them there, and when you double click them you will be able to assign commands to them. The commands available depend on what your current configuration is, for more, see Scripts.
When you want to map VST Automation Parameters, you can also enable the "Learning" flag in the VST editor and the necessary entry in the Controller Map is created automatically when you click an automation parameter in the VST. For more, see VSTs.