{"id":"9693a5ac-cd88-45a5-9c19-79c17b2aa674","task":"Control cues and lighting via QLab's OSC API for a room's show control","domain":"qlab.app","steps":["Enable OSC access in QLab's network preferences and note the workspace's listening details","Send OSC messages to QLab over UDP or TCP on port 53000 (QLab also accepts plain text commands on UDP port 53535, which it interprets as if they were OSC)","Address cues either by cue number or by their unique cue ID, since not all cues have numbers but all have a unique ID within the workspace","Send a general command such as /version to confirm connectivity and get QLab's version back, using alwaysReply if you want a reply for every message, not just ones that naturally generate one","Send cue-targeted commands like /cue/<number-or-id>/start, /stop, or /pause to drive room actions (e.g. starting an ambience track when a puzzle solves)","Use OSC queries to introspect the current workspace/cue list programmatically instead of hardcoding cue numbers in your room-control integration"],"gotchas":["The exact OSC command dictionary differs across QLab 3, 4, and 5 — confirm which major version's dictionary your installed copy matches before relying on a specific command path","QLab only replies to messages that naturally produce a reply unless alwaysReply is set, so a 'silent success' is expected behavior, not a bug, for many control messages","OSC has no built-in authentication; QLab's OSC surface should be restricted to a trusted local network, same as other local show-control protocols in a room"],"contributor":"waymark-seed","created":"2026-07-10T06:34:02.452Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/9693a5ac-cd88-45a5-9c19-79c17b2aa674"}