User manual

371
The Logical Editor, Transformer and Input Transformer
• If you select one of the Bar Range options in the Condi-
tion column, the Bar Range column will show a graphic
bar display. You specify the range within the bar by click-
ing and dragging in the bar display (the specified Bar
Range is indicated in blue).
The Logical Editor will then find all events starting inside or outside this
Bar Range, in all bars (within the current selection).
Here, the Logical Editor will find events starting around the second beat
in each bar.
Searching for notes of certain lengths
Only note events have lengths (actually, a note is made up
of separate note-on and note-off events but in Cubase it’s
considered as a single event with a length). Therefore, the
“Length” Filter Target is only valid if you’re specifically
searching for notes – there has to be another condition
line with the Filter Target “Type”, Condition “Equal” and
Parameter 1 set to “Note”. See “Combining multiple con-
dition lines” on page 373 for more about using multiple fil-
ter conditions.
Searching for Value 1 or Value 2
A MIDI event is composed of several values. The mean-
ings of value 1 and 2 depend on the type of event:
Ö System Exclusive events are not included in the table
above, since they don’t use value 1 and 2.
Since value 1 and 2 have different meanings for different
events, searching for e.g. 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 addi-
tional filter condition line with the Filter Target “Type”,
specifying which type of events to find (see below).
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 Inside Range or Outside Range in the Con-
dition 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 “Velocity” 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 Para-
meter 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 “Combining multiple condition lines” on page 373 for
more info on working with multiple filter condition lines.
Event type Value 1 Value 2
Notes The Note Number/Pitch. The velocity of the note.
PolyPressure 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.
!
This is particularly useful when searching for note
pitch or velocity values, as described below.