OSC (Open Sound Control)
Native OSC has no universal TCP/UDP port assignment. OSC is a transport-independent message format; the application or endpoint defines the listener port, reply port, transport, and framing. Do not approve a firewall line that says only "OSC." Require the actual sender, receiver, application, direction, port, protocol, message dictionary, security boundary, and failure behavior.
Scope: OSC (Open Sound Control) — select the deployed product/version; optional services require separate selection.
protocol · Catalog reviewed 2026-09-27
OSC 1.0; implementation-specific carrier
Infrastructure Requirements
- IP reachability or another packetized/framed transport
- explicit endpoint OSC dictionary
- matching transport/framing mode (UDP, TCP packet-length, TCP SLIP, or framed serial)
- explicit source/destination/port schedule
- network isolation or separate security wrapper where control is sensitive
- and tested reconnect/failure behavior.
Network & Physical Requirements
| Port / allocation | Transport | Connection / signal flow | Feature and requirement | Evidence |
|---|---|---|---|---|
| Configured | UDP | OSC sender → Configured OSC listener | Profile requirement · Core OSC messages and bundles OSC 1.0 message format, UDP carrier Specify host, destination/reply ports, address patterns, data types and timetag handling. | Source checked 2026-09-27 OSC Packets: transport of OSC packets; OSC Messages; OSC Bundles |
| Configured | TCP | OSC client → OSC server | Optional · TCP transport OSC stream carriage OSC 1.0 TCP carriage; application-configured listener OSC 1.0 specifies a 32-bit packet-length prefix for a TCP stream. Confirm that both applications implement this framing and agree on the listener port; other framing modes require a separate product profile. | Source checked 2026-09-27 OSC PacketsOSC 1.0, 26 March 2002 |
Gotchas & IT Notes
- ⚠Set the receive and reply ports in both applications. QLab/Eos examples are product profiles, not mandatory OSC ports.