Protocol Reference
Every protocol type CueSync can speak, with its transport and default port.
Why this table has 20 rows and the rest of the site says 15. Both numbers are right; they count different things. This table is the engine-level list, so a protocol that speaks over two transports gets a row for each — grandMA2 has one for Telnet and one for OSC, grandMA3 one for TCP and one for UDP, QLab the same — and it includes the two DMX-over-IP paths that are still beta. The roster quoted on the rest of the site counts what you can connect to: collapse those three transport pairs, set aside Art-Net and sACN until they have been confirmed against a physical node, and 20 rows become 15 integrations. Nothing is present in one list and missing from the other.
How far each is proven. Two of the fifteen integrations have been graded against real equipment: grandMA3, on onPC 2.4.2.2 — console software, not a physical desk — and Unreal Engine 5, inside the engine. The other thirteen are built to the manufacturer's published interface and pinned to byte-exact wire fixtures. Not hardware-verified. disguise has never been run against a d3, vx or gx. Art-Net 4 and E1.31 sACN are beta: they emit real traffic, but nobody has confirmed fixtures move. Do a dry run on your own rig before show use. Every edition includes every protocol — editions gate workflows, never connectivity. Add outputs in Network Outputs; every connection is wrapped in auto-reconnect with a circuit breaker, and every send reports success or failure.
| Protocol | Transport | Default port | Notes |
|---|---|---|---|
| grandMA3 (UDP) | UDP OSC | 8000 | The recommended GMA3 connection. Current consoles don't open an OSC-over-TCP listener, so this is the transport that works on a 2.4.x desk; it also carries Session Sync pushes. On the console: Menu → In & Out → OSC, enable Input and Receive Command. |
| grandMA3 (TCP) | TCP OSC | 8000 | Use only when a desk actually accepts an OSC-TCP session (2.3.x). Session Sync prefers it when one is connected. |
| grandMA2 (Telnet) | Telnet | 30000 | Classic MA2 remote console. |
| grandMA2 (OSC) | UDP OSC | 8000 | ⚠️ Not an MA2 console feature. grandMA2 has no native OSC input — OSC arrived with MA3 — so a stock console ignores everything sent here. Worse, UDP sends always "succeed", so cues report green while the desk does nothing. Only usable against a console running a third-party OSC bridge plugin, whose address space is specific to that plugin. Use grandMA2 (Telnet) instead; this is not a fallback, because there is nothing to fall back to. |
| ETC Eos | TCP OSC | 3032 | Eos family consoles. |
| Avolites Titan | HTTP REST | 4430 | Titan's WebAPI. |
| ChamSys MagicQ | UDP OSC | 6171 | MagicQ's OSC input. |
| Resolume | UDP OSC | 7000 | Arena / Avenue. |
| disguise (d3) | UDP OSC | 3031 | Transport, section/track navigation, cue recall and the master volume/brightness — the whole of disguise's /d3/showcontrol surface. No layer or timeline control: disguise publishes no OSC address for it. Built to disguise's published interface and pinned to byte-exact wire fixtures; it has never been run against a d3, vx or gx. |
| TouchDesigner | UDP OSC | 9000 | Any TD network. |
| VIOSO | TCP | 9091 | VIOSO media servers. |
| Pixera | TCP (JSON-RPC 2.0) | 1234 | Pixera media servers — timeline transport, cue recall and timeline seek. Pixera has no default API port: open Pixera → Settings → API, set an API Access slot to protocol TCP, and enter the port you typed there. 1234 is a starting guess, not a standard. |
| Unreal Engine 5 | UDP OSC | 8001 | Remote Control plugin; see the CueSync for Unreal plugin for the deeper link. |
| Pangolin Beyond | TCP (PangoScript) | 16063 | Beyond laser software. 16062 is Beyond's UDP port — a TCP connection there never opens. |
| QLab (TCP) | TCP OSC | 53000 | Reliable QLab link with delivery guarantees. |
| QLab (UDP) | UDP OSC | 53000 | Lower-latency alternative. |
| Custom OSC | UDP OSC | user-set | Your own device schemas; also the target for Fade ramps. |
| MIDI Show Control | MIDI SysEx | — | Via any connected MIDI interface. |
| Art-Net | UDP | 6454 | Experimental preview — the full output path is wired and sends real packets at cue fire, but nobody has confirmed fixtures move on a real node. Connection health is honest: a node that never answers an ArtPoll reads unverified, not connected. Don't build a show on it yet. |
| sACN / E1.31 | UDP | 5568 | Experimental preview — same status as Art-Net. |
Beyond the output list above, CueSync also sends and receives MIDI (notes, CC, clock, MIDI Show Control) through the system MIDI devices configured in Settings → MIDI & Sync, receives OSC input for triggers (default port 9001, Settings → Advanced), and syncs tempo over Ableton Link.
Connection behaviour (every protocol)
- Auto-reconnect with exponential backoff, starting at 1 s and capping at 30 s.
- Circuit breaker — repeated failures open the breaker (visible as an EdgeBar chip) instead of flooding the network; it recovers automatically and can be retried manually.
- Honest sends — every command reports delivery; failures surface as notifications and in Diagnostics, never silently.
- No store-and-forward — there is no queue. A command sent while a device is unreachable is reported as failed, not held; a console coming back online is never hit by a flood of cues from the part of the show you have already played past.
Related
- Network Outputs — adding, testing, and monitoring outputs
- Action Reference — which actions target which protocol
- Diagnostics — the connection event log
- Technical Specifications — the full port/firewall table
Looking for a quick fix?
The Help Center has short task-focused articles and a support team that responds within 24 hours.