Types of actions

Actions are used in expression maps to determine how individual switches are controlled in order to trigger the required playback technique or combination of playback techniques. Dorico Pro supports multiple types of actions, as different sound libraries require different actions.

Control change actions

Control change actions use MIDI CC events to modulate sounds. They are particularly useful when using sound libraries whose sounds can be manipulated incrementally, such as increasing/decreasing the string vibrato intensity.

Program change actions

Program change actions use MIDI PC events to switch to different sounds. They are particularly useful when using sound libraries, such as General MIDI, that use separate programs for each playback technique or combinations of instrument sounds and effects presets.

Key switch actions

Key switch actions use MIDI note events to switch to different sounds. They are particularly useful when recording MIDI live, as you can press the specified notes on a MIDI keyboard to trigger key switch actions while simultaneously playing the notes you want to record. Usually, key switch actions are mapped to notes in the lowest octave of the MIDI keyboard as they are rarely used for note input.

Key switch actions are also known as “note events”.

Absolute channel change actions

Absolute channel change actions switch to a specific, explicitly numbered channel. They are particularly useful for sound libraries that have separate plug-in instances for each individual instrument. For example, you might use an absolute channel change action to switch from “natural” on channel 1 to “pizzicato” on channel 2 in your viola section plug-in instance.

Relative channel change actions

Relative channel change actions switch to a channel numbered relative to the starting channel. They are particularly useful for sound libraries that have multiple instruments with separate playback technique channels in the same plug-in instance, as they can switch between playback techniques according to their relative channel number rather than an absolute number. For example, if you have four trumpet instruments loaded in the same plug-in instance, each with three channels for different playback techniques, and want to use the same switches for all four trumpets, you might use a relative channel change action to switch from the “natural” original channel to “muted” on the +1 relative channel.

Relative channel numbers relate to the original channel number of the endpoint for the corresponding instrument. A 0 relative channel change switches back to the original channel.

Tip

You can add actions to individual switches in the Expression Maps dialog.