QLab · OSC Message Generator

Build OSC to control QLab (v4/v5) — copy the string into Companion, a lighting console, TouchOSC or any OSC sender.

Workspace transport

Workspace-level messages. With no Workspace ID set, they broadcast to every workspace listening on the port. "Go to cue" uses /go/<number>.

Control a specific cue

Address /cue/<number>/<command> — targets the cue by its number, wherever it is in the workspace.

Raw / custom message

Full manual control. If a Workspace ID is set it's prepended as /workspace/<id>.

Heads up — browsers can't send OSC directly. OSC travels over UDP, which web pages can't open. This tool builds the exact message; paste it into a real OSC sender (Bitfocus Companion, a lighting console, TouchOSC, Open Stage Control — or our own SchwiftyEx) aimed at the QLab machine's IP on port 53000 (UDP).
Generated message
Address
Argument

Manual & examples

New to OSC? Do the three steps once, then copy any ready-made example straight into your OSC sender. Every message below already reflects your Workspace ID from the top bar.

STEP 1

Turn on OSC in QLab

In QLab: Workspace Settings → Network → OSC Access. Enable OSC control. QLab listens on port 53000 (UDP); set a passcode there if you want one.

STEP 2

Build a message above

Pick a tab (Transport, Cue…), set the fields, and the panel on the right shows the finished message live.

STEP 3

Copy it into an OSC sender

Paste into Companion, a lighting console, TouchOSC or any OSC app, aimed at the QLab machine's IP on port 53000.

Numbers are examples — cue 5. Swap in your own (or use a cue's number/name). With no Workspace ID set, messages go to every workspace on the port. If a workspace has a passcode, send /workspace/<id>/connect <passcode> first.