Steinberg Cubase SE 3 Operation Manual

							CUBASE SE
The MIDI editors 21 – 441
Using drum name lists
Even if no drum map is selected for the edited MIDI track, you can still 
use the Drum Editor if needed. As previously mentioned, the drum 
sound list will then only have four columns: Audition, Pitch, Instrument 
(drum sound names) and Quantize. There will be 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 
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 available. This means you 
can use the drum sound names in any loaded drum map without using 
I-notes and O-notes, should you so like. 
						

							CUBASE SE
21 – 442 The MIDI editors
The List Editor – Overview
The toolbar
The toolbar contains several items that are the same as in the Key 
Editor (edit solo, snap, quantize settings, etc.). These are described 
earlier in this chapter. The following toolbar items are unique to the 
List Editor:
• The Insert pop-up menu is used when creating new events.
This is where you determine what type of event to add (see page 444).
• The Mask pop-up menu and Filter view (Show Filter View button) allow you to 
hide events from view, based on their type and other properties.
See page 447.
•The Value View button can be used for hiding and showing the Value 
display (see below).
The List Editor has no info line (numerical editing is available in the list 
instead).
The list
This lists all events in the currently selected MIDI part(s), in the order 
(from top to bottom) they are played back. You can edit the event 
properties by using regular value editing, as described on page 444.  
						

							CUBASE SE
The MIDI editors 21 – 443
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 or-
der), while the horizontal position corresponds to its actual position in 
the project. This is where you add new parts or events, drag to move 
them, etc.
The value display
This display shows the “value” of each event, allowing for easy view-
ing and graphical editing. Typically, the value shown is the “Data 2” or 
“Value 2” property (amounts for MIDI controller events, velocity for 
notes, etc.). You can show or hide this display by clicking the “Show 
List Value View” button on the toolbar.
List Editor operations
Customizing the view
You can click and drag the divider between the list and the event dis-
play to make one area wider and the other narrower. Furthermore, the 
list can be customized in the following ways:
• You can change the order of the columns by dragging the column headings.
• You can resize columns by dragging the dividers between the column headings.
Setting the display format
Just like in the Project window, you set the display format (bars+beats, 
seconds, etc.) by right-clicking (Win) or [Ctrl]-clicking (Mac) in the ruler 
and selecting an option from the pop-up menu. This setting affects 
both the ruler and all start, end and length values shown in the list.
Zooming
You can change the horizontal magnification in the event display by us-
ing the zoom slider below the display or the Magnification Glass tool. 
						

							CUBASE SE
21 – 444 The MIDI editors
Adding events
To add a new event to the edited part, proceed as follows:
1.Use the Insert pop-up menu on the toolbar to select the event type.
2.Select the Pencil 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 easily be adjusted in the list.
•Notes you enter will get the insert velocity value set in the insert velocity 
field on the toolbar. See page 407.
Editing in the list
The list allows you to perform detailed numerical editing of the events’ 
properties. The columns have the following functionality:
Column Description
L Locate column. An arrow in this column indicates the event that starts 
closest before the project cursor position. If you click in this column for an 
event, the project cursor is moved to the start of that event. Double click-
ing moves the cursor position and starts/stops playback – useful for au-
ditioning when editing in the list.
Type The event type. This cannot be changed.
Start The start position of the event, shown in the format selected for the ruler. 
Changing this is the same as moving the event. Note that moving the 
event past any other event in the list will re-sort the list (the list always 
shows the events in the order they are played back). 
						

							CUBASE SE
The MIDI editors 21 – 445
•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 the list.
However, clicking the Comment column opens the MIDI SysEx Editor, in which you 
can perform detailed editing of system exclusive events – this is described in the sep-
arate “MIDI Devices and Features” pdf.
End This is only used for note events, allowing you to view and edit the end 
position of a note (thereby resizing it).
Length This is only used for note events. It shows the length of the note – chang-
ing this resizes the note and automatically changes the End value as well.
Data 1 This is the “data 1” or “value 1” property of the event. The content of this 
depends on the event type – for notes, this is the pitch, for example. 
Where applicable, the values are shown in the most relevant form. For in-
stance, the Data 1 value for notes is shown as a note number in the for-
mat selected in the Preferences dialog (Event Display–MIDI page). See 
also the table on page 449.
Data 2 This is the “data 2” or “value 2” property of the event. The content of this 
depends on the event type – for notes, this is the velocity value, for exam-
ple. See the table on page 449.
Channel The MIDI channel of the event. Note that this setting is normally overrid-
den by the channel setting for the track. To make a MIDI event play back 
on “its own” channel, set its track to channel “Any” in the Project window.
Comment This column is used for some event types only, providing an additional 
comment about the event. Column Description 
						

							CUBASE SE
