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
362
The MIDI editors
Open the Functions pop-up menu in the top left corner to
open a list of available functionalities:
Ö Drum maps are saved with the project files. If you have
created or modified a drum map, you should use the Save
function to store it as a separate XML file, available for
loading into other projects.
If you always want to have the same drum map(s) included in your
projects, you may want to load these into the template – see “Save as
Template” on page 451.
O-Note Conversion
This function on the MIDI menu goes through the selected
MIDI part(s) and sets the actual pitch of each note ac-
cording to its O-note setting. This is useful if you want to
convert a track to a “regular” MIDI track (with no drum
map) and still have the notes play back the correct drum
sound. A typical application is if you want to export your
MIDI recording as a standard MIDI file (see “Exporting and
importing standard MIDI files” on page 458) – by first per-
forming an O-Note Conversion you make sure that your
drum tracks play back as they should when they are ex-
ported.
Use Head Pairs and Edit in Scores
These options are explained in detail in the section “Set-
ting up the drum map” on page 616.
Using drum name lists
Even if no drum map is selected for the edited MIDI track,
you can still use the Drum Editor if needed. As previously
mentioned, the drum sound list will then only have four col-
umns: Audition, Pitch, Instrument (drum sound name) and
Quantize. There will be no I-note and O-note functionality.
In this mode, the names shown in the Instrument column
depend on the selection on the Names pop-up menu, just
below the Map pop-up in the Drum Editor.
The options on this pop-up menu are the currently loaded
drum maps plus a “GM Default” item which is always avail-
able. This means you can use the drum sound names in any
loaded drum map without using I-notes and O-notes, if you
want to.
Button Description
New Map Click this to add a new drum map to the project. The
drum sounds will be named “Sound 1, Sound 2” and so
on, and have all parameters set to default values. The
map will be named “Empty Map”, but you can rename it
by clicking and typing in the list.
New Copy Adds a copy of the currently selected drum map. This is
probably the quickest way to create a new drum map: se-
lect the map that is similar to what you want, create a
copy, change the desired drum sound settings and re-
name the map in the list.
Remove Removes the selected drum map from the project.
Load Opens a file dialog, allowing you to load drum maps from
disk. On the Cubase DVD you will find a number of drum
maps for different MIDI instruments – use this function to
load the desired maps into your project.
Save Opens a file dialog for saving the drum map selected in
the list. If you have created or modified a drum map, you
should use this function to save it as a file on disk – this
allows you to load it into other projects. Drum map files
have the extension “.drm”.
Edit head pairs Allows you to customize the note pairs, see “Customizing
note head pairs” on page 617.
Init Display
Notes
Allows you to reset the Display Notes entry to the original
setting, i.e. the Pitch entry.
Close Closes the dialog.