Steinberg Cubase Studio 4 Operation Manual Studio Manual

							331
MIDI processing and quantizing
Freeze MIDI Modifiers
The “Freeze MIDI Modifiers” function affects the following 
settings for MIDI tracks:
 Several settings on the main tab of the Inspector (program 
and bank selection and the Delay parameter).
 The settings on the MIDI Modifiers tab (i.e. Transpose, Veloc-
ity Shift, Velocity Compression and Length Compression).
 The settings on the MIDI Inserts tab (if, e. g., you are using an ar-
peggiator and want to convert the added notes to real events).
The following settings for MIDI parts are taken into account 
as well:
 The Transpose and Velocity settings for parts displayed on the 
info line – the Volume setting is not taken into account. 
To use the “Freeze MIDI Modifiers” function, proceed as 
follows:
1.Select the desired MIDI track.
2.Pull down the MIDI menu and select “Freeze MIDI 
Modifiers”.
The Inspector settings will be converted to MIDI events and inserted at 
the beginning of the part(s). All notes of the part(s) will be modified ac-
cordingly and the Inspector settings will be reset.
Merge MIDI in Loop
The function “Merge MIDI in Loop” combines all MIDI 
events on all unmuted tracks, applies MIDI modifiers and 
effects and generates a new MIDI part, containing all the 
events as you would hear them play back. Proceed as fol-
lows:
1.Make sure only the desired MIDI track(s) are unmuted.
If you only want to include events from a single track in the merge opera-
tion, you may want to solo the track.
2.Set up the left and right locator around the area you 
want to merge.
Only events starting within this area will be included.
3.Select the track on which you want the new part to be 
created.
This can be a new track or an existing track. Data in the cycle area on the 
track can be kept or overwritten (see below).
4.Select “Merge MIDI in Loop” from the MIDI menu.
A dialog appears with the following options:
5.Click OK.
A new part is created between the locators on the destination track, con-
taining the processed MIDI events.
Applying effects to a single part
Normally, the MIDI modifiers and effects affect a whole 
MIDI track. This may not always be what you want – you 
may want to apply some MIDI effects to a single part for 
example (without having to create a separate track for that 
part only). The Merge MIDI in Loop function can help:
1.Set up your MIDI modifiers and MIDI effects the way 
you want them for the part.
This will of course affect the whole track, but focus on the part for now.
2.Set the locators to encompass the part.
Simply select the part and choose Locators to Selection from the Trans-
port menu (or use the corresponding key command, by default [P]).
3.Make sure the track holding the part is selected in the 
Track list.
4.Select Merge MIDI in Loop.
5.In the dialog that appears, activate the desired effect 
options, make sure that Erase Destination is activated and 
click OK.
Now a new part is created on the same track, containing the processed 
events. The original part is deleted.
6.Turn off or reset all MIDI modifiers and effects, so that 
the track plays back as usual.
Option Description
Include Inserts If this is activated, any MIDI insert effects currently acti-
vated for the track(s) will be applied.
Include Sends If this is activated, any MIDI send effects currently acti-
vated for the track(s) will be applied.
Erase 
DestinationIf this is activated, all MIDI data between the left and right 
locator on the destination track will be deleted.
Include Chase If this is activated, events placed outside the selected part 
but relating to it will be included in the processing, e. g. a 
Program Change right before the left locator. For more 
about chase events, see “About Chase” on page 64. 
						

							332
