You can define conditions that determine which events are selected for transform operations. This is done in the Selection Conditions area of the MIDI Transform window. Each column represents a different MIDI event parameter.
The condition is considered to be fulfilled when an event matches the defined effective range, and values, of all event parameters. These ranges and values are determined in the pop-up menus and fields found under each of the event parameter columns.
Selection conditions
Position: Determines the time position of the event, referenced to the start point of the MIDI region (not the start point of the project).
Status: Determines the event type.
Channel: Recorded MIDI channel of the event
Data Byte 1/Pitch: First data byte (controller number) or note pitch
Data Byte 2/Velocity: Second data byte (controller value) or note velocity
Note: The parameters displayed in the Data Byte fields are dependent on the Status pop-up menu setting. Certain Status pop-up menu settings will not show the Data Byte fields at all.
Length: Length of the note or event
Subposition: Time position of the event, within a bar
Open the Status pop-up menu to determine which events will be selected. You have a choice of two settings:
All: All event types fulfill the condition.
“=”: An additional pop-up menu is displayed (below the Status pop-up menu), where you can define the event type. These include note, poly pressure, control change, program change, channel pressure, pitch bend, meta, and fader.
Open the pop-up menus (in each column that is needed) to define the selection criteria for events. One or two value fields appear below the pop-up menu, unless Map is chosen. You can assign one of the following value conditions for each of the parameter columns:
“=”: The event must be equal to the value in the field, for the condition to be fulfilled. For example, only note C#3 events will meet the condition.
Unequal: The event must not be equal to the value in the field, for the condition to be fulfilled. All events that are not C#3 will meet the condition, for example.
Smaller/Equal (<=): The event value must be less than, or equal to, the value in the field (a note velocity less than, or equal to 98, for example) for the condition to be fulfilled.
Larger/Equal (>=): The event value must be larger than, or equal to, the value in the field (a note pitch higher than, or equal to C#3, for example), for the condition to be fulfilled.
Inside: The event must fall within the value range (of event positions or note pitches, for example) of both fields, for the condition to be fulfilled.
Outside: The event must be outside the value range (of event positions or note pitches, for example) of both fields, for the condition to be fulfilled.
Map: Most conditions are numerical relationships, and the condition is met if the incoming MIDI event value satisfies the condition. The last condition, Map, works a little differently. Two numerical parameters are specified, and the incoming value is first converted by the map, to create a mapped value. The mapped value is then compared with the two parameters to see if it falls inside them. Incoming events with a mapped value that falls within the range will fulfill the condition—all other events will not fulfill the condition. For more information, see Use the map.
Use the mouse as a slider, or enter a value directly into the field.