OSC lets a controller send structured control messages to another application over a network. In a TuneIT playback rig, the objective is to trigger a verified audio action while keeping the destination, message and operator feedback unambiguous. OSC carries control data; it does not carry the audio file to the loudspeakers.
Draft — technical verification required. TuneIT’s public documentation confirms OSC support but does not provide a complete command dictionary. Exact command addresses, argument types, transport and feedback have not been verified against the current release. This draft deliberately contains no executable TuneIT command examples. Complete the verification table below before approving this guide for publication.
Record the receiving configuration
Start with the TuneIT computer. Record the installed product version and build, the project used for testing and the network interface connected to the controller. The public TuneIT documentation describes an OSC / Remote settings area. Confirm its current label and the OSC enable/listen controls in the release being documented before giving a click-by-click instruction.
Read the actual OSC listening port from that build’s settings or release-matched specification. The existing website mentions a default, but this guide does not treat an older web value as proof of the active configuration. OSC control and a mobile Remote or Viewer connection may use different services; do not copy a mobile connection port into an OSC sender without verifying it.
Set the destination IP address and network path
When a controller runs on a different device, its destination must identify the TuneIT computer on the reachable show network. Read the address from the intended interface rather than choosing an address belonging to an unrelated Wi-Fi, VPN or other adapter. A loopback address refers to the sending device itself, so it cannot identify a separate playback computer.
Have the network administrator confirm the route between the two devices and the permissions for the required service. A guest network or wireless client-isolation setting can prevent devices from reaching one another even when both have internet access. Use the transport specified by TuneIT; a matching port number alone does not establish that two protocols will communicate.
- Record the controller’s destination address and the verified listening port together.
- Check whether the playback computer’s address changes after reconnecting; use the venue’s agreed address-management method.
- Allow the required application/service through the local firewall according to the documented transport. Do not disable the firewall as a general fix.
- Keep the test on the intended local production network. This guide does not require public port forwarding.
Command examples: release verification register
| Required example | Evidence needed before publication | Acceptance test |
|---|---|---|
| Trigger one identified playback pad | Exact OSC address; pad identification/indexing; argument types and values; transport. | One test message starts only the intended audio cue. |
| Stop the tested audio action | Exact supported stop address and scope: one cue, playlist or all playback. | Only the intended playback scope stops. |
| Control a playlist, if supported by the release | Exact supported action, target identification and arguments. | The named action affects the intended playlist. |
| Read feedback, if supported | Whether feedback exists, how it is enabled, return destination, message format and timing. | Observe and record an actual response; distinguish receipt from playback state. |
For each accepted example, add a copyable message from the authoritative TuneIT specification and record the tested build beside it. Do not substitute QLab addresses, guessed paths or commands inferred from a button label. A controller reporting “sent” proves only that it attempted to transmit; it does not prove that TuneIT received or acted on the message.
Test triggering in a controlled order
First confirm that the intended audio cue works from TuneIT’s own interface. Then configure a single external control using one verified message. Send it once and observe the target cue and audio output. Repeat with a stop action only after confirming its scope. Expand the controller layout after this small end-to-end test succeeds.
Document the expected result, actual result and any controller feedback separately. Recheck after restarting the applications or reconnecting the network. A useful handover includes the receiving build, destination, verified messages and the operator’s recovery action if communication fails.
Controller integrations
TuneIT’s public documentation refers to Bitfocus Companion for OSC workflows and Stream Deck for tactile control. That establishes the intended use case, not a guarantee that every plugin version has the same actions. Check the installed module or plugin against the TuneIT release. A generic OSC sender can be used only when its transport and message encoding match the verified specification.
Troubleshooting by symptom
- Nothing happens: test the cue locally, then check OSC enablement, receiver address, listening port, transport and firewall permissions.
- The wrong cue fires: compare the target identifier and indexing with the specification. Do not correct an uncertain index by trial during a show.
- Messages appear to arrive but do not act: inspect the OSC address, argument types and values, not just the controller’s button name.
- It works until reconnecting: confirm that the receiver address and active interface have not changed.
- No feedback appears: establish whether that action supports feedback at all, and verify the documented return configuration before relying on an indicator.
Before this draft can be published
Obtain the current OSC specification or a developer-approved command list, verify each example against the released Windows and macOS builds being supported, and replace the verification register with tested commands and results. Remove this draft notice only after technical review. Use Support for product-specific questions and Downloads for the official release source.
Review TuneIT playback and control features or return to the documentation overview.