Steinberg Cubase 8 Manual

							The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
871
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 combines two condition lines and determines the result in the 
following way:
• If two condition lines are combined with a boolean And, both conditions must 
be fulfilled for an element to be found.
The Logical Editor will only find elements that are notes and start at the beginning of 
the third bar.
• If two condition lines are combined with a boolean Or, one of the conditions 
(or both) must be fulfilled for an element 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).bar.
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 
element to be found, you do not have to think about the boolean column – just add 
the required lines and make the usual filter settings.
Using brackets
The bracket (parenthesis) columns let you enclose two or more condition 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 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:
• Expressions within brackets are evaluated first.
If there are several layers of brackets, these are evaluated “from the inside 
out”, starting with the innermost brackets. 
						

							The Logical Editor, Transformer, and Input Transformer
Selecting a function
872
You add brackets by clicking in the bracket columns and selecting an option. Up to 
triple brackets can be selected.
Selecting a function
The pop-up menu at the bottom of the Logical Editor is where you select the 
function – the basic type of editing to be performed.
Below, the available options are listed. Note that some options are not available in 
the Transformer effect.
Delete
Deletes all elements found by the Logical Editor. In the case of the 
Transformer, this function will remove (or “mute”) all found elements from the 
“output stream” – the actual elements on the track are not affected.
Transform
Changes one or several aspects of the found elements. You set up exactly 
what is changed in the action list.
Insert
This will create new elements and insert these into the part(s) (Logical Editor) 
or the output stream (Transformer). The new elements will be based on the 
elements 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 
elements, transforms them according to the action list and inserts the 
transformed copies among the existing elements.
Insert Exclusive
This will transform the found elements according to the action list. Then, all 
elements that were not found (that did not meet the filter conditions) are 
deleted (Logical Editor) or removed from the output stream (Transformer).
Copy (Logical Editor only)
This will copy all found elements, 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. 
						

							The Logical Editor, Transformer, and Input Transformer
Specifying actions
873
Extract (Logical Editor only)
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 (Logical Editor only)
This will simply select all found events, highlighting them for further work in the 
regular MIDI editors.
RELATED LINKS
Specifying actions on page 873
Specifying actions
The lower list in the Logical Editor window is the action list. This is where you 
specify any changes that are 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 “+” button below the 
list, and fill out the columns as required. To remove a superfluous action line, select 
it and click the “-” button.
Action Target
This is where you select the property that is changed in the events:
Option Description
Position (Logical Editor only) Adjusting this value will move the events.
Length (Logical Editor only) Lets you resize the events (notes only).
Value 1 This adjusts value 1 in the events. What is 
displayed for value 1 depends on the event 
type. For notes, value 1 is the pitch.
Value 2 This adjusts value 2 in the events. What is 
displayed for value 2 depends on the event 
type. For notes, value 2 is the velocity value.
Channel Allows you to change the MIDI channel 
setting.
Type Allows you to change the event type, e. g. 
transform aftertouch events to modulation 
events, or pitchbend events to VST 3 Tuning 
events. 
						

							The Logical Editor, Transformer, and Input Transformer
Specifying actions
874
NOTE
The Position and Length parameters are interpreted via the time base setting in the 
Bar Range/Time Base column, with the exception of the Random setting, which 
uses the time base of the affected events.
RELATED LINKS
Searching for properties on page 891
Searching for Value 1 or Value 2 on page 865
Operation
This setting determines what to do with the Action Target. The options on this 
pop-up menu are different depending on the selected Action Target.
Below, all available operations are listed:
Add
Adds the value specified in the Parameter 1 column to the Action Target.
Subtract
Subtracts the value specified in the Parameter 1 column from the Action 
Target.
Multiply by
Multiplies the Action Target value with the value specified in the Parameter 1 
column.
Divide by
Divides the Action Target value by the value specified in the Parameter 1 
column.
Cubase Pro only: VST3 Value Operation – Invert (Logical Editor only)
Inverts Note Expression data containing the specified VST 3 event parameter.
Value 3 This adjusts value 3 in the events, which is 
used for handling of Note-off velocity when 
searching for properties.
NoteExp Operation (Logical Editor only) Cubase Pro only: Allows you to specify a 
Note Expression operation in the Operation 
column.
VST3 Value Operation (Logical Editor only) Allows you to perform common operations 
within the VST 3 value range (0.0 to 1.0) 
instead of the standard MIDI value range 
(0-127), for finer adjustments. Option Description 
						

							The Logical Editor, Transformer, and Input Transformer
