Steinberg Cubase 8 Manual

							The Logical Editor, Transformer, and Input Transformer
Window overview
861
• In the MIDI editors, edits using the Logical Editor are applied to all selected 
events. If no events are selected, all events in the edited part(s) will be affected.
You can change the selection while the Logical Editor window is open.
2. Select “Logical Editor…” from the MIDI menu.
Window overview
1) Filter conditions list
2) Action list
3) Function pop-up menu
4) Apply button (not available in the Transformer)
Setting up filter conditions
General procedure
The upper list is where you set up the filter conditions, determining which elements 
to find. The list can contain one or several conditions, each on a separate line.
• To add a new condition, click the “+” button below the list.
A 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 condition, select it and click the “-” button below the list. 
						

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
862
NOTE
If you have already defined filter conditions and/or applied a preset, but want to start 
again from scratch, you can initialize the settings by selecting the Init option from 
the Presets pop-up menu.
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:
Left bracket
This is used for “bracketing” several lines together when creating conditions 
with multiple lines and the boolean operators And/Or.
Filter Target
Here you select which property to look for when finding elements. Your choice 
here affects the available options in the other columns as well, see below!
Condition
This determines how the Logical Editor compares the property in the Filter 
Target column to the values in the Parameter columns (see below). The 
available options depend on the Filter Target setting.
Parameter 1
Here you set which value the element properties are compared to (depending 
on the Filter Target).
For example, if the Filter Target is “Position” and Condition is “Equal”, the 
Logical Editor will look for all elements starting at the position you specify in 
the Parameter 1 column.
Parameter 2
This column is used if you have selected one of the “Range” options in the 
Condition column. This allows you to find all elements with values inside (or 
outside) the range between Parameter 1 and Parameter 2.
Furthermore, if you want to find certain VST 3 events (Filter Target set to 
“Type is” and Parameter 1 set to “VST3 Event”), you can use the Parameter 
2 column to specify the VST 3 parameter that you are searching for, e.
 g. 
