A modern rundown is not just a list of stories. It is a metadata-rich document that coordinates video playback, graphics rendering, audio mixing, remote feeds, and editorial content. Behind every story are multiple assets, each with its own metadata schema and operational requirements. Rundown software must manage all of this in a consistent and machine-readable way.
Let us examine video objects first. A video clip referenced in a rundown may exist in a media asset management (MAM) system, a shared NAS, or a video playout server. The clip has a unique ID, a file path, a duration, a codec, and sometimes auxiliary metadata. A video server must know which clip to cue and when. The rundown system stores references to these clip IDs and includes them in MOS object messages so playout devices can prepare.
Graphics objects are more complex. A typical lower third graphic template contains placeholders for text fields. The rundown must store:
- the template name
- the field values
- the animation preset
- layer assignments
- timing metadata
When the producer updates a guest name or title, the rundown system must regenerate the MOS object with updated field values. This ensures the graphics engine always renders the correct graphic.
Metadata objects also include script data. Scripts often include markup such as emphasis, italics, presenter notes, and inline commands. A modern show rundown software must store scripts as structured XML or JSON, mapping them to the correct story ID.
One of the most technical challenges is maintaining object associations during story reordering. If a story moves from position 3 to position 1, all attached objects must remain linked. MOS accomplishes this through persistent object IDs.
During updates, the rundown system must ensure that MOS objects are sent before story references to them. This ordering ensures that devices never reference objects they do not yet possess.
Another important requirement is media validation. Rundown systems may check:
- clip existence
- duration mismatches
- template availability
- character limits
- encoding formats
This avoids on-air surprises.
A modern rundown system must also support fallback logic. For example, if a video clip fails to load, the system might fall back to a safe graphic. If a graphic template is missing, the system might revert to a generic lower third. These fallback strategies reduce on-air errors.
Cloud-based systems must also support prefetching. When a rundown is updated, the system may pre-load media into edge caches for remote playout or remote production hubs. This reduces startup latency during live segments.
Metadata synchronization extends beyond MOS. Many systems integrate with REST APIs for automation, distributed playout, or cross-platform publishing workflows. A clip referenced in a rundown may automatically trigger social media or OTT workflows in parallel.
The integrity of metadata is crucial. Rundown systems must track version history, detect inconsistencies, and prevent mismatched media from reaching playout.
Falcon Rundown incorporates structured metadata models that keep assets consistent across scripts, graphics, cuecards, and automation layers. This tight integration ensures that editorial updates propagate cleanly throughout the technical broadcast chain.
The management of video, graphics, and metadata objects is one of the most vital yet invisible aspects of modern rundown software. It is the engine behind the scenes that keeps every part of the broadcast aligned.