Specifying actions
875
Round by
This “rounds” the Action Target value using the value specified in the 
Parameter 1 column. In other words, the Action Target value is changed to the 
closest value that can be divided by the Parameter 1 value.
For example, if the Action Target value is 17 and Parameter 1 is 5, the result 
of rounding will be 15 (the closest value that can be divided by 5). Another 
word for this type of operation would be “quantizing”, and it is actually 
possible to use it for this, by setting the Action Target to “Position” and 
specifying a quantize value with Parameter 1 (in ticks, with 480 ticks per 
quarter note).
Set Random Values between
This will set the Action Target value to a random value within the range 
specified with Parameter 1 and 2.
Set to fixed value
This sets the Action Target to the value specified in the Parameter 1 column.
Set Relative Random Values between
This will add a random value to the current Action Target value. The added 
random value will be within the range specified with Parameter 1 and 2. Note 
that these can be set to negative values.
For example, if you set Parameter 1 to - 20 and Parameter 2 to + 20, the 
original Action Target value will get a random variation, never exceeding ±
 20.
Add Length (Logical Editor only)
This is only available when Action Target is set to Position. Furthermore, it is 
only valid if the found events are notes (and thus have a length). When Add 
Length is selected, the length of each note event will be added to the Position 
value. This can be used for creating new events (using the Insert function) 
positioned relative to the end positions of the original notes.
Transpose to Scale
This is only available when Action Target is set to Value 1, and when the filter 
conditions are specifically set up to find notes (a “Type = Note” filter condition 
line has been added). When “Transpose to Scale” is selected, you can 
specify a musical scale using the Parameter 1 and 2 columns. Parameter 1 is 
the key (C, C#, D, etc.) while Parameter 2 is the type of scale (major, melodic 
or harmonic minor, etc.).
Each note will be transposed to the closest note in the selected scale.
Use Value 2
This is only available when Action Target is set to Value 1. If this option is 
selected, the Value 2 setting in each event will be copied to the Value 1 
setting.
This is useful, for example, if you are transforming all Modulation controllers to 
Aftertouch events (since controllers use Value 2 for their amount, while 
Aftertouch uses Value 1). 
						

							The Logical Editor, Transformer, and Input Transformer
Specifying actions
876
Use Value 1
This is only available when Action Target is set to Value 2. If this option is 
selected, the Value 1 setting in each event will be copied to the Value 2 
setting.
Mirror
This is only available when Action Target is set to Value 1 or Value 2. When 
this option is selected, the values will be “mirrored” around the value set in the 
Parameter 1 column.
In the case of notes, this will invert the scale, with the key set in the Parameter 
1 column as “center point”.
Linear Change in Loop Range (Logical Editor only)
This will affect events within the loop range (between the left and right 
locators) only. It will create a linear “ramp” of values (replacing the original 
values) starting at the value in the Parameter 1 column and ending at the 
Parameter 2 value.
This can be used for creating linear controller sweeps, velocity ramps, etc.
Relative Change in Loop Range (Logical Editor only)
As with the previous option, this will create a ramp of values, affecting events 
in the loop range only (i.
 e. between the locators). However, here the changes 
