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
- The Transpose functions
- The mixer
- 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
- Working with Track Presets
- Track Quick Controls
- Remote controlling Cubase
- MIDI realtime parameters and effects
- Using MIDI devices
- MIDI processing and quantizing
- 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 System Exclusive messages
- Recording System Exclusive parameter changes
- Editing System Exclusive messages
- VST Expression
- The Logical Editor, Transformer and Input Transformer
- The Project Logical Editor
- Editing tempo and signature
- 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
- 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 key, clef 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
- Scoring for drums
- Creating tablature
- The score and MIDI playback
- Tips and Tricks
- Index
355
The MIDI editors
Deleting events in the controller display
You delete events by clicking on them with the Eraser tool
or by selecting them and pressing [Backspace]. Please
note:
• Deleting a controller event makes the last event before
this valid up until the next event. It does not “zero” any
controller changes.
• You can delete notes by deleting their velocity bars in
the controller display.
Please be aware that if there is more than one note on the same position,
there may still only be one velocity bar visible – make sure you delete only
the desired notes!
Editing continuous controllers on the controller lane
When a continuous controller is selected for a controller
lane, additional data is displayed on the controller lane.
This is due to the fact that MIDI controller data can be re-
corded (or entered) either for an automation track or for a
MIDI part (see “MIDI Controller automation” on page 202).
The following applies:
• In the controller pop-up menu, an asterisk is displayed
next to the controller name if automation data already ex-
ists for this controller.
This can be either controller data you entered in a MIDI editor (the data
will then be displayed on the controller lane), or controller data recorded
on an automation track in the Project window (in which case no events
are displayed on the controller lane).
For this controller, automation data is available.
• If conflicting controller data exists in two different
places, you can specify what will happen on playback by
making settings for the Automation Merge Mode (see
“Merging automation data” on page 202). The resulting
curve is displayed in addition to the curve you entered on
the controller lane.
• On the controller lane, you can also see the controller
curve that is applied before the part starts. That way, you
know which controller value (if any) is currently being used
at the starting point of the part so that you can choose the
start value accordingly.
Note that this value also depends on the Automation Merge Mode.
Adding and editing Poly Pressure events
Poly Pressure events are special, in that they “belong to” a
specific note number (key). That is, each Poly Pressure
event has two editable values: the note number and the
amount of pressure. Therefore, when Poly Pressure is se-
lected on the event type pop-up menu, there are two value
fields to the left of the controller display, one for the note
number and one for the amount.
Controller curve entered on
the controller lane
Resulting controller curve (if controller
automation was also recorded on a
track). These values depend on the
selected Automation Merge Mode.
The controller curve before the part starts. This curve depends on the
existing controller data (if any) and on the selected Merge Mode.