RTW devices gain powerful new workflow options. Whether you need to automate loudness resets, trigger presets from a console, or integrate with a DAW, or other third-party tools, actions open up a world of flexible control.
Multi-Device Control
With OSC integration, RTW devices TMxCore, TouchControl 5 und TouchMonitor 5 can send commands simultaneously to multiple devices on the network. This makes it possible to start, stop, reset loudness measurements synchronously with a playback, or load presets across all connected units with a single action, ensuring consistent operation throughout the setup.
A TouchControl 5 positioned at the operator’s desk can be used to navigate and control a TouchMonitor 5 remotely, providing centralized access without the need to operate each device directly.
Transmit: Outgoing Commands
Within a press on a button the RTW devices can send OSC messages via TCP or UDP and HTTP requests.
Action Button
A dedicated Action button can be customized with its own size, color, and label.
OSC Everywhere
Any button in a preset can send OSC commands in addition to its primary function. For example, pressing the TALK button can simultaneously trigger one or more OSC commands, such as activating the DIM function in the monitoring application or switching on speakers when the corresponding output is selected.
Multi-Command Capability
A single button can send not just one, but multiple commands at once, OSC and HTTP commands can be mixed in one action.
Multi-state
For a toggle button (e. g. TALK), the button’s state is transmitted. When the button is ON, TRUE is sent; when it is OFF, FALSE is sent.
OSC Settings
| Active: | Indicates whether the command is active |
| Name: | The name of the action |
| Type: | There are three types of commands: |
| • OSC TCP | |
| • OSC UDP | |
| • HTTP Request | |
| Host | The IP address of the target device |
| Port | The port of the target device, typical 8000 |
| Message | If Type is OSC, this is the Address. If Type is HTTP, this is the URI |
Receive: Incoming Commands
RTW devices can also react to OSC commands. This means external systems can control core functions such as:
- Recalling presets
- Resetting loudness
- Triggering monitoring actions
This makes it super easy to integrate with broadcast consoles, Stream Decks, or other controllers.
OSC Receive Implementation
The OSC receive implementation uses TCP on Port 8000.
Below is an overview of the available OSC actions, addresses, types, and arguments.
| Action | Address | Argument Type | Argument Description |
| Presets | |||
| Recall preset number n | preset/recall | INTEGER | n (zero-based: Default preset = 0) |
| Recall preset by name | preset/recall | STRING | Preset Name (Case Sensitive) |
| Examples | |||
| Recall preset number 3 | preset/recall | INTEGER | 2 |
| Recall preset with the name "Live Sports" | preset/recall | STRING | "Live Sports" |
| Metering | |||
| Within Metering, you can reset/start/stop, both per individual application or across all metering applications within the currently loaded preset. appId = Application ID The first application has appId = 0, the second has appId = 1 and so on If you set appId = all, the command applies to all Metering applications |
|||
| Start loudness measurement (per application or all) |
metering/appId/start | - | - |
| Stop loudness measurement (per application or all) |
metering/appId/stop | - | - |
| Reset loudness measurement (per application or all) |
metering/appId/reset | - | - |
| Examples | |||
| Start loudness measurement on the first application | metering/0/start | - | - |
| Stop loudness measurement on the second application | metering/1/stop | - | - |
| Reset loudness across all application | metering/all/reset | - | - |
| Monitoring | |||
| Set Volume | monitoring/volume | FLOAT | Value in dB |
| Recall reference volume | monitoring/reference | - | - |
| DIM Speaker | monitoring/dim | BOOL | TRUE/FALSE |
| Mute Speaker | monitoring/mute | BOOL | TRUE/FALSE |
| Enable Headphone | monitoring/phones | BOOL | TRUE/FALSE |
| Select Input | monitoring/input | INTEGER | Input number (zero-based: Input 1 = 0) |
| Select Ouput | monitoring/output | INTEGER | Output number (zero-based: Output 1 = 0) |
| Examples | |||
| Set levell to 60 dB | monitoring/volume | FLOAT | 60 |
| Mute Speakers | monitoring/mute | BOOL | TRUE |
| Un-mute Speakers | monitoring/mute | BOOL | FALSE |
| Select Input 2 | monitoring/input | INTEGER | 1 |
| Talkback | |||
|
appId = Application ID The first application has appId = 0, the second has appId = 1 and so on If you set appId = all, the command applies to all Talkback applications |
|||
| Set Mic input gain (per application or all) |
talkback/appId/gain | FLOAT | -12 to +12 dB |
| Enable/disable Talkback (per application or all) |
talkback/appId/active | BOOL | TRUE/FALSE |
| Examples | |||
| Enable talkback in first application | talkback/0/active | BOOL | TRUE |
| Device | |||
| Phantom Power On/Off | device/phantom | BOOL | TRUE/FALSE |