Steinberg Cubase 7 User Manual

							591
The Logical Editor, Transformer, and Input TransformerSpecifying actions
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.
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:
OptionDescription
Position (Logical 
Editor only)Adjusting this value will move the events.
Length (Logical 
Editor only)Lets you resize the events (notes only).
Value 1This adjusts value 1 in the events. As described in the section 
“Searching for Value 1 or Value 2” on page 584, what is displayed for 
value 1 depends on the event type. For notes, value 1 is the pitch.
Value 2This adjusts value 2 in the events. As described in the section 
“Searching for Value 1 or Value 2” on page 584, what is displayed for 
value 2 depends on the event type. For notes, value 2 is the velocity 
value.
ChannelAllows you to change the MIDI channel setting, see “Searching for MIDI 
channels” on page 586.
TypeAllows you to change the event type, e. g. transform aftertouch events to 
modulation events, or pitchbend events to VST
 3 Tuning events.
Value 3This adjusts value 3 in the events, which is used for handling of Note-off 
velocity when searching for properties, see 
“Searching for properties” 
on page 587.
NoteExp 
Operation 
(Logical Editor 
only)Cubase 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 VST3 value range 
(0.0 to 1.0) instead of the standard MIDI value range (0-127), for finer 
adjustments. 
						

							592
The Logical Editor, Transformer, and Input TransformerSpecifying actions
Ö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.
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 only: VST3 Value Operation – Invert (Logical Editor only)
Inverts Note Expression data containing the specified VST 3 event parameter.
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. 
						

							593
The Logical Editor, Transformer, and Input TransformerSpecifying actions
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 – see 
“Searching for Value 1 or Value 2” on page 584).
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 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. 
						

							594
The Logical Editor, Transformer, and Input TransformerApplying the defined actions
Cubase 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.
Cubase only: NoteExp Operation – Reverse (Logical Editor only)
Reverses the Note Expression data.
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.
Logical Editor operations can be undone just like any other editing.
Working with presets
The Presets pop-up menu at the top of the window allows you to load, save, and 
manage Logical Editor presets.
•To load a preset, select it from the Presets pop-up menu. If available, an 
explanatory text appears to the right of the menu. When setting up your own 
presets, you can click in this area and enter a description.
•You can also select Logical Presets directly from the MIDI menu.
This allows you to apply a preset to the selected MIDI part, without having to open 
the Logical Editor.
•It is also possible to select and apply Logical Presets from within the List Editor 
(from the Mask menu).
•It is also possible to set up a key command for a preset. That way you can 
conveniently apply the same operation to several selected events in one go (for 
further information about setting up key commands, see the chapter 
“Key 
commands” on page 711).
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:
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.
!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 current 
settings are automatically applied in realtime during playback or live playing. 
						

							595
The Logical Editor, Transformer, and Input TransformerThe Input Transformer
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.
Ö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.
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 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. 
						

							596
The Logical Editor, Transformer, and Input TransformerThe Input Transformer
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 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).
For detailed descriptions of the filter conditions and action columns, see “General 
procedure” on page 581.
•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.
Ö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. 
						

							597
The Project Logical Editor (Cubase only)
Introduction
On the Edit menu you will find the function “Project Logical Editor…”. This opens a 
Project Logical Editor for the entire project. It works similar to the Logical Editor on the 
MIDI menu, see the chapter 
“The Logical Editor, Transformer, and Input Transformer” 
on page 580. The most important difference is that the Logical Editor for MIDI works 
at the event level, whereas the Project Logical Editor works at the project level and is 
therefore a very powerful tool for “search and replace” functions in your entire project.
ÖThe MIDI events in the MIDI parts will not be affected by the Project Logical Editor 
operations. If you want to change MIDI notes or controller data, you have to use the 
Logical Editor.
With the Project Logical Editor, you can combine filter conditions with actions to 
create complex procedures, e.
 g. for special track type operations on tracks that are 
named identically. You can use its functions to delete all muted MIDI parts or to toggle 
the open state of all folder tracks in your project, etc. 
Included with the Project Logical Editor are a number of presets that give you an 
impression of the great possibilities that this feature offers, see 
“Working with 
presets” on page 608. Many of them can also be used as starting points when you set 
up your own editing operations. 
The principle for the Project Logical Editor is this:
•You set up filter conditions to find certain elements.
This can be elements of a certain type, with certain attributes or values or on 
certain positions, in any combination. You can combine any number of filter 
conditions and make composite conditions using AND/OR operators.
•You select the basic function to be performed.
The options are Transform (changing properties of the found elements), Delete 
(removing the elements) and Select (selecting the found elements).
•You set up a list of actions, which specify exactly what is done.
This is not necessary for all functions. For example, the Delete function does not 
require any additional action specifications – it simply removes all found elements. 
•In the Macro pop-up menu you can choose an additional macro that will be 
executed after the actions you defined.
Use this to extend the possibilities offered by combining the filter conditions and 
actions specified in the Project Logical Editor even further.
By combining filter conditions, functions, the specific actions, and additional macros, 
you can perform very powerful processing.
!The Project Logical Editor allows all kinds of settings that may not always make sense. 
Experiment a bit before applying your edits to important projects. You can undo the 
operations by using the Undo command on the Edit menu. 
						

							598
