6.0
Table Of Contents
- Table of Contents
- About this manual
- 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
- Startup Options
- 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
- Playback and the Transport panel
- Recording
- Quantizing MIDI and audio
- Fades and crossfades
- The arranger track (Cubase Elements only)
- Using markers
- The Mixer
- Audio effects
- VST instruments and instrument tracks
- Automation
- Audio processing and functions
- The Sample Editor
- The Audio Part Editor
- The Pool
- The MediaBay
- Working with track presets
- Remote controlling Cubase
- MIDI realtime parameters
- Using MIDI devices
- MIDI processing
- The MIDI editors
- Introduction
- Opening a MIDI editor
- The Key Editor – Overview
- Key Editor operations
- The Drum Editor – Overview
- Drum Editor operations
- Working with drum maps
- Using drum name lists
- Working with SysEx messages
- Recording SysEx parameter changes
- Editing SysEx messages
- The Score Editor – Overview
- Score Editor operations
- Editing tempo and signature
- Export Audio Mixdown
- Synchronization
- Video
- ReWire (not in Cubase LE)
- File handling
- Customizing
- Key commands
- Index
92
Quantizing MIDI and audio
Freeze MIDI Quantize
The Freeze MIDI Quantize function on the Edit menu,
Advanced Quantize submenu, makes the start and end
positions of MIDI events permanent. This is useful in situa-
tions where you want to quantize a second time, based on
the current quantized positions rather than the original
positions.
Create Groove Quantize Preset
This lets you create a groove quantize preset from a MIDI
part, a sliced audio part, or an audio event containing
hitpoints.
To extract the timing, i. e. generate a groove quantize map
based on hitpoints that you have created in the Sample
Editor, proceed as follows:
1. Open the Sample Editor for the audio event from
which you want to extract the timing.
2. Create and edit hitpoints.
For further information, see “Working with hitpoints and slices” on page
186.
3. On the Hitpoints tab in the Sample Editor, click the
“Create Groove” button.
The groove is extracted.
If you open the Quantize pop-up menu on the Project win-
dow toolbar, you will find an additional item at the bottom
of the list, with the same name as the file from which you
have extracted the groove. You can select it as a base for
quantizing, just like any other quantize value.
4. To save the groove, open the Quantize Panel and store
it as a preset, see
“Save/Remove Preset” on page 92.
The Quantize Panel
You can open the Quantize Panel by clicking on the corre-
sponding button on the toolbar or by opening the Edit
menu and selecting “Quantize Panel”.
Using the Quantize Panel, you can quantize audio or MIDI
to the grid or to a groove. Depending on what method you
choose, different parameters are shown on the Quantize
Panel. However, there is also a set of common settings.
Common settings
Quantize Presets pop-up menu
On this pop-up menu, you can select a quantize or a
groove preset.
Save/Remove Preset
The preset controls allow you to store the current settings
as a preset, making them available on all Quantize Presets
pop-up menus. To save a preset, proceed as follows:
1. Set up the quantize parameters as desired.
This includes Swing, Catch Range, etc.
2. Click the Save Preset button (the plus sign) to the
right of the Quantize Presets pop-up menu.
A preset name is generated automatically, according to your settings.
• If you want to rename the preset, open the Quantize
Presets pop-up menu, select “Rename Preset” and enter
the desired name in the dialog that appears.
• To remove a user preset, select it and click the “Remove
Preset” button.
Non-Quantize
This setting allows you to set a “distance” in ticks (120
ticks correspond to one 16th note), so that events that are
within the specified distance from the nearest quantize
grid position are not quantized. This allows you to keep
slight variations when you quantize, but still correct notes
that are too far away from the grid.