Steinberg Cubase SX/SL 3 MIDI Devices And Features Manual

							CUBASE SX/SLThe Logical Editor, Transformer and Input Transformer 4 – 121
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”, the Logical Editor 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 Logical Editor can then find all notes of a certain key, in 
all octaves.
See page 125 for more info on working with multiple filter condition 
lines. 
						

							CUBASE SX/SL4 – 122 The Logical Editor, Transformer and Input Transformer
Searching for controllers
There is similar extended functionality when searching for controllers: 
If you’ve added an additional “Type = Controller” condition line, the 
Logical Editor will “know” you are searching for controllers. The Pa-
rameter 1 column will then show the names of the MIDI controllers 
(Modulation, Volume, etc.) when Value 1 is selected as Filter Target.
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 Logical Editor will find all events matching or not matching the se-
lected type (depending on the Condition).
As mentioned above, selecting Type = Note or Type = Controller adds 
some additional functionality to the Logical Editor. You should make it a 
habit to add a Type condition when applicable. 
						

							CUBASE SX/SLThe Logical Editor, Transformer and Input Transformer 4 – 123
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 SX/SL 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 Logical Editor will find all muted events.
Here, the Logical Editor will find all events that are selected but not muted. 
						

							CUBASE SX/SL4 – 124 The Logical Editor, Transformer and Input Transformer
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 
(especially useful in the Input Transformer).
"Last Event" indicates the state of an event which has already passed 
the Input Transformer/Logical Editor. The condition has to be com-
bined with Parameter 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 (the “Note is playing” condition is only available in the Input 
Transformer and in the Transformer effect):
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 SX/SLThe Logical Editor, Transformer and Input Transformer 4 – 125
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 and the brackets.
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 Logical Editor will only find events that are notes and start at the beginning of 
the third bar.
•If two condition lines are separated by a boolean Or, one of the condi-
tions (or both) must be fulfilled for an event to be found.
The Logical Editor will find all events that are notes (regardless of their position) 
and all events starting at the beginning of the third bar (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. 
						

							CUBASE SX/SL4 – 126 The Logical Editor, Transformer and Input Transformer
Using brackets
The bracket (parenthesis) columns let you enclose two or more condi-
tion lines, dividing the conditional expression into smaller units. This is 
only relevant when you have three or more condition lines and want to 
use the boolean Or operator. This is how it works:
•Without brackets, the conditional expressions are evaluated according 
to their order in the list.
In this case we have the expression Type = Note AND Pitch = C3 OR Channel = 1, 
without brackets. This means that the Logical Editor will find all MIDI notes with the 
pitch C3, as well as all events (regardless of their type) set to MIDI channel 1.
Maybe you wanted to find all notes that either had the pitch C3 or the 
MIDI channel 1 (but no non-note events)? Then you need to add 
some brackets:
Here the expression is Type = Note AND (pitch = C3 OR Channel = 1), which will 
find what you want. The rule behind this is:
•Expressions within brackets are evaluated first.
If there are several layers of brackets, these are evaluated “from the inside out”, start-
ing with the innermost brackets.
You add brackets by clicking in the bracket columns and selecting an 
option. Up to triple brackets can be selected. 
						

							CUBASE SX/SLThe Logical Editor, Transformer and Input Transformer 4 – 127
Editing filter conditions as text
The area directly below the filter condition list shows you the current 
filter conditions as text. It also allows you to enter and edit the filter 
conditions in textual form. For tips on the syntax, please study the in-
cluded presets.
•There is no additional functionality involved when editing filter condi-
tions as text; it is simply another way to make settings. 
When you enter something in the text field you will see the corresponding settings ap-
pear in the filter condition list (provided that you have used the correct syntax). 
						

							CUBASE SX/SL4 – 128 The Logical Editor, Transformer and Input Transformer
Selecting a function
The pop-up menu in the top left corner of the Logical Editor is where 
you select the function – the basic type of editing to be performed. 
When you select an option from the pop-up menu, the field to the right 
displays a clarifying text, making it easier to see what the function does.
In the Logical Editor, processing isn’t performed until you click the Do It 
button. When using the Transformer MIDI effect there is no Do It button 
– the current settings are automatically applied in real time during play-
back or live playing.
Below, the available options are listed. Note that some options are 
available in the Logical Editor only – not in the Transformer effect.
Delete
Deletes all events found by the Logical Editor. In the case of the 
Transformer, this function will remove (or “mute”) all found events from 
the “output stream” – the actual events on the track are not affected.
Transform
Changes one or several aspects of the found events. You set up exactly 
what should be changed in the action list, as described on page 130.
Insert
This will create new events and insert these into the part(s) (Logical 
Editor) or the output stream (Transformer). The new events will be 
based on the events found by the Logical Editor’s filter conditions, but 
with any changes you have set up in the action list applied. 
Another way of expressing this is that the Insert function copies the 
found events, transforms them according to the action list and inserts 
the transformed copies among the existing events. 
						

							CUBASE SX/SLThe Logical Editor, Transformer and Input Transformer 4 – 129
Insert Exclusive
This will transform the found events according to the action list. Then, 
all events that were not found (that didn’t meet the filter conditions) 
are deleted (Logical Editor) or removed from the output stream 
(Transformer).
Copy (not available in the Transformer)
This will copy all found events, transform them according to the action 
list and paste them into a new part on a new MIDI track. The original 
events are not affected.
Extract (not available in the Transformer)
This works like Copy, but will cut the found events instead. Or in other 
words, Extract will transform all found events and move them to a new 
part on a new MIDI track.
Select (not available in the Transformer)
This will simply select all found events, highlighting them for further 
work in the regular MIDI editors. 
						

							CUBASE SX/SL4 – 130 The Logical Editor, Transformer and Input Transformer
Specifying actions
The lower list in the Logical Editor window is the action list. This is 
where you specify any changes that should be made to the found 
events (relevant for all function types except Delete and Select).
The handling of the action list is similar to the filter condition list, but 
without the brackets and booleans. You simply add lines by clicking 
the Add Line button to the right, and fill out the columns as required. 
To remove a superfluous action line, select it and click the Delete Line 
button.
Action Target
This is where you select the property that should be changed in the 
events:
Option Description
Position Adjusting this value will move the events.
Length Lets you resize the events (notes only).
Value 1 This adjusts value 1 in the events. As described on page 120, the 
meaning of value 1 depends on the event type. For notes, value 1 is the 
pitch.
Value 2 This adjusts value 2 in the events. As described on page 120, the 
meaning of value 2 depends on the event type. For notes, value 2 is the 
velocity value.
Channel Allows you to change the MIDI channel setting. See page 122.
Type Allows you to change an event from one type to another, e.g. transform 
aftertouch events to modulation events.
Value 3 This adjusts value 3 in the events, which is used for handling of Note-
off-velocity when searching for properties. See page 123.