User manual
Table Of Contents
- Table of Contents
- Part I: Getting into the details
- 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 and lanes
- Playback and the Transport panel
- Recording
- Quantizing MIDI and audio
- Fades, crossfades and envelopes
- The arranger track
- The transpose functions
- Using markers
- 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
- 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
- Expression maps (Cubase only)
- Note Expression (Cubase only)
- 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
- Scoring for drums
- Creating tablature
- The score and MIDI playback
- Tips and Tricks
- Index
431
Note Expression (Cubase only)
In the lower part of the Note Expression tab, the following
global settings and parameters are available:
Showing/hiding controllers
You can specify which parameters are displayed in the
Note Expression editor and in the event display by activat
-
ing/deactivating them in the leftmost column in the list.
When you want to edit a single parameter, it might be best
to hide the data for the other parameters. Activating sev
-
eral parameters allows you to view them in context, giving
you a better overview. In the Inspector, visible controllers
are shown with a filled rectangle in front of their name.
Hidden controllers are shown with an empty rectangle. To
show or hide a parameter, click on its rectangle.
Filtering the list
If you click on the Parameter column header, a pop-up
menu opens, containing the following filter commands:
Bypassing Note Expression
Like for most other Inspector tabs, you can bypass the
Note Expression settings by clicking on the button at the
top right of the Inspector tab, so that it lights up yellow. If
Bypass is activated, all Note Expression data will be by
-
passed for the track.
Bypass is active for the Note Expression Inspector tab.
Mapping controllers
External keyboards have no controls or faders for VST 3
parameters, which can therefore not be recorded directly.
To remedy this, you have the possibility to assign a certain
MIDI controller (or Pitchbend and Aftertouch) to any of the
Note Expression parameters in the list. The MIDI assign
-
ment is shown in the CC column in the Inspector.
The same MIDI controller can be used for several parame-
ters, but only one of these controllers can be active at a
time. If the mapping is active, the number for the assigned
MIDI controller is displayed (or PB and AT for Pitchbend
and Aftertouch, respectively). If a MIDI controller is as
-
signed but inactive, e. g., because the selected parameter
uses the same assignment as another parameter, a dot is
shown in the CC column.
The VST 3 parameter Tuning is automatically assigned to
the pitchbend wheel of your MIDI controller. All other pa
-
rameters are assigned by default to the first MIDI control-
ler (CC1: Modulation).
You can manually specify the record mapping for the pa-
rameters, use the MIDI Learn function, or load a mapping
preset, see below.
Manual mapping
To manually map a MIDI controller to the selected Note
Expression parameter, you can select the MIDI controller
from the MIDI assignment pop-up menu. If the MIDI con
-
troller you are looking for is not on the list, select “MIDI
Controller Setup…” and activate it in the dialog. This is
the same as selecting which controllers are available for
the controller lanes in the Key Editor, see
“Selecting the
event type” on page 389.
Option Description
MIDI as Note
Express
ion
If this button is activated, incoming MIDI controllers will
be recorded as Note Expression data, see
“Recording
MIDI controllers as Note Expression data” on page 438.
Overdub When this is activated, you can overdub existing Note
Expression data. See
“Overdubbing” on page 432.
Latch Buffer With this button, you can activate/deactivate the latch
buffer used for overdub recording, see
“Latch mode”
on page 433.
Option Description
Show only used
Parameters
Select this command to only display the parame-
ters in the list for which data exists.
Make all Parameters
visible
Select this command to display all available pa-
rameters in the event display.
Make only edited
Parameter visible
Select this command to display only the currently
edited parameter in the event display.
This controller
is visible.
This controller
is hidden.










