User manual

587
The Logical Editor, Transformer, and Input Transformer
Setting up filter conditions
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 only: Here, the Logical Editor will find all Note Expression data.
Cubase only: Here, the Logical Editor will find all MIDI controller events that form part of Note
Expression data.
Cubase 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.
Here, the action will only be performed when the sustain pedal is down:
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