The Project Logical Editor (Cubase only)Opening the Project Logical Editor
Opening the Project Logical Editor
1.Open the desired project.
All elements in the project will be affected, you do not have to make any selection.
2.Select “Project Logical Editor…” from the Edit menu.
Window overview
To understand the Project Logical Editor, it might be a good idea to start by exploring 
the included presets. These are found on the Presets pop-up menu at the top of the 
window. For information on how to create and handle your own presets, see 
“Working 
with presets” on page 608.
Setting up filter conditions
General procedure
The upper list is where you set up the filter conditions, determining which elements to 
find. The list contains one or several conditions, each on a separate line.
•To add a new condition, click the “+” button below the list.
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 condition, select it and click the Delete button (-) below the list.
Ö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:
Function and Macro pop-up menus List of filter 
conditions
Action List
Apply button
ColumnDescription
Left bracketThis is used for “bracketing” several lines together when creating 
conditions with multiple lines and the boolean operators And/Or, see 
“Combining multiple condition lines” on page 604. 
						

							599
The Project Logical Editor (Cubase only)Setting up filter conditions
Below, the different Filter Targets (and their corresponding Condition and Parameter 
options) are described in more detail.
Searching for Media types
1.Select “Media Type” in the Filter Target pop-up menu.
This allows you to find elements of certain types of media only. 
2.Open the pop-up menu in the Parameter 1 column and select the desired option.
When the Filter Target is set to Media Type, the pop-up menu lists the available 
media types. The following table lists what is found:
Filter TargetHere 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!
ConditionThis determines how the Project Logical Editor compares the 
property in the Filter Target column to the values in the Parameter 
columns. The available options depend on the Filter Target setting.
Parameter 1Here 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 Project Logical Editor will look for all elements starting at the 
position you specify in the Parameter 1 column.
Parameter 2This column is only used if you have selected one of the “Range” 
options in the Condition column. Typically, this allows you to find all 
elements with values inside (or outside) the range between 
Parameter 1 and Parameter 2.
Bar Range/Time 
BaseThis 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 (allowing you to find all elements on or around the first beat of 
every bar, for example). 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.). See 
“Searching for elements at 
certain positions” on page 602 for details.
Right bracketThis is used for “bracketing” several lines together, see “Combining 
multiple condition lines” on page 604.
boolThis allows you to insert the boolean operators And/Or, when 
creating conditions with multiple lines, see 
“Combining multiple 
condition lines” on page 604.
Column Description
Media TypeDescription
AudioIf no container type is specified, this finds audio events, audio parts 
and audio tracks.
MIDIIf no container type is specified, this finds MIDI parts and MIDI tracks.
AutomationIf no container type is specified, this finds automation events and 
automation tracks.
MarkerIf no container type is specified, this finds marker events and marker 
tracks.
TransposeIf no container type is specified, this finds transpose events and 
transpose tracks.
ArrangerIf no container type is specified, this finds arranger events and 
arranger tracks. 
						

							600
The Project Logical Editor (Cubase only)Setting up filter conditions
3.Open the pop-up menu in the Condition column and select the desired condition. 
For media types, the following options are available:
For example, if you have set up the Project Logical Editor like this…
…it will find all marker events and tracks in the project.
Searching for Container types
1.Select Container Type in the Filter Target pop-up menu.
This allows you to find parts, events or tracks. 
2.Open the pop-up menu in the Parameter 1 column and select the desired option.
When the Filter Target is set to Container Type, the pop-up menu lists the 
available container types. The following table lists what will be found:
3.Open the pop-up menu in the Condition column and select the desired condition. 
For container types, the following options are available:
For example, if you have set up the Project Logical Editor like this…
…it will find all Folder tracks in the project.
TempoIf no container type is specified, this finds tempo events and tempo 
tracks.
SignatureIf no container type is specified, this finds signature events and 
signature tracks.
ChordIf no container type is specified, this finds chord events and chord 
tracks.
Scale EventIf no container type is specified, this finds scale events.
ConditionDescription
EqualThis finds the Media Type set up in the Parameter 1 column.
All TypesThis finds all Media Types.
Media Type Description
Container TypeDescription
Folder TrackThis finds all folder tracks, included FX Channel and Group 
Channel folders.
TrackThis finds all track types.
PartThis finds audio, MIDI, and instrument parts. Folder parts will not 
be found.
EventThis finds automation points, markers, as well as audio, arranger, 
transpose, tempo and time signature events.
ConditionDescription
EqualThis finds the Container Type set up in the Parameter 1 column.
All TypesThis finds all Container Types.