User manual

Table Of Contents
202
Automation
MIDI Controller automation
Merging automation data
When working with Cubase, it is possible to record auto-
mation data for MIDI controller data in two places: as MIDI
part data and as data on an automation track.
If you have such “conflicting” automation data, you can
specify separately for every parameter how these will be
combined during playback. This is done by selecting an
Automation Merge mode in the Track list for the automa-
tion track.
The following options are available:
Ö This pop-up menu is only available for controllers that
can be recorded both for a part and a track. When the
pop-up menu is not available in the Track list, the current
parameter will not cause any playback conflicts.
Ö For a full list of all the parameters with potential auto-
mation data conflicts, open the MIDI Controller Automa-
tion Setup dialog, see below.
Ö The settings you make for a controller are applied to all
MIDI tracks that use this controller.
MIDI Controller Automation Setup settings
In the MIDI Controller Automation Setup dialog, you can
specify how existing MIDI automation should be handled
on playback and where new automation data should be
recorded, in a MIDI part or as track automation.
Proceed as follows:
1. On the MIDI menu, select “MIDI Controller Automation
Setup”.
A dialog opens.
2. On the “Record Destination on conflict (global)” pop-
up menu, specify the record destination for MIDI controller
data.
This determines which destination will be used if there is a
“conflict”, i.e if MIDI controller data is received by Cubase
and both the Record and the Automation Write buttons are
enabled.
Option Description
Use Global
Settings
When this is selected, the automation track uses the
“global” Automation Merge mode specified in the MIDI
Controller Automation Setup dialog, see below.
Replace 1 -
Part Range
When this is selected, the part data has playback prior-
ity over the automation track data, i.e. at the left and
right part borders, the automation mode switches
abruptly from part to track automation, and vice versa.
Replace 2 - Last
Value Continues
Similar to the above, but part automation only begins
when the first controller event within the part is
reached. At the end of the part, the last controller value
will be kept until an automation breakpoint is reached
on the automation track.
Average When this is selected, the average values between part
and track automation will be used.
Modulation In this mode, the automation track curve modulates the
existing part automation, with higher curve points em-
phasizing the automation values and lower curve points
reducing the automation values even further.
The options on
the Automation
Merge Mode
pop-up menu