Live event content
Every cue built, tested and handed to the operator
We build the show’s content package: a cue list tied to the running order, files at output spec, and an operator handover.
Where show content usually falls apart
Content arrives as a folder of files with nothing mapping it to the running order. Part of it is the wrong resolution for the screen, and the operator first sees it at rehearsal. Then the running order changes late and nobody can say which file is current.
From running order to operator handover
01
Lock the running order first
We start from the run of show, not the design. Every content moment gets a cue number, duration, source and owner on one list everyone works from.
02
Build to the screen’s output spec
Canvas size, pixel map, frame rate and codec come from the screen and the playback system, not a template. We test files on that playback path before handover, so problems surface before the room is live.
03
Hand over with a fallback
The operator gets named files, a cue sheet and a dry run with us before doors. Anything live, such as a data view or a camera feed, ships with a held frame to cut to.
What arrives before show day
01
A cue list numbered against the running order, with duration, source, operator note and owner per cue.
02
Master and backup renders at the output spec, named to the cue list, plus a held frame for every live element.
03
An operator pack: playback project or playlist, cue sheet, version log, and a rehearsal pass with us on site or on call.
Rooms this has already run in
Show and screen content for BYD, Al Futtaim, Al Futtaim Electric Mobility, Hyundai via Touchpoint and Lean. Also TeamNL Volkswagen via Holy Cow and TABADUL at Gitex, covering keynote content, large format LED, signage and interactive installations.
Send your running order and we will map the cues
Send the run of show, the screen spec and the date, and we will come back with a draft cue list.