7

440 Chapter 16 The Transform Window
Imagine you want to add a mod wheel controller event (#1) 10 ticks before each note,
with a value that matches the note’s velocity. To do this, you set Status = Note in
Conditions. In Operations, set the Position to Add and enter a value of 10 in the field
below it. Set Status as Fix Control and Pitch (-1-) as Fix 1. The last of these operations
means “the first data byte (-1-) receives the value of 1” (the first data byte defines the
controller number for controller events, and mod wheel events happen to be #1).
If we analyze these settings, we see that all note events will be selected for operation. A
copy of each will be made, then moved 10 ticks earlier than the original, and converted
to CC#1 (Mod Wheel)—with a value that corresponds to the velocity of the original
note. This is because the second data byte (Vel) is left unaltered.
Event Parameters
Individual MIDI event parameters have their own columns in the Conditions and
Operations panels:
Position
Time position of the event, referenced to the start of the MIDI Region (not of the song).
Status
Type of event.
Channel
Recorded MIDI channel of the event.
-1-/Pitch
First data byte (note or controller number).
-2-/Vel
Second data byte (velocity or controller value).
Length
Length of the note.
Subposition
Time position of the event, within a bar.
Conditions
The middle section of the window (Conditions) defines the conditions that determine
which events are selected for edit operations. Each column represents a different MIDI
event parameter.
The condition is considered to be fulfilled when an event matches the defined effective
range of all event parameters. These ranges are determined in the pull-down menus
found under each of the event parameter columns (except the Status column). The
possible value conditions are listed below.