ShowTiming
Optional: OBS Browser Source countdown that stays with régie
Only if you need a stream overlay — one remaining time with the operator, without pasting a second timer into the scene.
If you use OBS and your overlay drifts from the operator clock, this optional guide shows how ShowTiming Broadcast feeds OBS Browser Source from the same server clock as Control.
The problem
Local OBS countdown plugins and manual text sources only know what you typed. When régie pauses or nudges thirty seconds, the overlay can lag — or never move.
The pattern
Control runs the show. Broadcast is a fullscreen, read-only countdown URL. Drop that URL into OBS as a Browser Source. Stage can use a separate tokenized link for floor monitors.
- Create an event and build the rundown in ShowTiming.
- Open Control and generate a Broadcast link for the event.
- In OBS, add a Browser Source and paste the Broadcast URL.
- Size the source to your overlay; leave the page fullscreen chrono.
- Start, pause, or nudge from Control — OBS follows the same remaining time.
Why Browser Source
Browser Source keeps the overlay dumb: no operator chrome, no cue message clutter on Broadcast, just countdown and alert state. That stability matters mid-show.
Stage vs Broadcast
Broadcast is for overlays. Stage is for talent and crew monitors (active segment, next cue, message). Don’t put Control in OBS — guests should not get transport controls.
Checklist before doors
- Confirm Broadcast URL loads fullscreen on a spare machine.
- Test pause and +10s from Control while watching OBS.
- Revoke or rotate tokens after the show if the link was shared widely.
- Treat network to the server clock as show-critical — same as any cloud régie tool.