Steinberg Cubase LE Operation Manual

							CUBASE LEThe MIDI Editors 19 – 411
• Drum maps are saved with the project files. If you have created or modi-
fied a drum map, you should use the Save function to store it as a sepa-
rate 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 default project – see page 504.
O-Note Conversion
This function on the MIDI menu goes through the selected MIDI part(s) 
and sets the actual pitch of each note according to its O-note setting. 
This is useful if you want to convert the track to a “regular” MIDI track 
(with no drum map) and still have the notes play back the correct drum 
sound. A typical application is if you want to export your MIDI record-
ing as a standard MIDI file (see page 507) – by first performing an O-
Note Conversion you make sure that your drum tracks play back as 
they should when they are exported.
Load Opens a file dialog, allowing you to load drum maps from disk. On the Cu-
base LE CD you will find a number of drum maps for different MIDI instru-
ments – use this function to load the desired maps into your project.
Save Opens a file dialog for saving the drum map selected in the list. If you have 
created or modified a drum map, you should use this function to save it as 
a file on disk – this allows you to load it into other projects. Drum map files 
have the extension “.drm”.
Assign Click this button to assign the selected drum map to the current MIDI 
track (only available if a MIDI track was selected when you opened the 
Drum Map Setup dialog). This is the same as selecting the drum map from 
the Map pop-up menu.
OK Closes the dialog. Button Description 
						

							CUBASE LE19 – 412 The MIDI Editors 
						

							20
The Input Transformer 
						

							CUBASE LE20 – 414 The Input Transformer
Introduction
The Input Transformer function allows you to selectively filter out and 
change MIDI data coming to a MIDI track, before it is recorded. There 
are four independent “modules”, for which you can set up different fil-
tering and actions if you like. You can activate any or all of these four 
modules.
Here are some of the things the Input Transformer allows you to do:
• Make up split keyboard combinations for recording left and right hands sepa-
rately.
• Turn a controller like a foot pedal into MIDI notes (for playing bass drum the 
right way).
• Filter out one specific type of MIDI data on one MIDI channel only.
• Turn aftertouch into any controller (and vice versa).
• Invert velocity or pitch.
And again: four of these things can be done at the same time.
Opening the Input Transformer
To open the Input Transformer for a MIDI track, select the track and 
click the Input Transformer button in the Inspector. 
						

							CUBASE LEThe Input Transformer 20 – 415
Handling the four modules
The Input Transformer actually consists of four separate transformers, 
or modules.
•You select which module to view and make settings for by clicking its 
button in the Selected Module section.
Module 2 selected for viewing and editing.
•The checkboxes in the Active Module section determine which mod-
ules are active.
Here, modules 1, 2 and 4 are active.
The two modes
The Mode pop-up menu contains two modes: Filter and Transform.
•In Filter mode, only the filter conditions (the upper list) are taken into 
account. All events matching the conditions set up will be filtered out 
(excluded from the recording).
•In Transform mode, events matching the filter conditions will be trans-
formed according to the settings in the action list (the lower list). 
						

							CUBASE LE20 – 416 The Input Transformer
Setting up filtering and actions
Here is a brief rundown:
•Click the Add Line buttons to add lines to the filter condition list or 
action list.
To remove a line, click it to select it and click the Delete Line button to the right.
•Clicking the columns in the filter condition list brings up pop-up 
menus, allowing you to specify the conditions to match.
•Clicking the columns in the action list brings up pop-up menus, allow-
ing you to specify what should be done to the found events (when 
Transform mode is selected).
•The Input Transformer settings are active as soon as you activate an 
Active Module checkbox.
The settings made in the activated modules will affect all MIDI data you record on the 
track.
• Closing the Input Transformer window does not turn it off – you need to 
deactivate all Active Module checkboxes for this!
A lit Input Transformer button in the Inspector indicates that one or more modules are 
active.
The Input Transformer filters out and transforms MIDI data as it is re-
corded. In other words, the settings you make in the Input Transformer 
will affect the actual MIDI events you record.  
						

							CUBASE LEThe Input Transformer 20 – 417
