Defining conditions and operations, Editing pitch bend events – Apple Logic Pro 9 User Manual

Page 1129

Advertising
background image

• The data byte 2 value sets the value of the data byte.

• The channel controls the action to be taken:

Channel 1: The changed SysEx message is sent.

Channel 2: The changed SysEx message is not sent.

Channel 3: The unchanged SysEx message is sent.

Channels 4 to 16: No meaning (reserved for future use).

The “Filter non-matching” checkbox prevents incoming MIDI events (that don’t control
the SysEx message) from being passed through. Typically, you’ll want this feature turned
on, to prevent interloping controller data from invading the SysEx data stream.

Track Automation Splitter (True

to Cable)

If the condition matches, incoming events are sent to the track automation of the object
connected to the top cable of the transformer, after passing through the Operation field.
With the appropriate Operation field settings, incoming MIDI data is transformed into
Fader event data, allowing the automation of any possible parameter of the connected
mixer object. Exception: Channel volume and channel pan uses Control events.

Defining Conditions and Operations

The conditions and operations are the same as those found in the Transform window.
For more information, see

Editing MIDI Events in the Transform Window

. The only

differences arise from the fact that a transformer object works in real time and therefore
position and note length have no useful meaning.

Editing Pitch Bend Events

A transformer object can process 14-bit pitch bend events, which contain two discrete
data bytes: if byte 1 is changed (by addition or scaling with the -1- operation), the change
also affects the second byte.

Set the Data Byte 2 operation to Thru to ensure that 14-bit pitch bend data is processed
properly.

Using Meta Events to Control Condition and Operation Values

You can control the values of any transformer conditions or operations by using meta
events. Meta events are internal Logic Pro messages—their form is similar to MIDI controller
events, but they have no MIDI meaning, they never leave Logic Pro, and they control
internal Logic Pro parameters.

Like MIDI controller events, meta events have two data values: the first one indicates the
type of meta event (49 to 127, but not all are used), and the second one is the event value
(0 to 127).

1129

Chapter 37

Environment Objects Reference

Advertising