TouchOSC

Next generation modular control surface
TouchOSC Manual

Editor · Messages · MIDI


A control can have multiple MIDI messages configured. Messages can be both sent and received on multiple connections.

When a message is enabled to send, it will be sent on the configured connections when any of the control's values enabled as trigger change, and if the change matches the change condition of the trigger.

When a message is enabled to receive, it will be considered to be matched against received MIDI messages if the incoming message is received on one of the enabled connections.

Message matching depends on the type of MIDI message. TouchOSC defines part of a MIDI message as the address part, used for routing to determine the target controls, and another part as the payload.

The type of the message and the address part will be used to determine if the incoming message matches the control's message, and the payload part will then be processed to extract values and properties to update (if so configured).

See the message matching section for details on address/payload for each message type.



Enabled

The enabled state of the message.

If a message is not enabled, it will neither be sent or matched to received messages.

 

Send

The send enable flag of the message.

Only if the send flag is set to on for the message, it will be considered for sending when any of the values enabled as triggers change, and the trigger's change condition is met.

 

Receive

The receive enable flag of the message.

Only if the receive flag is set to on for the message, it will be considered for being matched against any incoming MIDI messages received on any of the connections enabled for the message.

 

Feedback

The feedback enable flag of the message.

The feedback flag controls the processing of the message in situations where both the send and receive flags are enabled and a received MIDI message changes a value that is also enabled in the list of send triggers for the message.

If a received MIDI message, and subsequent change of value, would also cause the same message to be sent again immediately, this could cause an undesirable feedback loop in the interaction with another application, hence this flag controls if the message should be sent again in this case.

The feedback enable flag is set to off by default because of the potential problems this behavior could cause. Please handle with care.

 

Connections

The connections that the message should be sent and received on. The numbers refer to the numbered MIDI connections configured in the MIDI connections configuration.

If the message is enabled to be sent, it will be sent only on the enabled connections.

If the message is enabled to be received, any received MIDI messages will only be considered to be matched to the message if received on one of the enabled connections.

 

Trigger

The trigger conditions for the message to be sent.

If the message send flag is set to on, it will be sent only if any of the value objects enabled here change, and only if the configured change condition is being met.

Any of the control's values can be enabled individually here, with one of the possible change conditions of:

  • ANY - Any change in value will cause the message to be sent
  • RISE - Any change causing the value to increase will cause the message to be sent
  • FALL - Any change causing the value to decrease will cause the message to be sent
 

Type

The type of MIDI message.

TouchOSC supports the following types of MIDI messages:

  • Note Off/On
  • Poly pressure
  • Control change
  • Program change
  • Channel pressure
  • Pitch bend
  • System exclusive

Depending on the type of message selected, the configuration of the message fields will change. For any of the possible parts of any given MIDI message type, the source value used can be any of:

  • CONSTANT

    A constant value.

  • INDEX

    The current index of the control in its parent list of child controls.

  • VALUE

    The current value of any of the control's value objects.

  • PROPERTY

    The current value of any of the control's properties.

All values will be converted to integer types, and all source value types except for CONSTANT can optionally be scaled before sending (and in reverse after reception). Scaling is applied using following calculation:

out = min + in * (max - min)

 

Matching

If the receive flag is set to on for a message, it will be considered as the target of any received MIDI message if its configuration matches the incoming message.

The type of message will determine how an incoming message will be matched, and then possibly routed, to be received and processed according to this message's configuration. Only if an incoming message's type and address part match the configured message will it be received and processed according to this message's description.

If the message configuration uses a control value or property for any of the address parts of the message type, the received message has to also match current values of these at the time of reception.

If the message configuration uses a control value or property for the payload part of the message type, the value or property will be updated using the received payload value.

The following table lists the parts of a MIDI message TouchOSC considers address and payload for each of the supported message types:

Type Address Payload
Note Off/On Channel + Note Velocity
Poly pressure Channel + Note Velocity
Control change Channel + Controller Value
Program change Channel Value
Channel pressure Channel Value
Pitch bend Channel Value

NOTE: Received messages of type System exclusive can only be processed using scripting and only at the document root level.

 

hexler.net uses cookies to deliver website content. By continuing without changing your preferences, you agree to our use of cookies.