User manual
Table Of Contents
- Table of Contents
- Part I: Getting into the details
- About this manual
- VST Connections: Setting up input and output busses
- The Project window
- Playback and the Transport panel
- Recording
- Fades, crossfades and envelopes
- The Arranger track
- Folder tracks
- Using markers
- The Transpose functions
- The mixer
- Control Room (Cubase only)
- Audio effects
- VST Instruments and Instrument tracks
- Introduction
- VST Instrument channels vs. instrument tracks
- VST Instrument channels
- Instrument tracks
- Comparison
- Automation considerations
- What do I need? Instrument channel or Instrument track?
- Instrument Freeze
- VST instruments and processor load
- Using presets for VSTi configuration
- About latency
- External instruments (Cubase only)
- Surround sound (Cubase only)
- Audio processing and functions
- The Sample Editor
- The Audio Part Editor
- The Pool
- VST Sound
- The MediaBay
- Track Presets
- Track Quick Controls
- Automation
- MIDI realtime parameters and effects
- MIDI processing and quantizing
- The MIDI editors
- The Logical Editor, Transformer and Input Transformer
- The Project Logical Editor
- Working with System Exclusive messages
- Working with the Tempo track
- The Project Browser
- Export Audio Mixdown
- Synchronization
- Video
- ReWire
- File handling
- Customizing
- Key commands
- Part II: Score layout and printing
- How the Score Editor works
- The basics
- About this chapter
- Preparations
- Opening the Score Editor
- The project cursor
- Page Mode
- Changing the Zoom factor
- The active staff
- Making page setup settings
- Designing your work space
- About the Score Editor context menus
- About dialogs in the Score Editor
- Setting key, clef and time signature
- Transposing instruments
- Working order
- Force update
- Transcribing MIDI recordings
- About this chapter
- About transcription
- Getting the parts ready
- Strategies: Preparing parts for score printout
- Staff settings
- The Main tab
- The Options tab
- The Polyphonic tab
- The Tablature tab
- Situations which require additional techniques
- Inserting display quantize changes
- Strategies: Adding display quantize changes
- The Explode function
- Using “Scores Notes To MIDI”
- Entering and editing notes
- About this chapter
- Score settings
- Note values and positions
- Adding and editing notes
- Selecting notes
- Moving notes
- Duplicating notes
- Cut, copy and paste
- Editing pitches of individual notes
- Changing the length of notes
- Splitting a note in two
- Working with the Display Quantize tool
- Split (piano) staves
- Strategies: Multiple staves
- Inserting and editing clefs, keys or time signatures
- Deleting notes
- Staff settings
- Polyphonic voicing
- About this chapter
- Background: Polyphonic voicing
- Setting up the voices
- Strategies: How many voices do I need?
- Entering notes into voices
- Checking which voice a note belongs to
- Moving notes between voices
- Handling rests
- Voices and display quantize
- Creating crossed voicings
- Automatic polyphonic voicing - Merge All Staves
- Converting voices to tracks - Extract Voices
- Additional note and rest formatting
- Working with symbols
- Working with chords
- Working with text
- Working with layouts
- Working with MusicXML
- Designing your score: additional techniques
- Scoring for drums
- Creating tablature
- The score and MIDI playback
- Printing and exporting pages
- Frequently asked questions
- Tips and Tricks
- Index
212
Automation
Where did the automation data I recorded end
up?
When using global Write automation, you can write auto-
mation data on the automation tracks of all channels. In
the previous write operations, you probably added auto-
mation events for many different channels and parameters.
• To view all the automation events you recorded during
the operations, select “Show All Used Automation” from
the Track Folding submenu of the Project menu.
Now the automation data for every channel parameter that you adjusted
in the mixer during Write mode is shown on corresponding subtracks in
the Project window. The automation events recorded are shown as
points in the automation curves.
Working with automation curves
About automation curves
There are two kinds of automation curves, “ramp” and
“jump”:
• Jump curves are created for any parameter that only has
on/off values, like a Mute button, for example.
• Ramp curves are created for any parameter that gener-
ates continuous multiple values, such as fader or dial
movements etc.
Examples of jump and ramp automation curves shown in the event dis-
play.
About the static value line
When you first open an automation subtrack for a para-
meter, it doesn’t contain any automation events (unless
you have previously adjusted that parameter with write au-
tomation activated), and this is reflected in the event dis-
play as a straight horizontal black line, the “static value”
line. This line represents the current parameter setting.
• If you have manually added any automation events or
used write automation for the corresponding parameter,
and then deactivate Read mode, the automation curve will
be greyed-out in the automation subtrack event display
and the static value will be used instead.
As soon as Read mode is activated, the automation curve will become
available.
Editing automation events
Drawing automation events
By using write automation in the mixer, you generate auto-
mation events by moving parameter dials and faders in the
mixer. You can also add them manually by drawing automa-
tion curves on an automation subtrack. Proceed as follows:
1. Show the automation subtrack by clicking on the left
edge of the track in the Track list.
The static value line is shown in the event display for the automation sub-
track.
2. Select the Pencil tool.
You can also use the various modes of the Line tool for drawing curves,
see below.
3. If you click on the static value line, an automation event
is added, read automation mode is automatically activated,
and the static value line changes to a blue automation
curve.
4. If you click and hold, you can draw a curve by adding a
multitude of single automation events.