Configure a transformer object

Double-clicking a transformer icon opens the Transformer window, where you can set the conditions and operations.

• Mode pop-up menu: Defines how a transformer handles MIDI events. You can choose between the following operation modes:

  • Apply operation and let non-matching events pass thru: MIDI events that match the condition are processed. MIDI events that don’t conform to the condition are passed through.

  • Apply operation and filter non-matching events: MIDI events that conform to the condition are processed. MIDI events that don’t conform to the condition are not passed through.

  • Filter matching events: All MIDI events that match the condition are filtered out. MIDI events that don’t conform to the condition are passed through.

  • Copy matching events and apply operation: All MIDI events that conform to the condition are copied, and the copy is processed. The original and transformed copy (plus any MIDI events that don’t conform to the condition) are passed through. The unchanged original is parsed (processed) before the transformed copy.

  • Copy matching events and apply operation (reverse order): This is the same as above, except the original is parsed after the processed copy. You might want to use this when converting note events to pan controllers, for example. This causes the pan message to be sent before the note. (Many synths don’t alter the pan position of notes that are currently playing.)

  • Condition splitter (true → top cable): Events that match the conditions are altered by the operations, and sent to a transformer’s top output. Events that don’t match the conditions are sent, unaltered, to a transformer’s second output. Don’t use the other outputs as nothing ever appears there.

  • Alternating split: Events entering the transformer are alternated between the top two outlets. No conditions or operations apply.

  • SysEx mapper (data byte 1 → position, data byte 2 → value): This transformer mode is used to create and edit SysEx messages. The Transformer window operations are replaced by value fields that allow you to enter the structure of the SysEX message including its length, whether or not a checksum is required, and the values of bytes you don’t want to change in real time.

    

    In the Conditions area, you select the type of MIDI event that will affect the data bytes in the SysEx message. (Typically, you’ll use MIDI controller events.) Incoming MIDI events will then change the SysEx message data bytes, according to the following rules:

    • The data byte 1 value sets the position of the data byte.

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

    • 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 channel strip. Exception: Channel volume and channel pan use Control events.

• Define conditions and operations: The conditions and operations are the same as those found in the Transform window. For more information, see MIDI Transform window overview. 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.

• Edit 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.