User manual
Table Of Contents
- Table of Contents
- Introduction
- Part I: Getting into the details
- Setting up your system
- VST Connections
- The Project window
- Working with projects
- Creating new projects
- Opening projects
- Closing projects
- Saving projects
- The Archive and Backup functions
- The Project Setup dialog
- Zoom and view options
- Audio handling
- Auditioning audio parts and events
- Scrubbing audio
- Editing parts and events
- Range editing
- Region operations
- The Edit History dialog
- The Preferences dialog
- Working with tracks and lanes
- Playback and the Transport panel
- Recording
- Quantizing MIDI and Audio
- Introduction
- Quantizing Audio Event Starts
- AudioWarp Quantize (Cubase Only)
- Quantizing MIDI Event Starts
- Quantizing MIDI Event Lengths
- Quantizing MIDI Event Ends
- Quantizing Multiple Audio Tracks (Cubase Only)
- AudioWarp Quantizing Multiple Audio Tracks (Cubase Only)
- The Quantize Panel
- Additional Quantizing Functions
- Fades, crossfades, and envelopes
- The arranger track
- The transpose functions
- Using markers
- The MixConsole
- Overview
- Configuring the MixConsole
- Keyboard Navigation in the MixConsole
- Working with the Fader Section
- Working with the Channel Racks
- Linking Channels (Cubase only)
- Metering (Cubase only)
- Using Channel Settings
- Saving and Loading Selected Channel Settings
- Resetting MixConsole Channels
- Adding Pictures
- Adding Notes
- The Control Room (Cubase only)
- Audio effects
- VST instruments and instrument tracks
- Surround sound (Cubase only)
- Automation
- Audio processing and functions
- The Sample Editor
- The Audio Part Editor
- The Pool
- The MediaBay
- Introduction
- Working with the MediaBay
- The Define Locations section
- The Locations section
- The Results list
- Previewing files
- The Filters section
- The Attribute Inspector
- The Loop Browser, Sound Browser, and Mini Browser windows
- Preferences
- Key commands
- Working with MediaBay-related windows
- Working with Volume databases
- Working with track presets
- Track Quick Controls
- Remote controlling Cubase
- MIDI realtime parameters and effects
- Using MIDI devices
- MIDI processing
- The MIDI editors
- Introduction
- Opening a MIDI editor
- The Key Editor – Overview
- Key Editor operations
- The In-Place Editor
- The Drum Editor – Overview
- Drum Editor operations
- Working with drum maps
- Using drum name lists
- The List Editor – Overview
- List Editor operations
- Working with SysEx messages
- Recording SysEx parameter changes
- Editing SysEx messages
- The basic Score Editor – Overview
- Score Editor operations
- Working with the Chord Functions
- Introduction
- The Chord Track
- The Chord Track Inspector Section
- The Chord Editor
- The Chord Assistant (Cubase only)
- Creating a Chord Progression from Scratch (Chords to MIDI)
- Extracting Chords from MIDI (Make Chords)
- Controlling MIDI or Audio Playback with the Chord Track (Follow Chords)
- Assigning Chord Events to MIDI Effects or VST Instruments
- Expression maps (Cubase only)
- Note Expression
- The Logical Editor, Transformer, and Input Transformer
- The Project Logical Editor (Cubase only)
- Editing tempo and signature
- The Project Browser (Cubase only)
- Export Audio Mixdown
- Synchronization
- Video
- ReWire
- File handling
- Customizing
- Key commands
- Part II: Score layout and printing (Cubase only)
- How the Score Editor works
- The basics
- About this chapter
- Preparations
- Opening the Score Editor
- The project cursor
- Playing back and recording
- 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 clef, key, and time signature
- Transposing instruments
- Printing from the Score Editor
- Exporting pages as image files
- Working order
- Force update
- Transcribing MIDI recordings
- 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
- About this chapter
- Layout settings
- Staff size
- Hiding/showing objects
- Coloring notes
- Multiple rests
- Editing existing bar lines
- Creating upbeats
- Setting the number of bars across the page
- Moving bar lines
- Dragging staves
- Adding brackets and braces
- Displaying the Chord Symbols from the Chord Track
- Auto Layout
- Reset Layout
- Breaking bar lines
- Scoring for drums
- Creating tablature
- The score and MIDI playback
- Tips and Tricks
- Index
135
Quantizing MIDI and Audio
Quantizing MIDI Event Starts
AudioWarp quantize prevents warp markers from ending up on the same position. If
conflicts occur, only one of the warp markers is quantized. For example, if you use a
quantize value of 1/4 on audio that is based on sixteenth notes, the warp markers at
the quarter-note positions are quantized to the grid, and the remaining warp markers
are moved, keeping the relative distances between the warp markers.
You can also apply AudioWarp quantizing to selection ranges in the Project window
and in the Sample Editor. To avoid moving transient positions that lie outside the
selection range, additional warp markers are created at the closest hitpoint positions
outside the range.
Applying AudioWarp Quantizing
1. Select the audio event that you want to quantize.
2. On the toolbar, activate the “AudioWarp Quantize” button, open the “Quantize
Presets” pop-up menu, and select a preset to determine the quantize grid.
3. Open the Edit menu, and select Quantize.
You can also use the Quantize Panel for applying AudioWarp quantizing. The
Quantize Panel provides more parameters for defining the quantize grid, see
“The
Quantize Panel” on page 136.
Quantizing MIDI Event Starts
If you select MIDI notes in a part and use the Quantize function on the Edit menu, the
MIDI note starts are quantized, that is, the starts of MIDI notes that do not match exact
note positions are moved to the closest grid positions. The grid is set up on the
Quantize pop-up menu. The note lengths are maintained.
Ö If you quantize MIDI parts, all events are quantized, even if none is selected.
Quantizing MIDI Event Lengths
The “Quantize MIDI Event Lengths” function on the Edit menu, Advanced Quantize
submenu, quantizes the lengths of MIDI notes without changing their start positions.
At its most basic level, this function sets the lengths of the notes to the Length
Quantize value on the MIDI editor toolbar by cutting off the note ends.
However, if you have selected the “Quantize Link” option on the “Length Quantize”
pop-up menu, the function resizes the notes according to the quantize grid, taking the
Swing, Tuplet, and Catch Range settings into account.
Quantizing MIDI Event Ends
The “Quantize MIDI Event Ends” function on the Edit menu, Advanced Quantize
submenu, moves the ends of your MIDI notes to the nearest grid positions, taking the
Quantize pop-up menu setting into account.
Quantizing Multiple Audio Tracks (Cubase Only)
You can quantize multiple audio tracks at the same time. To maintain phase
coherence, all tracks have to be sliced at exactly the same start and end positions.
Only then the resulting slices can be quantized without risk of getting phase errors.
Ö For this to work, the audio tracks must reside in the same folder track and the “=”
button for Group Editing must be activated. Furthermore, at least one of the tracks
must contain hitpoints.