are “relative”, meaning that values will be added to the existing values.
In other words, you set up a value ramp starting at Parameter 1 and ending at 
Parameter 2 (note that the Parameter values can be negative). The resulting 
value ramp is then added to the existing values for the events within the loop 
range.
For example, if you apply this to note velocities with Parameter 1 set to 0 and 
Parameter 2 set to -100, you create a velocity fade-out, keeping the original 
velocity relations:
Cubase Pro only: NoteExp Operation – Remove Note Expression (Logical 
Editor only)
This option is only available for notes. It allows you to remove all Note 
Expression data from a note.
Cubase Pro only: NoteExp Operation – Create One-Shot (Logical Editor only)
This option is only available for notes. It allows you to add Note Expression 
data for notes in “One Shot” mode, meaning that you add a parameter as Note 
Expression data. After having added the one-shot parameter, you have to set 
it to the desired value in a second go. 
						

							The Logical Editor, Transformer, and Input Transformer
Applying the defined actions
877
Cubase Pro only: NoteExp Operation – Reverse (Logical Editor only)
Reverses the Note Expression data.
RELATED LINKS
Searching for Value 1 or Value 2 on page 865
Applying the defined actions
Once you have set up filter conditions, selected a function and set the required 
actions (or loaded a preset), you apply the actions defined with the Logical Editor 
by clicking the Apply button.
IMPORTANTIMPORTANTIMPORTANTIMPORTANT
In the Logical Editor, processing is not performed until you click the Apply button. 
When using the Transformer MIDI effect, there is no Apply button 
						

							The Logical Editor, Transformer, and Input Transformer
The Input Transformer
878
Storing your own settings as a preset
If you have made Logical Editor settings that you want to use again, you can save 
them as a preset:
PROCEDURE
1. Click on the Store Preset button on the right of the Preset menu.
A dialog for specifying a name for the new preset is displayed.
2. Enter a name for the preset and click OK.
The preset is stored.
To remove a preset, load it and click on the Remove Preset button.
Organizing and sharing presets
The Logical Editor presets are stored within the application folder in the 
Presets\Logical Edit subfolder. While these files cannot be edited “manually”, you 
can reorganize them (e.
 g. putting them in subfolders) like any files.
This also makes it easy to share presets with other Cubase users, by transferring 
the individual preset files.
NOTE
The list of presets is read each time the Logical Editor is opened.
The Input Transformer
This function allows you to filter out and change MIDI data coming to a MIDI track 
before it is recorded. The Input Transformer is very similar to the Transformer MIDI 
effect, but contains four independent “modules”, for which you can set up different 
filtering and actions. You can activate any or all of these four modules.
Here are some of the things the Input Transformer allows you to do:
• Set up split keyboard combinations for recording left and right hands 
separately.
• 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. 
						

							The Logical Editor, Transformer, and Input Transformer
The Input Transformer
879
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 to open the pop-up menu.
• Select Global to make Input Transformer settings that affect all MIDI inputs 
(and thereby all MIDI tracks).
• Select Local to make Input Transformer settings for this track only.
In both cases, the button lights up and the Input Transformer opens.
Handling the four modules
The Input Transformer is really four separate transformers, or modules.
• You select which module to view and make settings for by clicking the 
corresponding Module tab.
Module 1 selected for viewing and editing.
• The On/Off buttons next to the Module names determine which module(s) are 
active.
Here, Module 1 is inactive and Module 2 is active. 
						

							The Logical Editor, Transformer, and Input Transformer
The Input Transformer
880
The Function pop-up menu
The Function pop-up menu contains two options: 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 transformed 
according to the settings in the action list (the lower list).
Setting up filtering and actions
This is done just like in the Logical Editor. Here is a brief rundown:
• Click the “+” button to add lines to the filter condition list or action list.
To remove a line, click it to select it and click the “-” button below the lists.
• Clicking the columns in the filter condition list opens pop-up menus allowing 
you to specify the conditions to match.
• Clicking the columns in the action list opens pop-up menus allowing you to 
specify how the found events are transformed (when Transform mode is 
selected).
• The Input Transformer has no Apply button – the settings are active as soon 
as you activate the On/Off button of a module.
The settings made in the active modules will affect all MIDI data you record 
on the track.
NOTE
Closing the Input Transformer window does not turn it off – you need to deactivate 
the On/Off buttons of all modules for this! A lit Input Transformer button in the 
Inspector indicates that one or more modules are active.
RELATED LINKS
General procedure on page 883