CueProX
⌘K

Docscore-concepts

Real-time sync

What happens behind the scenes when the director clicks a cue.

Real-time sync

The promise

When the director advances a cue, the team's output screens update instantly. No refresh, no manual broadcast, no "can everyone reload?" It just happens.

This is the foundation the whole product is built on. Everything else — the cue structure, the team outputs, the Q&A pipeline, the alerts — is only useful because the updates arrive fast enough to be actionable in a live environment.

How it works

Every device connected to CueProX — the director's laptop, the sound engineer's monitor, the host's tablet — maintains an open connection to the server. When the director takes an action, the change is sent out immediately to every device that needs to see it. There's no polling, no waiting for a scheduled refresh.

You don't need to configure anything for this to work. It's on by default, for every room, for every connected device.

What syncs in real time

  • The current cue and the one coming next
  • Cue-level team notes
  • Director alerts (flashed across all outputs)
  • Team messages
  • Q&A questions, approval status, and answers
  • Stage roster, including who's soloed
  • Output content and presenter view

When any of these change, connected devices see the update within a second or less under normal network conditions.

Tip

Screen fell behind? If a device loses its connection briefly — flaky venue Wi-Fi, a tablet that went to sleep — it may show a stale state. Refreshing the page reconnects and immediately pulls the latest. Nothing is lost; the device just catches up. The system is designed to handle brief disconnections without affecting the show.

Practical implications

Devices don't need to be on the same network. Output screens connect over the internet like any other web page. A guest speaker's personal tablet connects the same way as the hardwired monitor at the production desk. As long as there's internet access, the output is live.

Multiple devices can show the same output. A sound engineer might have the team output open on both a laptop at the desk and a phone in their pocket. Both show the same content, both update at the same time. There's no limit on how many devices can display a given output simultaneously.

The director view and outputs are separate pages. This means the director can have multiple windows open — the main director view in one screen, a preview of a team output in another — without any interference.

Was this helpful?