MIDI processing and quantizing
Dissolve Part
The Dissolve Part function on the MIDI menu has two sep-
arate uses:
When you work with MIDI parts (on MIDI channel “Any”) 
containing events on different MIDI channels.
Dissolve Part separates the events according to MIDI channel.
When you want to separate MIDI events according to 
pitch.
A typical example would be drum and percussion tracks, where each 
pitch usually corresponds to a separate drum sound.
ÖWhen dissolving a part into either separate channels 
or separate pitches, you can automatically remove the si-
lent (empty) areas of the resulting parts by activating the 
“Optimized Display” checkbox in the Dissolve Part dialog.
Dissolving parts into separate channels
Setting a track to MIDI channel “Any” will cause each MIDI 
event to play back on its original MIDI channel, rather than 
a channel set for the whole track. There are two main situ-
ations when “Any” channel tracks are useful:
When you record several MIDI channels at the same 
time.
You may for example have a MIDI keyboard with several keyboard zones, 
where each zone sends MIDI on a separate channel. Recording on an 
“Any” channel track allows you to play back the recording with different 
sounds for each zone (since the different MIDI notes play back on sepa-
rate MIDI channels).
When you have imported a MIDI file of Type 0.
MIDI files of Type 0 contain only one track, with notes on up to 16 different 
MIDI channels. If you were to set this track to a specific MIDI channel, all 
notes in the MIDI file would be played back with the same sound; setting 
the track to “Any” will cause the imported file to play back as intended.
The Dissolve Part function scans MIDI parts for events on 
different MIDI channels and distributes the events into new 
parts on new tracks, one for each MIDI channel found. This 
allows you to work with each musical part individually. Pro-
ceed as follows:
1.Select the part(s) containing MIDI data on different 
channels.
2.Select “Dissolve Part” from the MIDI menu.
3.In the dialog that appears, select the “Separate Chan-
nels” option.Now, for each MIDI channel used in the selected part(s), a 
new MIDI track is created and set to the corresponding 
MIDI channel. Each event is then copied into the part on 
the track with the corresponding MIDI channel. Finally, the 
original part(s) are muted.
An example:
Dissolving parts into separate pitches
The Dissolve Part function can also scan MIDI parts for 
events of different pitches, and distribute the events into 
new parts on new tracks, one for each pitch. This is useful 
when the different pitches are not used in a regular me-
lodic context, but rather for separating different sounds 
(e.g. MIDI drum tracks or sampler sound FX tracks). By 
dissolving such parts, you can work with each sound indi-
vidually, on a separate track. Proceed as follows:
1.Select the part(s) containing MIDI data.
2.Select “Dissolve Part” from the MIDI menu.
3.In the dialog that appears, select the “Separate 
Pitches” option.
A new MIDI track is created for each used pitch in the selected part(s). 
The events are then copied into the parts on the track for the corres-
ponding pitch. Finally, the original part(s) are muted.
This part contains events on 
MIDI channel 1, 2 and 3.
Selecting “Dissolve Part” creates new parts on new tracks, 
set to channel 1, 2 and 3. Each new part contains only the 
events on the respective MIDI channel.
The original MIDI 
part is muted. 
						

							333
MIDI processing and quantizing
O-Note Conversion
See “Working with drum maps” on page 359 for more in-
formation on drum maps and O-Notes.
Repeat Loop
With this function, the events inside the independent track 
loops will be repeated until the end of the part, i. e. the 
notes that were previously only played repeatedly are now 
actual notes on the MIDI track. Events to the right of the 
independent track loop (within the same part) will be re-
placed by this function. For more information about inde-
pendent track loops, see “The independent track loop” on 
page 342.
Other MIDI functions
The following items can be found in the Functions sub-
menu of the MIDI menu:
Legato
Extends each selected note so that it reaches the next note.
You can specify the desired gap or overlap with the “Legato 
Overlap” setting in the Preferences (Editing–MIDI page).
When using Legato with this setting, each note will be extended to end 
5 ticks before the next note.
When you activate the “Legato Mode: Selected Only” op-
tion, the length of the note will be adjusted so that it 
reaches the next selected note, allowing you e.g. to only ap-
ply Legato to your bass line (when playing on a keyboard).
Fixed Lengths
This function resizes all selected notes to the length set 
with the Length Quantize pop-up menu on the MIDI editor 
toolbar.
Delete Doubles
This function removes double notes, i.e. notes of the same 
pitch on the exact same position. Double notes can occur 
when recording in Cycle mode, after Quantizing, etc.
Delete Controllers
This function removes all MIDI controllers from the se-
lected MIDI parts.
Delete Continuous Controllers
This function removes all “continuous” MIDI controller 
events from the selected MIDI parts. Therefore, “on/off” 
events such as sustain pedal events are not removed.
!This function is only available from within the MIDI 
editors.
!This function always affects whole MIDI parts.
!This function always affects whole MIDI parts.
!This function always affects whole MIDI parts. 
						

							334
