Steinberg Cubase 7 User Manual

521
The MIDI editorsWorking with drum maps
Open the Functions pop-up menu in the top left corner to open a list of available 
functionalities:
ÖDrum maps are saved with the project files. If you have created or modified a drum 
map, use the Save function to save it as a separate XML file, available for loading into 
other projects. 
ÖIf you always want to have the same drum map(s) included in your projects, you may 
want to load these into the template – see 
“Save as Template” on page 58.
O-Note...

522
The MIDI editorsUsing drum name lists
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...

523
The MIDI editorsList Editor operations
The event list
This lists all events in the selected MIDI part(s), in the order (from top to bottom) in 
which they are played back. You can edit the event properties by using regular value 
editing, see 
“Editing in the list” on page 524.
The event display
This shows the events graphically. The vertical position of an event in the display 
corresponds to its entry in the list (i.
 e. to the playback order), while the horizontal 
position corresponds to its...

524
The MIDI editorsList Editor operations
2.Select the Draw tool and click in the event display at the desired position (relative 
to the ruler).
If you are creating note events, you can click and drag to set the length of the note.
The new event appears in the list and in the display. Its properties will be set to default 
values, but can be adjusted in the list.
•Notes will get the insert velocity value set in the Insert Velocity field on the toolbar, 
see 
“Setting velocity values” on page 494....

525
The MIDI editorsList Editor operations
•You can edit several events at once. If several events are selected and you edit a 
value for one event, the other selected events’ values will be changed as well.
Normally, any initial value differences between the events will be maintained – i. e. 
the values will change by the same amount. If you press [Ctrl]/[Command] when 
you edit, however, all events will get the same value.
ÖFor SysEx (system exclusive) events, you can only edit the position (Start) in...

526
The MIDI editorsList Editor operations
•In the top section, the following options are available:
•Cubase only: In addition to these options, the menu also gives you access to the 
presets available in the Logical Editor. Using the “Setup…” item, you can directly 
open the Logical Editor. In this editor, you can create very complex filter settings 
(see the chapter 
“The Logical Editor, Transformer, and Input Transformer” on page 
580). 
When you apply any of the Logical presets or use the Logical...

527
The MIDI editorsWorking with SysEx messages
Exactly which value is shown for an event depends on the event type. The following 
table shows what is displayed and edited in the Data columns and the value display:
•For note events there will also be a value in the Data 3 column, which is used for 
note-off velocity.
•Note that for SMF and text events no values are displayed.
Working with SysEx messages
SysEx (System Exclusive) messages are model-specific messages for setting various 
parameters of a...

528
The MIDI editorsWorking with SysEx messages
Proceed as follows:
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...

529
The MIDI editorsRecording SysEx parameter changes
Some advice
•Do not transmit more data than you need. If all you want is a single program, do not 
send them all, it will only make it harder to find the one you want. Usually, you can 
specify exactly what you want to send.
•If you want the sequencer to dump the pertinent sounds to your instrument each 
time you load a project, put the SysEx data in a silent “count-in” before the project 
itself starts.
•If the dump is very short (for instance, a...

530
The MIDI editorsEditing SysEx messages
•To open the MIDI SysEx Editor for an event, click in the Comments column for the 
event in the List Editor/Project Browser.
The display shows the entire message on one or several lines. SysEx messages 
always begin with F0 and end with F7 with a number of arbitrary bytes in between. If 
the message contains more bytes than fit on one line, it continues on the next. The 
Address indication to the left helps you find out on which position in the message a...