Plugin MIDI Filtering and Automation
Each plugin (both instruments and insert effects) contains a MIDI Routing map. The MIDI Routing map changes MIDI input events before they enter the plugin. Examples of routing and filtering include masking out MIDI input, re-channelizing it, layering across channels, limiting key ranges, transposing keys, and many advanced operations on MIDI CC events.
|•||Each plugin has a full set of MIDI Routing options|
|•||Each plugin's MIDI routing is independently configurable for each scene|
Open the plugin console for the plugin and select the MIDI Routing tab.
The MIDI Routing tab configures channel-specific MIDI input settings.
Each MIDI input port can be either enabled or disabled. If enabled, each input channel can be remapped and layered. In the above picture channel 6 is layered to channel 5 and channel 6. Each MIDI event (e.g. notes) on channel 6 is duplicated and sent to the instrument both on channel 5 and channel 6.
Right click a row in the To column to make changes to this mapping. Click the triangle icon to expand or collapse portions of the channel display.
Right click the To column on the port row to enable or disable the entire port, disable all its channels, reset channels to a 1-1 map (unity), or map all channels to channel 1.
For each MIDI input port and channel from/to pair you can independently configure:
|•||What MIDI note ranges a instrument will respond to (splits and layers configuration)|
|•||How incoming MIDI notes will be transposed (after note range filtering)|
|•||How incoming MIDI continuous controller data is remapped to different controller numbers.|
Use the Quick MIDI Routing button to quickly set up basic channel routing.
The menu item “Full Reset” resets all port mappings and then applies the selected port/channel. The menu item “Port Reset” only changes the port selected while leaving other ports unaffected.
Use the Advanced MIDI Channel Routing dialog to configure channel from/to pairs using a convenient matrix view:
Right click on a MIDI port to alter how events are filtered for this plugin.
|•||Copy/Paste enables you to copy the MIDI routing for one port to another|
|•||Copy to all ports on this plugin enables you to duplicate the configuration of one port to all ports on this plugin only.|
|•||Copy port to all scenes copies the port configuration to all other scenes for this plugin and this port|
Click Save to save the MIDI Routing of the currently selected port.
Clock Open/Load to load a MIDI Routing into the currently selected port.
Press Save to save a configuration. This includes for each MIDI input:
This enables frequently used MIDI configuration parameters to be applied to other Instrument Modules or stored for future use. When a MIDI Configuration is loaded you may optionally load or ignore specific portions of the configuration.
Tip: Each MIDI Configuration file stores information about a single MIDI port. If you save a file, it will reflect the configuration of the currently selected port (if a channel from/to pair is selected beneath it, it will still save the parent port info.) When you load a MIDI Configuration file, it is loaded into the current port. This makes it useful to save MIDI Configuration files that are “device-specific” because devices are attached to ports.
A last-used MIDI configuration is always saved with an Instrument Module. Usually, this MIDI configuration will be reloaded automatically on any future Instrument Module using the same instrument. However, if you select a MIDI configuration to be the default, it will be used instead. This ‘paperclip’ icon will be displayed with a green color if a default exists for this instrument module. Double clicking the button erases any existing default.