MIDI processing and quantizing
Delete Notes
Allows you to delete very short or weak notes. This is use-
ful for automatically removing unwanted “ghost notes” af-
ter recording. Selecting “Delete Notes…” opens a dialog 
in which you set up the criteria for the function.
The parameters have the following functionality:
Minimum Length
When the Minimum Length checkbox is activated, the 
note length is taken into account, allowing you to remove 
short notes. You can either specify the minimum length 
(for notes to be kept) in the value display or by dragging 
the blue line in the graphical length display below.
The graphical length display can correspond to 1/4 bar, 
one bar, two bars or four bars.
You change this setting by clicking in the field to the right of the display.
In this case, the whole length display corresponds to two bars, and the 
Minimum Length is set to 1/32nd notes (60 ticks).
Minimum Velocity
When the Minimum Velocity checkbox is activated, the ve-
locity of notes is taken into account, allowing you to re-
move weak notes. You specify the minimum velocity (for 
notes to be kept) in the value display.
Remove when under
This setting is only available when both Minimum Length 
and Minimum Velocity is activated. By clicking the value 
display, you select whether both length and velocity crite-
ria must be met for notes to be deleted, or whether one of 
the criteria will suffice.
OK and Cancel
Clicking OK performs the automatic delete according to 
the rules set up. Clicking Cancel closes the dialog without 
deleting notes.
Restrict Polyphony
Selecting this item opens a dialog in which you can spec-
ify how many “voices” should be used (for the selected 
notes or parts). Restricting the polyphony this way is use-
ful when you have an instrument with limited polyphony 
and want to make sure all notes will be played. The effect 
is achieved by shortening notes as required, so that they 
end before the next note starts.
Pedals to Note Length
This function scans for Sustain pedal on/off events, length-
ens the affected notes to match the Sustain pedal off posi-
tion, and then removes the Sustain Controller on/off events.
Delete Overlaps (mono)
This function allows you to make sure that no notes of the 
same pitch overlap (i.e. that one starts before the other 
ends). Overlapping notes of the same pitch can confuse 
some MIDI instruments (a new Note On is transmitted be-
fore the Note Off is transmitted). This command can then 
be used to automatically solve the problem.
Delete Overlaps (poly)
This function shortens notes when required, so that no 
note begins before another ends. This happens regard-
less of which pitch the notes have.
Velocity
This function opens a dialog that allows you to manipulate 
the velocity of notes in various ways. 
						

							335
MIDI processing and quantizing
The following types of velocity processing are available:
Add/Subtract
This simply adds a fixed number to the existing velocity 
values. You set the value (positive or negative) with the 
Amount parameter.
Compress/Expand
Compresses or expands the “dynamic range” of MIDI 
notes by scaling the velocity values according to the Ratio 
setting (0 – 300%). The principle behind this is that multi-
plying different velocity values with a factor higher than 1 
(over 100%) will also make the differences between ve-
locity values greater, while using a factor lower than 1 (un-
der 100%) will make the differences smaller. In short:
To compress (“even out” velocity differences), use ratio 
values below 100%.
After compression, you would probably want to add a velocity amount 
(with the Add/Subtract function) to maintain the average velocity level. 
To expand (create greater difference in velocity), use ra-
tio values above 100%.
Before you expand, you may want to adjust the velocity with the Add/
Subtract function, so that the average velocity is somewhere in the mid-
dle of the range. If the average velocity is high (near 127) or low (near 0), 
expansion will not work properly, simply because velocity values can only 
be between 0 and 127!
Limit
This function allows you to make sure that no velocity val-
ues fall outside a given range (the Lower and Upper val-
ues). Any velocity values outside this range are raised/
lowered to exactly the Lower/Upper values.
Fixed Velocity
This function sets the velocity of all selected notes to the 
Insert Velocity value on the toolbar in the MIDI editors.
Thin Out Data
Thins out MIDI data. Use this to ease the load on your ex-
ternal MIDI devices if you have recorded very dense con-
troller curves etc. 
You can also manually thin out the controller data by using 
the quantize function in the Key Editor.
Extract MIDI Automation
This option allows you to automatically convert continuous 
controller data of a MIDI part into MIDI track automation 
data. Proceed as follows:
1.Select the desired MIDI part containing the continuous 
controller data.
2.Select “Extract MIDI Automation”. (This command is 
also available on the Key Editor context menu.)
The controller data will automatically be removed from the controller lane 
in the editor.
3.In the Project window, open the automation track(s) 
for the respective MIDI track. You will find that an automa-
tion track has been created for each of the continuous 
controllers in the part.
ÖPlease note that this function can only be used for con-
tinuous controllers. Data such as Aftertouch, Pitchbend or 
SysEx cannot be converted to MIDI track automation data.
ÖRemember that to be able to hear the automation data, 
you have to activate the Read button for the respective au-
tomation track(s).
Reverse
This function inverts the order of the selected events (or of 
all events in the selected parts), causing the MIDI music to 
play backwards. Note that the effect is different from re-
versing an audio recording. With MIDI, the individual notes 
will still play as usual in the MIDI instrument – it’s only the 
order of playback that is changed.
Merge Tempo from Tapping
This function allows you to create a complete tempo track 
based on your tapping, see the section “Merge Tempo 
From Tapping” on page 402.
!This is an extremely useful function as it allows you to 
quickly and easily convert the continuous controllers 
of your recorded MIDI parts into MIDI track automa-
tion data, making them available for editing in the 
Project window. 
						

							27
