8.0
Table Of Contents
- Table of Contents
- Introduction
- Setting Up Your System
- VST Connections
- Project Window
- Project Handling
- Tracks
- Track Handling
- Adding Tracks
- Removing Tracks
- Moving Tracks in the Track List
- Renaming Tracks
- Coloring Tracks
- Showing Track Pictures
- Setting the Track Height
- Selecting Tracks
- Duplicating Tracks
- Disabling Audio Tracks (Cubase Elements only)
- Organizing Tracks in Folder Tracks
- Handling Overlapping Audio
- How Events are Displayed on Folder Tracks
- Modifying Event Display on Folder Tracks
- Track Presets
- Parts and Events
- Range Editing
- Playback and Transport
- Virtual Keyboard
- Recording
- Quantizing MIDI and Audio
- Fades and crossfades
- Arranger Track (Cubase Elements only)
- Markers
- MixConsole
- Audio Effects
- Audio processing and functions
- Sample Editor
- Audio Part Editor
- Pool
- MediaBay
- Working With the MediaBay
- Setting Up the MediaBay
- Define Locations Section
- Scanning Your Content
- Updating the MediaBay
- Locations Section
- Results Section
- Previewer Section
- Filters Section
- Sound Browser and Mini Browser
- MediaBay Preferences
- MediaBay Key Commands
- Working with MediaBay-Related Windows
- Working With Volume Databases
- Automation
- VST Instruments
- Installing and Managing Plug-ins
- Remote controlling Cubase
- MIDI realtime parameters
- Using MIDI devices
- MIDI Processing
- MIDI Editors
- Chord Functions
- Chord Pads
- Editing tempo and signature
- Export Audio Mixdown
- Synchronization
- Video
- ReWire (not in Cubase LE)
- Key Commands
- File handling
- Customizing
- Optimizing
- Preferences
- Index
Automation
MIDI Part Data vs. Track Automation
361
NOTE
The R button is automatically enabled when you enable the W button. 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 MixConsole toolbar and at the top of the track
list. 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 the R/W buttons of all tracks simultaneously.
MIDI Part Data vs. Track Automation
You can enter or record MIDI controller data in two ways: 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 conflicting data types are combined during playback as follows:
• Part automation only begins when the first 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.
Writing Automation Data
There are two approaches that you can use to create automation curves: manually
and automatically.
• Manual writing makes it easy to quickly change parameter values at specific
points without having to activate playback.
• Automatic writing lets you work almost as if you were using a real mixer.
With both methods, any applied automation data is reflected in both the MixConsole
(a fader will move for example) and in the corresponding automation track curve.
RELATED LINKS
Manual Writing of Automation Data on page 362