6.0
Table Of Contents
- Table of Contents
- 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
- Playback and the Transport panel
- Recording
- Quantizing MIDI and audio
- Fades and crossfades
- The arranger track (Cubase Elements only)
- Using markers
- The Mixer
- Audio effects
- VST instruments and instrument tracks
- Automation
- Audio processing and functions
- The Sample Editor
- The Audio Part Editor
- The Pool
- The MediaBay
- Working with track presets
- Remote controlling Cubase
- MIDI realtime parameters
- Using MIDI devices
- MIDI processing
- 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
- Working with SysEx messages
- Recording SysEx parameter changes
- Editing SysEx messages
- The Score Editor – Overview
- Score Editor operations
- Editing tempo and signature
- Export Audio Mixdown
- Synchronization
- Video
- ReWire (not in Cubase LE)
- File handling
- Customizing
- Key commands
- Index
279
The MIDI editors
Using drum name lists
Even if no drum map is selected for the edited MIDI track,
you can still use the Drum Editor. As previously mentioned,
the drum sound list then only has four columns: Audition,
Pitch, Instrument (drum sound name), and Quantize. There
is 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 menu 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.
Working with SysEx messages
SysEx (System Exclusive) messages are model-specific
messages for setting various parameters of a MIDI device.
This makes it possible to address device parameters that
would not be available via normal MIDI syntax.
Every major MIDI manufacturer has its own SysEx identity
code. SysEx messages are typically used for transmitting
patch data, i.
e. the numbers that make up the settings of
one or more sounds in a MIDI instrument.
Cubase allows you to record and manipulate SysEx data
in various ways. The following sections point to various
features that help you manage and create SysEx data.
To learn about the possibilities of the MIDI Device Man-
ager for controlling your device, see the chapter “Using
MIDI devices” on page 238.
Bulk dumps
Recording a bulk dump in Cubase
In any programmable device, the settings are stored as
numbers in computer memory. Change those numbers,
and you will change the settings.
Normally, MIDI devices allow you to dump (transmit) all or
some settings in the device’s memory in the form of MIDI
SysEx messages. A dump is therefore (among other
things) a way of making backup copies of the settings of
your instrument: sending such a dump back to the MIDI
device will restore the settings.
If your instrument allows the dumping of a few or all of its
settings via MIDI by activating some function on the front
panel, this dump will probably be recordable in Cubase.
1. Open the Preferences dialog from the File menu (on
the Mac, this is located on the Cubase menu) and select
the MIDI–MIDI Filter page.
This allows you to govern which MIDI event types are recorded and/or
thru-put.
2. Make sure that recording of SysEx data is not filtered,
by deactivating the SysEx checkbox in the Record section.
The SysEx checkbox in the Thru section can be left as it is
(by default activated).
This way, SysEx messages will be recorded but not echoed back out to
the instrument (which might lead to unpredictable results).
3. Activate recording on a MIDI track and initiate the
dump from the front panel of the instrument.
4. When done recording, open the part in the Key Editor
and open the controller lane for it.
This allows you to check that the SysEx dump was recorded – there
should be one or several SysEx events in the controller lane.