The MIDI editors 
						

							337
The MIDI editors
About editing MIDI
There are several ways to edit MIDI in Cubase. You can 
use the tools and functions in the Project window for 
large-scale editing, or use the functions on the MIDI menu 
to process MIDI parts in various ways (see “What is affec-
ted by the MIDI functions?” on page 325). For hands-on 
graphical editing of the contents of MIDI parts, you use the 
MIDI editors:
The Key Editor is the default MIDI editor, presenting 
notes graphically in an intuitive piano roll-style grid.
The Key Editor also allows for detailed editing of non-note events such 
as MIDI controllers. For more information, see “The Key Editor – Over-
view” on page 339.
The Score Editor shows MIDI notes as a musical score 
and comes with advanced tools and functions for notation, 
layout and printing.
The Score Editor is described in detail in “Part II: Score layout and prin-
ting” on page 484.
The Drum Editor is similar to the Key Editor, but takes 
advantage of the fact that with drum parts, each key corre-
sponds to a separate drum sound. 
This is the editor to use when you’re editing drum or percussion parts. 
For more information, see “The Drum Editor – Overview” on page 356.
The List Editor shows all events in the selected MIDI 
parts as a list, allowing you to view and edit their proper-
ties numerically.
For more information, see “The List Editor – Overview” on page 363.
The Edit In-Place function allows you to edit MIDI parts 
directly in the Project window.
This is similar to working in the Key Editor, but makes it easier to edit 
MIDI in context with other track types. See “Edit In-Place” on page 354.
You can also edit MIDI in the Project Browser.
Like the List Editor, the Project browser shows the events in a list and al-
lows you to perform numerical editing. However, you will probably find the 
List Editor better suited for MIDI editing, since it has various dedicated fea-
tures and functions for this. The Project Browser is described in the chap-
ter “The Project Browser” on page 407.
ÖYou can define each of the editors mentioned above 
as your default MIDI editor, see below. 
About this chapter
This chapter describes how to use all editors except the 
Score Editor (which is described in detail in “Part II: Score 
layout and printing” on page 484). 
Please note that features that are identical in these editors 
(especially in the Key and Drum Editors) will be described 
in the Key Editor section. The sections about the Drum Ed-
itor (see “The Drum Editor – Overview” on page 356), the 
Inplace-Editor (see “Edit In-Place” on page 354) and the 
List Editor (see “The List Editor – Overview” on page 363) 
describe the specific features of these editors only.
Opening a MIDI editor
There are two ways to open a MIDI editor:
Select one or several parts (or a MIDI track, with no 
parts selected) and select Open Key Editor, Open Score 
Editor, Open Drum Editor, Open List Editor or Open In-
Place Editor from the MIDI menu (or use the correspond-
ing key command).
The selected parts (or all parts on the track, if no part was selected) will 
open in the chosen editor.
Double-click a part to open it in the default editor.
Which editor opens depends on the Default Edit Action setting in the 
Preferences (Event Display–MIDI page).
If the option “Edit as Drums when Drum Map is assigned” 
is activated and a drum map is selected for the edited 
track (see “Selecting a drum map for a track” on page 
361), the Drum Editor will open. This way you can double-
click to open the Key Editor (or the Score Editor, List or 
Edit In-Place Editor, depending on your preferences) but 
drum tracks will automatically open in the Drum Editor. 
						

							338
