Steinberg Cubase SE 3 MIDI Devices And Features Manual

							4
Logical Presets, Transformer
and Input Transformer 
						

							CUBASE SE4 – 52 Logical Presets, Transformer and Input Transformer
Introduction
About the Logical Presets
Most of the time you will probably perform your MIDI editing graphi-
cally, from one of the main graphic editors. But there are times when 
you want more of a “search and replace” function on MIDI data, and 
that’s where the Logical Presets come in and allow you to perform 
very powerful processing.
The Logical Presets are found in the MIDI menu.
•To apply a preset, select it from the Logical Presets submenu.
This applies the preset to the selected MIDI part directly.
• It is also possible to select and apply Logical Editor presets directly in 
the List Editor (from the Mask menu).
About the Transformer MIDI effect
The Transformer effect allows you to apply editing to the events played 
back from a track “on the fly”.
About the Input Transformer
Just like the Transformer effect, the Input Transformer works in real 
time. However, the Input Transformer filters out and transforms MIDI 
data as it is recorded. In other words, the settings you make in the 
Input Transformer will affect the actual MIDI events you record. 
						

							CUBASE SELogical Presets, Transformer and Input Transformer 4 – 53
Setting up filter conditions
General procedure
The upper list is where you set up the filter conditions, determining 
which events to find. The list contains one or several conditions, each 
on a separate line.
• If you want to start from scratch (as opposed to basing your settings on 
an existing preset) you may want to initialize the settings by clicking the 
Init button.
•To add a new line (condition) click the Add Line button to the right.
The new line is added at the bottom of the list. If there are many lines, you may need to 
use the scrollbar to the right to view them.
•To remove a line, click anywhere on it to select it and click the Delete 
Line button to the right.
You set up a filter condition line by clicking in the columns and selecting 
options from the pop-up menus that appear. Here is a brief description 
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 Logical Editor should compare the property 
in the Filter Target column to the values in the Parameter columns 
(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).   
						

							CUBASE SE4 – 54 Logical Presets, Transformer and Input Transformer
Conditions
The options in the Condition column have the following meaning (note 
that the available Condition options depend on the Filter Target setting):
• The Conditions for the “Property” filter target are different, see page 58.
Below, the different Filter Targets (and their corresponding Condition 
and Parameter options) are described in more detail.
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 inside (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 60.
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 column.
Bigger …has a value higher than the one set up in the Parameter 1 column.
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 column.
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 Parameter 1 
and Parameter 2 columns.
Note is equal to …is the note specified in the Parameter 1 column, regardless of oc-
tave (Pitch only). Lets you find e.g. all C notes, in all octaves. Column Description 
						

							CUBASE SELogical Presets, Transformer and Input Transformer 4 – 55
Searching for notes of certain lengths
Only note events have lengths (actually, a note is made up of separate 
note-on and note-off events but in Cubase SE it’s considered as a 
single event with a length). Therefore, the “Length” Filter Target is only 
valid if you’re specifically searching for notes – there has to be another 
condition line with the Filter Target “Type”, Condition “Equal” and Pa-
rameter 1 set to “Note”. See page 60 for more about using multiple fil-
ter conditions.
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, 
searching 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”, specifying 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, 
displayed 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 SE4 – 56 Logical Presets, Transformer and 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 Logical Editor 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”, 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 60 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 
Input 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.  
						

							CUBASE SELogical Presets, Transformer and Input Transformer 4 – 57
Searching for MIDI channels
Each MIDI event contains a MIDI channel setting (1-16). Normally, 
these settings are not used, since the MIDI event plays back on the 
MIDI channel set for its track. However, you can come across MIDI 
parts with events set to different channels in the following scenarios 
for example:
• If you have recorded MIDI from an instrument sending on several different 
channels (e.g. a master keyboard with different key zones).
• If you have imported a MIDI file of type 0 (with a single track, containing MIDI 
events with different channel settings).
Searching for MIDI channel values is straightforward; you select a 
Condition and enter a MIDI channel (1-16) in the Parameter 1 column 
(and, if you’ve selected one of the Range Conditions, a higher channel 
in the Parameter 2 column, creating a value range).
Searching for event types
Selecting Type as the Filter Target allows you to find events of a cer-
tain type only.
• The Condition column contains only three options: Equal, Unequal and All 
Types.
• Clicking the Parameter 1 column displays a pop-up menu, listing the available 
event types (Note, PolyPressure, Controller, etc.).
The Input Transformer will find all events matching or not matching the 
selected type (depending on the Condition).
As mentioned above, selecting Type = Note or Type = Controller adds 
some additional functionality to the Input Transformer. You should 
make it a habit to add a Type condition when applicable. 
						

							CUBASE SE4 – 58 Logical Presets, Transformer and Input Transformer
Searching for properties
On the Filter Target pop-up menu you will find an option called Prop-
erty. This allows you to search for properties that are not part of the 
MIDI standard but rather event-specific Cubase SE settings.
When the Property option is selected, the Condition column has two 
options: “Property is set” and “Property is not set”. Which property to 
look for is selected in the Parameter 1 column. The options are “muted” 
and “selected”. Two examples:
Here, the Input Transformer will find all muted events.
Here, the Input Transformer will find all events that are selected but not muted. 
						

							CUBASE SELogical Presets, Transformer and Input Transformer 4 – 59
Searching for event contexts
On the Filter Target pop-up menu you will find an option called “Last 
Event”. This can be used to perform context dependant searches.
"Last Event" indicates the state of an event which has already passed 
the Input Transformer. The condition has to be combined with Para-
meter 1 and Parameter 2. 
A few examples on how the Last Event filter target can used:
Here, the action will only be performed when sustain pedal is down:
In this example, the action will be performed when the note C1 is 
pressed:
In this example, the action will be performed after playing the C1 note:
Fiter Target Condition Parameter 1 Parameter 2
Last Event Equal MIDI Status 176/Controller
Last Event Equal Value 1 64
Last Event Bigger Value 2 64
Fiter Target Condition Parameter 1 Parameter 2
Type is Equal Note 
Last Event Equal Note is playing 36/C1
Fiter Target Condition Parameter 1 Parameter 2
Last Event Equal Value 1 36/C1 
						

							CUBASE SE4 – 60 Logical Presets, Transformer and Input Transformer
Combining multiple condition lines
As described above, you can add condition lines by clicking the Add 
Line button to the right of the list. The result of combining condition 
lines depends on the boolean And/Or operators.
The bool column
By clicking in the “bool” column to the right in the list, you can select 
a boolean operator: “And” or “Or”. A boolean operator separates two 
condition lines and determines the result in the following way:
• If two condition lines are separated by a boolean And, both conditions 
must be fulfilled for an event to be found.
The Input Transformer will only find events that are notes and are muted.
• If two condition lines are separated by a boolean Or, one of the conditions 
(or both) must be fulfilled for an event to be found.
The Input Transformer will find all events that are notes (regardless of mute status) 
and all events that are muted (regardless of their type).
When you add a new condition line, the boolean setting defaults to And. 
Therefore, if all you want to do is set up two or more conditions that all 
must be met for an event to be found, you don’t have to think about the 
boolean column – just add the required lines and make the usual filter 
settings.