21 – 446 The MIDI editors
Editing in the event display
The event display allows you to edit the events graphically using the 
tools on the toolbar. You can edit single events as well as several se-
lected events simultaneously.
•To move an event, click and drag it to a new position.
Note that moving the event past any other event in the display will re-sort the list (the 
list always shows the events in the order they are played back). As a result, the vertical 
position of the event in the display will change as well.
•To make a copy of an event, press [Alt]/[Option] and drag it to a new 
position.
•To resize a note, select it and drag its end point with the Arrow tool as 
in the Project window.
This only works with notes.
•To mute or unmute an event, click on it with the Mute tool.
You can mute or unmute several events in one go by enclosing them in a selection 
rectangle with the Mute tool.
•You can select a color scheme for the events with the Colors pop-up 
menu on the toolbar.
This affects how all MIDI events are shown in the List, Key and Drum editors – see 
page 469.
•To delete an event, select it and press [Backspace] or [Delete], or 
click on it with the Eraser tool in the event display. 
						

							CUBASE SE
The MIDI editors 21 – 447
Filtering
Clicking the “Show Filter View” button on the toolbar opens an addi-
tional filter bar that allows you to hide specific event types from view. 
For example, it may be hard to find note events if the part contains a 
lot of controllers. By hiding these the list becomes more manageable.
To hide an event type, tick its checkbox on the filter view. To see one 
event type only (hide all other event types), press [Ctrl]/[Command] 
and click its checkbox. If you [Ctrl]/[Command]-click again, all check-
boxes are cleared (all events will be visible).
• The event types remain hidden even if you close the filter view.
To make sure you see all events, open the filter view and check that all checkboxes are 
deactivated.
• The filter view does not remove, mute or in any other way change the 
events.
Masking
The Mask function is similar to the filter view but allows you to hide 
events based on other criteria as well. Proceed as follows:
1.Select an event (or several events) of the type you want to view.
2.Pull down the Mask pop-up menu on the toolbar and select one of the 
options.
The results are as follows:
Option Description
Event Types Only events with the type of the selected event will be shown. This 
does the same as the filter view but is quicker if you only want to 
view a single event type.
Event Types and 
Data 1Only events of the same type and with the same “Data 1” value will 
be shown. For example, if a note event is selected, only notes with 
the same pitch will be shown. If a controller event is selected, only 
controllers of the same type will be shown.  
						

							CUBASE SE
21 – 448 The MIDI editors
In addition to the above options, the menu also gives you access to 
the Logical Editor presets (see the separate “MIDI Devices and Fea-
tures” pdf for details).
When you apply any of the presets from the Logical Editor, only the 
events that meet the criteria specified will be visible.
•To deactivate the Mask function, select “Nothing” from the Mask pop-
up menu.
The most typical usage of the Mask function is to view a certain type 
of controller only (e.g. Modulation, Breath Control, etc.). Since these 
are all the same event types (controller), this would not be possible 
using the filter view. With the “Event Types and Data 1” option on the 
Mask pop-up menu, it is!
Event Channels Only events with the same MIDI channel value as the selected 
event will be shown. Option Description 
						

							CUBASE SE
The MIDI editors 21 – 449
Editing in the value display
The value display to the right of the event display is a tool for quick 
viewing and editing of multiple values, e.g. velocities or controller 
amounts. The values are shown as horizontal bars, with the bar length 
corresponding to the value.
A velocity ramp in the value display.
You edit the values by clicking and dragging. Note that the pointer au-
tomatically takes on the shape of the Pencil tool when you move it into 
the value display – you don’t have to select the Pencil tool for this.
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:
Event type Data 1 Data 2 Value display
Note Pitch (note number) Velocity Velocity
Controller Controller type Controller amount Controller amount
Program Change Program number Not used Program number
Aftertouch Aftertouch amount Not used Aftertouch amount
Pitch Bend Bend amount Not used Bend amount
SysEx Not used Not used Not used 
						

							CUBASE SE
21 – 450 The MIDI editors
•The value display can be hidden from view by clicking the “Show List 
Value View” button on the toolbar, so that it is not lit.
The Score Editor – Overview
The Score Editor shows the MIDI notes as a musical score. The win-
dow contains the following sections and items:
The toolbar
The Score Editor toolbar is similar to the toolbar in the Key Editor, with 
the following differences:
• The Score Editor toolbar has a button for showing or hiding the extended 
toolbar (see below).
• There are no active part settings – in the Score Editor, parts on different 
tracks are shown on different staves.
• There is no chord recognition function.