The MIDI editors
ÖIf the part you open for editing is a shared copy, any ed-
iting you perform will affect all shared copies of this part.
Shared copies are created by pressing [Alt]/[Option]+[Shift] and drag-
ging, or by using the Repeat function with the “Shared copies” option 
activated. In the Project window, shared copies are indicated by the part 
name in italics and an icon in the bottom right corner of the part.
Handling several parts
When you open a MIDI editor with several parts (or a MIDI 
track containing several parts) selected, you might find it 
somewhat hard to get an overview of the different parts 
when editing.
For such cases the editor toolbar features a few functions 
to make working with multiple parts easier and more com-
prehensive:
The Part List menu lists all parts that were selected when 
you opened the editor (or all parts on the track, if no parts 
were selected), and lets you select which part should be 
active for editing.
When you select a part from the list, it is automatically made active and 
centered in the note display.
ÖNote that it is also possible to activate a part by select-
ing an event within this part with the Arrow tool.
The button “Edit Active Part Only” lets you restrict edit-
ing operations to the active part only.
For example, if you select “All” from the Select submenu on the Edit menu 
with this option activated, only events in the active part will be selected. 
Similarly, if you select notes by dragging with the Arrow tool (making a se-
lection rectangle), only the notes in the active part will be selected.
“Edit Active Part Only” activated on the toolbar.
You can zoom in on the active part so that it fills the 
screen by selecting “Zoom to Event” from the Zoom sub-
menu on the Edit menu.The button “Show Part Borders” can be used if you 
want to see clearly defined borders for the active part.
When this is activated, all parts except the active one are grayed out, mak-
ing the borders easily discernible. In the Key Editor, there are also two 
“markers” in the ruler with the name of the active part, marking its begin-
ning and end. These can be moved freely to change the size of the part.
“Show Part Borders” activated on the toolbar.
It is possible to cycle between parts (making them ac-
tive) using key commands.
In the Key Commands dialog – Edit category, you will find two functions for 
this: “Activate Next Part” and “Activate Previous Part”. If you assign key 
commands to these, you can use them to cycle between parts in the edi-
tors. For further information, see “Setting up key commands” on page 476. 
						

							339
The MIDI editors
The Key Editor – Overview 
The toolbar
As in other windows, the toolbar contains tools and vari-
ous settings. You can specify which toolbar items should 
be shown and store/recall different toolbar configurations 
– see “The Setup dialogs” on page 466. 
The info line
The info line shows information about selected MIDI 
notes. You can edit all values on the info line using regular 
value editing (see “Editing on the info line” on page 348 
for details). Length and position values are displayed in 
the format currently selected for the ruler (see below).
To hide or show the info line, click the icon in the toolbar.
Ruler Info line
Toolbar
Note display Controller display
Show/Hide Info line Solo Editor button
Key Editor toolsAutoscroll 
on/off
Audition on/off
Part list
Show/Hide Part 
borders
Edit active 
part only
Auto Select 
Controllers
Nudge ToolsTranspose Palette
Snap on/off
Velocity for inserted notesGrid modes
Indicate Transpositions
Quantize settingsStep Input
MIDI InputStep/MIDI input controls
Color pop-up menu
Independent track 
loop on/off
Loop range (see “The indepen-
dent track loop” on page 342).
Chord recog-
nition display Mouse pointer display: Current 
pitch and meter position
Open Device 
Button 
						

							340
The MIDI editors
The ruler
The ruler shows the time line, by default in the display for-
mat selected on the Transport panel. You can select a 
separate format for a MIDI editor ruler on the Ruler pop-up 
menu, opened by clicking the arrow button to the right of 
it. For a list of the available formats, see “The ruler” on 
page 34.
At the bottom of the pop-up menu, there are two addi-
tional items:
If “Time Linear” is selected, the ruler, note display and 
controller display will be linear in relation to time.
This means that if the ruler shows bars and beats, the distance between 
the bar lines will vary depending on the tempo.
If “Bars+Beats Linear” is selected, the ruler, note display 
and controller display will be linear in relation to tempo.
This means that if the ruler shows bars and beats, the distance between 
beats will be constant.
In most cases, you would probably set the display format 
to “Bars+Beats” in “Bars+Beats Linear” mode when edit-
ing MIDI.
The note display
The note display is the main area in the Key Editor. It con-
tains a grid in which MIDI notes are shown as boxes. The 
width of a box corresponds to the note length, and the 
vertical position of a box corresponds to the note number 
(pitch), with higher notes higher up in the grid. The piano 
keyboard to the left serves as a guide for finding the right 
note number. 
For a description on how to display colors in the note dis-
play, see “Coloring notes and events” on page 343.
The chord recognition function
Cubase features a handy chord recognition function that 
helps you identify chords in the Key Editor note display. To 
find out which chord is formed by simultaneously played 
notes, place the project cursor over the notes. All MIDI 
notes currently “touched” by the project cursor are ana-
lyzed and the chord recognition display in the toolbar 
shows you which chord the notes form.
In the picture above, the project cursor touches the notes C, Eb and G. 
As shown in the chord recognition display, this results in a C minor chord.