Total Chaos home page
Documentation sections
Early Access Last updated 2026-09-11

QLab Integration

Coordinate CueForge with QLab via OSC — early-access workflow and verification guidance.

Early Access

CueForge is designed to send OSC triggers to QLab. In the 0.99.1 beta this workflow is early access: it is designed to send, but it has not yet been validated against a real QLab workspace. Verify it in a dedicated workspace before production use.

Verify before showtime

QLab OSC behaviour varies between versions and workspace configurations. Verify message formats and workspace settings against your specific QLab version before relying on this in a live show.

Coexistence, not replacement

CueForge is positioned alongside QLab, not as a replacement. Use the right tool for the workflow: CueForge for show-control organisation, QLab for deep media playback where it already serves you well.

Intended design

  • CueForge sends OSC messages to QLab — for example from an OSC Cue aimed at the QLab machine (UDP, default port 53000), or from the cue editor’s Triggers section
  • Configurable host, port, address pattern, and arguments
  • Typical intent: fire QLab cues or advance cue lists in step with the CueForge show

These are designed capabilities of the OSC send path, not validated QLab-specific features. Confirm the exact address patterns your QLab build responds to.

Direction

CueForge sends OSC to QLab only. Bidirectional sync is planned.

Requirements

  • QLab 4 or 5 running on macOS
  • Network connection between CueForge and QLab machines (or both on one machine)
  • QLab OSC input enabled (default port 53000)

Verification checklist

  1. In QLab, open workspace settings, enable OSC input, and note the port.
  2. Create a dedicated test workspace with a non-production cue.
  3. In CueForge, create a dedicated OSC Cue aimed at QLab — set Host (127.0.0.1 if both run on one Mac), Port, and Address.
  4. Use the cue’s Test Send button to fire the message and verify QLab responds.
  5. Only then connect to the production workspace.
Exact menu paths

Exact QLab menu paths should be verified against the target software version; they vary between releases.

Show safety notes

  • Test in a dedicated QLab workspace before linking to a production show.
  • Verify QLab cue numbers match the CueForge cues that target them.
  • Keep a backup of the QLab workspace before every show.
  • Label every CueForge cue with its QLab target cue number.

Current limitations

  • Send-only; bidirectional sync is planned.
  • Not validated against a real QLab workspace in this beta.
  • No automatic cue list import/export between CueForge and QLab; numbering alignment is manual.