Tuning.
Bar Range/Time Base (Logical Editor only)
This column is only used if the Filter Target is set to “Position”. If one of the 
“Bar Range” options is selected in the Condition column, you use the Bar 
Range/Time Base column to specify “zones” within each bar (for example, 
allowing you to find all elements on or around the first beat of every bar). If any 
of the other Condition options is selected, you can use the Bar Range/Time 
Base column to specify the time base (PPQ, Seconds, etc.).
Right bracket
This is used for “bracketing” several lines together. 
						

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
863
bool
This allows you to insert the boolean operators And/Or, when creating 
conditions with multiple lines.
You can also set up filter conditions by dragging MIDI events directly into the upper 
list.
If the list contains no entries, a MIDI event dragged into this section will form 
conditions including the state and type of the event. If it contains entries, the 
dragged event will initialize the matching parameters. For example, if a length 
condition is used, the length will be set according to the length of the event.
RELATED LINKS
Combining multiple condition lines on page 892
Searching for elements at certain positions (Logical Editor only) on page 864
Combining multiple condition lines on page 892
Conditions
Depending on the Filter Target setting, the following options can be selected in the 
Condition column:
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. 
						

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
864
Inside Bar Range (Logical Editor only)
…is within the “zone” set up in the Bar Range/Time Base column (Position 
only), in each bar within the current selection.
Outside Bar Range (Logical Editor only)
…is outside the “zone” set up in the Bar Range/Time Base column (Position 
only), in each bar within the current selection.
Before Cursor (Logical Editor only)
…is before the song cursor position (Position only).
Beyond Cursor (Logical Editor only)
…is after the song cursor position (Position only).
Inside Track Loop (Logical Editor only)
…is inside the set track loop (Position only).
Inside Cycle (Logical Editor only)
…is inside the set cycle (Position only).
Exactly matching Cycle (Logical Editor only)
…exactly matches the set cycle (Position only).
Note is equal to
…is the note specified in the Parameter 1 column, regardless of octave (Pitch 
only). For example, lets you find all C notes, in all octaves.
NOTE
The Conditions for the “Property” filter target are different.
Below, the different Filter Targets (and their corresponding Condition and 
Parameter options) are described in more detail.
RELATED LINKS
Searching for properties on page 868
Searching for elements at certain positions (Logical Editor 
only)
Selecting “Position” in the Filter Target column lets you find elements starting at 
certain positions, either relative to the start of the song or within each bar.
• If you select any condition other than the Range or Bar Range options, you set 
up a specific position (in PPQ, seconds, samples, or frames) in the Parameter 
1 column. Use the Bar Range/Time Base column to specify the time base.
Here, the Logical Editor will find all elements at 1.1.1.0 in the project. 
						

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
865
• If you select Inside Range or Outside Range in the Condition column, you set 
the start position of the range in the Parameter 1 column and the end position 
in the Parameter 2 column. You can also change the time base using the Bar 
Range/Time Base column.
The Logical Editor will then find all elements inside or outside this position 
range.
• If you select one of the Bar Range options in the Condition column, the Bar 
Range/Time Base column will show a graphic bar display. You specify the 
range within the bar by clicking and dragging in the bar display (the specified 
Bar Range is indicated in blue).
The Logical Editor will then find all elements starting inside or outside this Bar 
Range, in all bars (within the current selection).
Here, the Logical Editor will find elements starting around the second beat in each 
bar.
Searching for notes of certain lengths (Logical Editor only)
Only note events have lengths (actually, a note is made up of separate note-on and 
note-off events but in Cubase it is considered as a single event with a length). 
Therefore, the “Length” Filter Target is only valid if you are specifically searching for 
notes – there has to be another condition line with the Filter Target “Type”, 
Condition “Equal” and Parameter 1 set to “Note”.
RELATED LINKS
Combining multiple condition lines on page 892
Searching for Value 1 or Value 2
A MIDI event is composed of several values. What is displayed for Value 1 and 2 
depends on the type of event:
Event type Value 1 Value 2
Notes The Note Number/Pitch. The velocity of the note.
Poly Pressure 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. 
						

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
866
NOTE
System Exclusive events are not included in the table above, because they do not 
use value 1 and 2.
Because value 1 and 2 have different meanings for different events, searching for 
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).
IMPORTANTIMPORTANTIMPORTANTIMPORTANT
This is particularly useful when searching for note pitch or velocity values, as 
described below.
The general procedures when searching for value 1 or 2 are:

						

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
867
• 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.
RELATED LINKS
Combining multiple condition lines on page 892
Searching for controllers
There is similar extended functionality when searching for controllers: If you have 
added an additional “Type = Controller” condition line, the Logical Editor 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.
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, for 
example in the following scenarios:
• 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 have selected 
one of the Range Conditions, a higher channel in the Parameter 2 column, creating 
a value range).
Searching for element types
Selecting Type as the Filter Target allows you to find elements of a certain 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 
types (Note, Poly Pressure, Controller, etc.).
The Logical Editor will find all elements matching or not matching the selected type 
(depending on the Condition). 
						

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
868
IMPORTANTIMPORTANTIMPORTANTIMPORTANT
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.
Searching for properties
On the Filter Target pop-up menu, you will find an option called Property. This 
allows you to search for properties that are not part of the MIDI standard but rather 
Cubase-specific 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”, “selected”, “empty”, “inside 
NoteExp”, and “valid VST3”. Some examples:
Here, the Logical Editor will find all muted events.
Here, the Logical Editor will find all events that are selected and muted.
Cubase Pro only: Here, the Logical Editor will find all Note Expression data.
Cubase Pro only: Here, the Logical Editor will find all MIDI controller events that form part 
of Note Expression data.
Cubase Pro only: Here, the Logical Editor will find all VST 3 events that cannot be played 
back, because there is no Note Expression compatible VST instrument on the related track.
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-dependent 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 combined with Parameter 1 
and Parameter 2.
Below, you will find a few examples on how the Last Event filter target can be used. 
						

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
869
Here, the action will only be performed when the 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:
Cubase Pro only: In this example, the action will be performed for Note Expression 
VST 3 Tuning events that are attached to a C1 note when C1 is pressed:
Searching for Chords (Logical Editor only)
NOTE
A note belongs to a chord, if at least two other notes play at the same time.
The Context Variable option on the Filter Target pop-up menu allows you to search 
for chords in a MIDI part or on the chord track.
When Context Variable is selected, the Condition column shows the following 
options: Equal, Unequal, Bigger, Bigger or Equal, Less, Less or Equal, Inside 
Range, Outside Range.
Parameter 1 allows you to specify which context variable is searched:
Filter 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
Filter Target Condition Parameter 1 Parameter 2
Ty p e  i s E q u a l N o t e
Last Event Equal Note is playing 36/C1
Filter Target Condition Parameter 1 Parameter 2
Last Event Equal Value 1 36/C1
Filter Target Condition Parameter 1 Parameter 2
Type is Equal VST3 Event Tuning
Last Event Equal MIDI Status 144/Note On
Last Event Equal Value 1 36/C1
Parameter 1 Searches for…
Highest/Lowest/Average 
Pitch…notes with the highest, lowest or average pitch in the 
selected MIDI part. 
						

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
870
For the following values of Parameter 1 you have to specify a Parameter 2:
The Musical Context presets give you an idea of the possibilities of this filter target.
RELATED LINKS
Conditions on page 863
Working with presets on page 898
Combining multiple condition lines
As described above, you can add condition lines by clicking the “+” button below 
the list. The result of combining condition lines depends on the boolean And/Or 
operators and the brackets.
Highest/Lowest/Average 
Ve l o c i t y…notes with the highest, lowest or average velocity in the 
selected MIDI part.
Highest/Lowest/Average 
CC Value…controllers with the highest, lowest or average value in 
the selected MIDI part.
Parameter 1 Parameter 2 Searches for…
No. of Notes in Chord (Part) Enter a value for the number 
of notes in the chord.…chords with the specified 
number of notes in the 
selected MIDI part.
No. of Voices (Part) Enter a number for the 
number of voices of the 
chord.…chords with the specified 
number of voices in the 
selected MIDI part.
Position in Chord (Part) Select the position (interval) 
in the chord.…the specified chord interval 
in the selected MIDI part.
Note Number in Chord 
(lowest = 0)Enter a number for the 
voicing number of chord.…the specified voicing 
number in the selected MIDI 
part.
Position in Chord (Chord 
track)Select the position (interval) 
in the chord.… the specified chord 
interval in the selected MIDI 
part. The Chord track is 
taken as reference.
Voice Select a voice in the chord. …the specified voice in the 
selected MIDI part. Parameter 1 Searches for…