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
577
Note Expression
Note Expression and MIDI
The dialog contains the following options:
2. When you have made the desired settings, click OK to close the dialog.
The settings you made in the Note Expression MIDI Setup dialog will be used
every time that you use the “Convert to Note Expression” function or record MIDI
controllers as Note Expression data.
Recording MIDI controllers as Note Expression data
To record Note Expression data using standard MIDI controller messages, activate
the “MIDI as Note Expression” button on the Note Expression Inspector tab and enter
the notes and controllers using your MIDI device. Afterwards, you can copy, paste and
move the notes and the associated controller data will follow.
However, you should not shift individual notes from a chord, because this leads to
conflicting controller messages. One way to avoid such conflicts is to record MIDI
controllers as Note Expression data for monophonic performances only. Another
option is to use a MIDI track set to “Any” channel and to split polyphony to separate
channels. This is useful when working with guitar-to-MIDI controllers, where each
string sends on a separate MIDI channel.
Ö When recording MIDI controllers as Note Expression data, keep in mind that this only
works within the limits of standard MIDI controllers. With the exception of Poly
Pressure, all MIDI controllers are channel-specific messages and therefore not
available for notes.
Converting MIDI Controllers into Note Expression data
You can also convert the MIDI controller data on the controller lanes into Note
Expression data.
Proceed as follows:
1. Open the MIDI part in the Key Editor.
2. Make sure that the MIDI controllers to be recorded are activated in the “Note
Expression MIDI Setup” dialog.
Option Description
Controller Activate this option if you want to use MIDI controllers when working
with Note Expression. In the table below, activate the MIDI controllers
you want to use and deactivate the MIDI controllers that should be
disregarded in the Note Expression context.
If MIDI controller data for a deactivated controller is received in Cubase,
it will end up on the controller lane.
Pitchbend Activate this option if you want incoming Pitchbend data to be used
when working with Note Expression.
Aftertouch Activate this option if you want incoming Aftertouch data to be used
when working with Note Expression.
Poly Pressure Activate this option if you want Poly Pressure data to be used when
working with Note Expression.
Controller Catch
Range
This allows you to associate controllers with a note, although they were
sent slightly before the note-on message. Specify the number of ticks in
the value field. For example, this might be necessary when working with
some electronic drums for which the drum head position message is
sent before the note.
!
When you are editing the MIDI notes after recording them, it might be necessary to
consolidate the controller data.