10.0

Table Of Contents
2 Jump curves
Jump curves are created for on/off parameters, such as mute.
Static Value Line
When you open an automation track for the rst time, it does not contain any automation events.
This is reected in the event display as a dotted horizontal line, the static value line. This line
represents the current parameter setting.
If you manually added any automation events or used write automation for the corresponding
parameter and then disable the reading of automation data, the automation curve is grayed out
in the event display and the static value line is used instead.
As soon as Read is enabled, the automation curve is used.
Write/Read Automation
You can automation-enable tracks and MixConsole channels by activating their automation write
W and read R buttons.
If you activate W for a channel, virtually all MixConsole parameters that you adjust during
playback for that specic channel are recorded as automation events.
If R is activated for a channel, all your recorded MixConsole actions for that channel are
performed during playback.
The R and W buttons for a track in the track list are the same as the R and W buttons in the
MixConsole.
NOTE
R is automatically enabled when you enable W. This allows Cubase to read existing automation
data at any time. You can separately deactivate W if you only want to read existing data.
There are also global read and write indicator buttons Activate/Deactivate Read/Write for All
Tracks on the Project window toolbar and the MixConsole toolbar. These buttons light up as
soon as there is an enabled R or W button on any channel/track within your project.
Furthermore, they can be clicked to activate or deactivate R/W of all tracks simultaneously.
MIDI Part Data vs. Track Automation
You can enter or record MIDI controller data as automation data on an automation track or as
part data in the MIDI part.
If Read Automation for a track is enabled, controller data is written as automation data
on an automation track in the Project window.
If Read Automation is disabled, the controller data is written in the MIDI part and can be
viewed and edited for example in the Key Editor.
Nevertheless, you can end up with both kinds of controller data for a MIDI part if you recorded
controller part data in one pass and automation data during another. In this case, these
conicting data types are combined during playback as follows:
Part automation only begins when the rst controller event within the part is reached. At
the end of the part, the last controller value is kept until an automation breakpoint is
reached on the automation track.
Automation
Static Value Line
440