Setting up filter conditions
The different columns
You set up a filter condition line by clicking in the columns and select-
ing options from the pop-up menus that appear. Here is a brief de-
scription of the columns:
Column Description
Filter Target Here you select which property to look for when finding events. Your 
choice here affects the available options in the other columns as well, 
see below!
Condition This determines how the Input Transformer should compare the prop-
erty in the Filter Target column to the values in the Parameter col-
umns (Equal, Unequal, Bigger, etc. – see the separate table below). 
The available options depend on the Filter Target setting.
Parameter 1 Here you set which value the event properties should be compared 
to (a numeric value or a choice from a pop-up menu, depending on 
the Filter Target).
Parameter 2 This column is only used if you have selected one of the “Range” op-
tions in the Condition column. Typically, this allows you to find all 
events with values within (or outside) the range between Parameter 1 
and Parameter 2.
bool This allows you to insert the boolean operators And/Or, when creat-
ing conditions with multiple lines. See page 422. 
						

							CUBASE LE20 – 418 The Input Transformer
Conditions
The options in the Condition column have the following meaning 
(please note that the available Condition options depend on the Filter 
Target setting):
Below, the different Filter Targets (and their corresponding Condition 
and Parameter options) are described in more detail.
Condition Events will be found if their Filter Target property...
Equal ...has the exact same value as set up in the Parameter 1 column.
Unequal ...has any value other than the one set up in the Parameter 1 col-
umn.
Bigger ...has a value higher than the one set up in the Parameter 1 col-
umn.
Bigger or Equal ...has a value that is the same as or higher than the one set up in 
the Parameter 1 column.
Less ...has a value lower than the one set up in the Parameter 1 col-
umn.
Less or Equal ...has a value that is the same as or lower than the one set up in 
the Parameter 1 column.
Inside Range ...has a value that is between the values set up in the Parameter 1 
and Parameter 2 columns. Note that Parameter 1 should be the 
lower value and Parameter 2 the higher.
Outside Range ...has a value that is not between the values set up in the Param-
eter 1 and Parameter 2 columns.
Note is equal to ...is the note specified in the Parameter 1 column, regardless of 
octave (Pitch only). Lets you find e.g. all C notes, in all octaves. 
						

							CUBASE LEThe Input Transformer 20 – 419
Searching for Value 1 or Value 2
A MIDI event is composed of several values. The meanings of value 1 
and 2 depend on the type of event:
• System Exclusive events are not included in the table above, since they 
don’t use value 1 and 2.
Since value 1 and 2 have different meanings for different events, search-
ing for e.g. value 2 = 64 would both find notes with the velocity 64 and 
controllers with the amount 64, etc. If this is not what you want, you can 
add an additional filter condition line with the Filter Target “Type”, speci-
fying which type of events to find (see below).
❐This is particularly useful when searching for note pitch or velocity values, 
as described below.
Event type Value 1 Value 2
Notes The Note Number/Pitch. The velocity of the note.
PolyPressure The key that was pressed. The amount of pressure for the key.
Controller The type of Controller, dis-
played as a number.The amount of Control Change.
Program Change The Program Change number. Not used.
Aftertouch The amount of pressure. Not used.
Pitchbend The “fine tune” of the bend. 
Not always used.The coarse amount of bend. 
						

							CUBASE LE20 – 420 The Input Transformer
The general procedures when searching for value 1 or 2 are:
• If you select any Condition other than the Range options, you set up a specific 
value in the Parameter 1 column.
Here, the Input Transformer will find all events with a value 2 less than 80.
• If you select the Inside or Outside Range option in the Condition column, the 
range consists of the values between Parameter 1 and Parameter 2. 
Note that Parameter 1 should have the lower value.
Searching for note pitch or velocity
If you add another condition line with the Filter Target “Type”, Condition 
“Equal” and Parameter 1 set to “Note”, the Input Transformer will 
“know” you are searching for pitch or velocity. This has the following 
benefits:
• The Filter Targets Value 1 and Value 2 will be displayed as “Pitch” and “Veloc-
ity” respectively, making it easier to grasp the function of the filter condition.
• Pitch values in the Parameter columns will be displayed as note names (C3, 
D#4, etc.). When entering pitch values you can either type a note name or a 
MIDI note number (0-127).
• When Value 1 (pitch) is selected as Filter Target, an additional option appears 
in the Condition column: “Note is equal to”. When this is selected, you specify 
a note name in the Parameter 1 column but without any octave number (C, 
C#, D, D#, etc.). The Input Transformer can then find all notes of a certain key, 
in all octaves.
See page 422 for more info on working with multiple filter condition 
lines.
Searching for controllers
There is similar extended functionality when searching for controllers: 
If you’ve added an additional “Type = Controller” condition line, the In-
put Transformer will “know” you are searching for controllers. The 
Parameter 1 column will then show the names of the MIDI controllers 
(Modulation, Volume, etc.) when Value 1 is selected as Filter Target.