5.0
Table Of Contents
- Table of Contents
- 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 mixer
- Audio effects
- VST Instruments and Instrument tracks
- Automation
- Audio processing and functions
- The Sample Editor
- The Audio Part Editor
- The Pool
- Working with Track Presets
- Remote controlling Cubase AI
- MIDI realtime parameters
- MIDI processing and quantizing
- 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
- The List Editor - Overview
- List Editor operations
- Working with System Exclusive messages
- Recording System Exclusive parameter changes
- Editing System Exclusive messages
- The Score Editor - Overview
- Score Editor operations
- Editing tempo and signature
- Export Audio Mixdown
- Synchronization
- Video
- File handling
- Customizing
- Key commands
- Index
58
Recording
Say, for instance, that you record one or several bass
parts on track 2. If you now set another track, like track 55,
to the same output and MIDI channel as track 2, you can
make a separate recording of just pitchbends for the bass
parts on track 55. This means that you activate recording
as usual and only move the pitchbend wheel during the
take. As long as the two tracks are set to the same output
and MIDI channel, it will appear to the MIDI instrument as
if the two recordings were made at the same time.
Program Change messages
Normally, when you switch from one program to another
on your keyboard (or whatever you use to record), a num-
ber corresponding to that program is sent out via MIDI as
a Program Change message. These can be recorded on
the fly with the music, recorded afterwards on a separate
track, or manually entered in the Key or List Editors.
System Exclusive messages
System Exclusive (SysEx) is a special type of MIDI mes-
sage used to send data that only makes sense to a unit of
a certain make and type. SysEx can be used to transmit a
list of the numbers that make up the settings of one or
more sounds in a synth. For details about viewing and ed-
iting SysEx messages, see the section “Working with Sys-
tem Exclusive messages” on page 210.
The Reset function
The Reset function on the MIDI menu sends out note-off
messages and resets controllers on all MIDI channels.
This is sometimes necessary if you experience hanging
notes, constant vibrato, etc.
There are two other options to perform a reset:
• Cubase AI can automatically perform a MIDI reset on
stop.
You can turn this function on or off in the Preferences (MIDI page).
• Cubase AI can automatically insert a reset event at the
end of a recorded part.
Open the Preferences (MIDI page) and activate the option “Insert Reset
Events after Record”. The inserted Reset event will reset controller data
such as Sustain, Aftertouch, Pitchbend, Modulation, Breath Control, etc.
This is useful if a MIDI part is recorded and e.g. the Sustain pedal is still
held after stopping recording. Usually, this would cause all following parts
to be played with Sustain, as the Pedal Off command was not recorded.
This can be prevented by activating “Insert Reset Events after Record”.
Retrospective Record
This feature allows you to capture any MIDI notes you play
in Stop mode or during playback and turn them into a MIDI
part “after the fact”. This is possible due to the fact that
Cubase AI can capture MIDI input in buffer memory, even
when not recording.
Proceed as follows:
1. Enable the Retrospective Record option in the Prefer-
ences (Record–MIDI page).
This activates the buffering of MIDI input, making Retrospective Record
possible.
2. Make sure a MIDI track is record-enabled.
3. When you have played some MIDI material you want
to capture (either in Stop mode or during playback), select
Retrospective Record from the Transport menu (or use
the key command, by default [Shift]-Num[*]).
The content of the MIDI buffer (i.e. what you just played) is
turned into a MIDI part on the record enabled track. The
part will appear where the project cursor was when you
started playing – this means that if you played along during
playback, the captured notes will end up exactly where you
played them in relation to the project.
• The Retrospective Record Buffer Size setting in the
Preferences (Record–MIDI page) determines how much
data can be captured.
MIDI Preferences
There are several other options and settings in the Prefer-
ences that affect MIDI recording and playback:
MIDI page
• Length Adjustment
Adjusts the length of notes so that there is always a short time between the
end of one note and the start of another (of the same pitch and on the
same MIDI channel). The time is set in ticks. By default there are 120 ticks
per 1/16 note.
Record–MIDI page
• Snap MIDI Parts to Bars
When this is activated, recorded MIDI parts will automatically be length-
ened to start and end at whole bar positions. If you are working in a
Bars+Beats-based context, this can make editing (moving, duplicating,
repeating, etc.) easier.