LIVE SHOW TIMING
TimeFest.
One operator. A shared clock. A clearer running order.
The problem
A show has its published plan, what actually happened and the forecast for what comes next. Those are different records — and mixing them up is how festivals run late.
What I did
Built operator, FOH and performer views with finish rules, live cues and an independent temporary timer for soundchecks.
Decisions that matter
- Keep planned, actual and forecast timings distinct.
- Resynchronise client displays using server timestamps to beat browser drift.
- Make inherited delay and changeover rules explicit.
Deployed · performer display public