Feature Library

Cue engine and operator console

<0.01 CPU ms
A still of the Cue engine and operator console demo
Still
The live demo starts when it’s in view.Go on the console, Page Down or a click on the audience screen · a cue number and Enter jumps · A arms a cue as next

Runs a live presentation from a cue list: go, back, jump, hold, calm and black, with builds inside a cue, from any clicker, the keyboard or the console.

What it costs a frame

<0.01 ms
GPU
not used
CPU, median
<0.01 ms
CPU, 95th pct
0.01 ms
Draw calls
0
Weight
Light

Measured 7 November 2026 on 13th Gen Intel(R) Core(TM) i9-13900H, Chrome 156, 1920×1080 at 1×. 600 frames × 3 rounds, median kept. What ran: Measured with the show driving itself: Go every 30 frames from the console, through every build and cue (each press reduced, sent over a BroadcastChannel to the audience pane, drawn there and in the console’s preview), a hold and resume on the questions, then Reset and again. The clocks tick once a second while live; between presses nothing else runs but the one-second heartbeat between the two windows. Phones: tiers are being measured next.

On every machine it was measured on
MachineGPU msCPU msCPU p95
unknown GPU · 13th Gen Intel(R) Core(TM) i9-13900Hreference · measuring toolnot timed<0.010.01
apple · Apple A19 Proin a browser tab · 16 November 2026not timed<0.010.02
Intel Arc 140V (Xe2-LPG) · Intel Core Ultra 7 258Vin a browser tab · 15 November 2026not timed<0.010.01

Bars against one 16.7 ms frame. A browser-tab run is timed in a visible tab without the tool’s scripted input, so read it as close, not exact.

What it needs

Renders with
DOM and CSSPlain DOM and CSS: every current browser.
Your browser
Runs hereNo WebGPU needed
Depends on
NothingNo other packages

What it’s for

  1. Live stage shows and talks run from a second screen
  2. A presenter’s clicker and an operator’s console in step
  3. Rehearsal timing against the plan
  4. Landing a flexible show on time
  5. Kiosk and event screens driven from a control window
  6. Any two windows kept in step offline
  7. A break or a question from the room that returns to the same slide
  8. The stage window placed on the projector, with a monitor of it on the laptop

Pitfalls, in brief

  1. Both windows must be the same origin (and the same browser profile) for BroadcastChannel.
  2. Two presses within a few milliseconds in two windows make two different revisions: the windows agree on one (the lower window id wins) and the other press is lost.
  3. The clock is Date.now by default, shared by every window on one machine.
  4. The audience window can only go full screen from a press in that window (browser rule): the first Go there asks for it, and F toggles it.
  5. Keep the show state yourself if a reload of both windows at once must survive: subscribe and write show.state to sessionStorage, and pass it back as state.
11 more in brief
  1. In standby the cover is black at 99.6 % opacity, so the first cue is drawn under it and warm; a GPU scene should still be compiled and drawn once before (warm-up is your renderer’s job).
  2. Locked, a presenter’s clicker can still go, go back and black the screen, but cannot jump, hold, calm, lock or reset, and cannot step past an operator’s hold or calm.
  3. The heartbeat runs once a second only while another window is known; alone, nothing runs.
  4. Import cue-console.base.css before cue-console.css.
  5. An interlude returns to the cue and build it left, and an armed cue comes next only once the current cue’s builds are shown.
  6. Interludes are not part of the plan: the finish estimate and the run of show count only planned cues (an interlude counts while it is on, and the plan carries on after the cue it returns to).
  7. Open the stage window inside the click.
  8. Placing windows on screens needs Chrome or Edge, a secure context (localhost counts) and a yes from the person, asked once per site.
  9. The monitor copies a canvas: captureStream sees only what is drawn into it, not DOM text laid over it, and a canvas holding images from another origin cannot be captured.
  10. A portal runs no code of its own: everything in the audience window is drawn by the console’s page.
  11. A portal lives and dies with the page that draws it: reload the console and the audience window would go blank, so the module closes it with that page.
16 pitfalls in full, the hook-up guide, the module source and its tests come with the part.

Where it comes from

Written for the library. Fully custom code.

WAI-ARIA Authoring Practices Guide (W3C): The listbox pattern for the cue list (one Tab stop, the arrows, Home and End, the selected option followed by focus, aria-current on the live cue), toggle buttons (aria-pressed) for Hold, Calm, Black and the lock, and a polite live region for changes. Written here from scratch.

HTML Living Standard (WHATWG): BroadcastChannel and cross-document messaging (postMessage), the two paths between the windows.

Window Management (W3C): getScreenDetails() and the window-management permission: which screens there are, and placing the stage window on the other one.

Media Capture from DOM Elements (W3C): HTMLCanvasElement.captureStream(): the console’s live monitor of the stage’s canvas.

cue listshow controlpresentationoperator consolepresenterclickerrehearsalrun of showtimingreducerevent sourcingdeterministic replayBroadcastChannelpostMessagetwo windowsofflinestory flowinterludearmed nextsecond screenWindow Management APIgetScreenDetailscaptureStreamprogram monitor

Near it in the frame