A virtual QLab driving two real firmwares. Both device panes run the actual compiled
code on one shared clock. The highlighted row is the standby cue — it has
not run yet. Its #timer/ directive sits armed (grey on the buddy), and only
when you press GO does that cue actually run: its timer starts and its device tags fire.
Clicking a row just moves the playhead, same as clicking a cue in QLab.
QLab 5Matinee.qlab5 · 192.168.1.45:53000
CueNameNotes
Press Esc anywhere on this page for Panic
OSC out
QLAB Buddy480×320 · touch
Physical BOOT tap = GO · hold 5 s = PANIC its GO drives QLab, same as the real one
⏻
Physical PWR short press toggles the backlight the firmware keeps drawing behind it
↻
Physical RST hard reset — reboots the chip RAM clears, splash runs
RF Relay320×170 · encoder
Turn the knob in the ring (scroll or drag it — dragging the
screen works too), tap to press, hold for a long press. No touchscreen on this board.
SlotSetup menu (every one of these drives the real encoder UI)
playing on the relay…
Radio & power
CC1101 present
CC1101 absent (NO RF)
Battery only
Cabled, QLab idle
Cabled, QLab live
Battery
78%
Director panel pair devices, teach the relay, drive timers, batteries and every network state
Network — every status-bar state the firmware can draw
QLab open
WiFi, no show
Cabled (LAN)
Pairing mode
WiFi lost (red)
Never configured (grey)
Internet check — only the QLAB state shows it, on the ring and label
Confirmed (gold)
Not confirmed (white)
QLab workspace — each is its own showBuddy — #timer/ directive · start and a duration ARM; the rest act now
Buddy — physical buttons
Buddy — OSC access (VIEW silences GO/PANIC, on-screen and physical)
CTRL
VIEW only
Buddy — devices (TEST fires; PING only flashes the LED)
Buddy — jump to (AppView, qlab_types.h)
Buddy — pairing (hotspot SYNC, exactly as on hardware)