In modern broadcasting, real time communication between editorial systems and technical devices is not optional. It is required. A rundown may look like a simple list of stories, but underneath the surface, it is the orchestration engine for the entire show. Video servers, graphic engines, teleprompters, automation layers, media asset systems, and playout controllers must receive accurate, timely information the moment a producer makes a change in the rundown.
The technology that makes this possible is MOS: the Media Object Server protocol.
MOS is one of the most successful broadcast technologies ever created. It has remained relevant for more than 25 years, even as newsrooms move from on premises NRCS systems to cloud based editorial tools. Understanding MOS is key to understanding how rundown software, broadcast rundown software, and rundown automation systems work at a deep technical level.
The MOS Philosophy
MOS was designed with three principles:
- Newsrooms need a common language for communicating story structure.
- Devices and servers need a predictable, deterministic protocol.
- Updates must sync instantly across dozens of systems in real time.
Unlike modern REST or WebSocket APIs, MOS is intentionally simple and predictable. It uses XML based messages transmitted over TCP sockets. This makes it extremely stable, ideal for mission critical studio environments.
How MOS Devices and NRCS Systems Connect
A MOS environment typically includes three categories:
- MOS compliant devices
- The NRCS or rundown system
- The MOS Gateway
Legacy NRCS systems such as iNews, ENPS, and Dalet had built in MOS layers. Modern cloud based systems like Falcon Rundown use a gateway that sits inside the broadcast facility. This gateway handles:
- authentication
- device registration
- MOS ID management
- heartbeat monitoring
- message forwarding
- object storage
- queue reliability
When a story changes in the rundown system, the gateway sends out MOS messages to all connected MOS devices.
The Core MOS Message Types
Understanding MOS means understanding the message types that actually flow between devices. The most important categories include:
- MOS rundown messages
- MOS story messages
- MOS item updates
- MOS object creation
- MOS playlist linking
- MOS time updates
- MOS deletion messages
- MOS progress and status reports
For example, a MOS story message may contain:
- story ID
- slug
- duration
- sequence number
- attached MOS objects
- script XML
- element metadata
This allows a graphics engine, video server, or studio automation system to understand exactly what belongs to a specific story.
Media Object Handling
One of the most powerful parts of MOS is its object handling. A MOS object represents a media item such as:
- a lower third
- a fullscreen graphic
- a still image
- a video clip
- a super
- a title card
- a camera preset
- a remote feed ID
When the rundown system associates an object with a story, the MOS protocol guarantees that the device receives the object and stores it locally. This may include:
- file path
- template name
- metadata
- timing
- layer mapping
- playout ID
During a live broadcast, when a story becomes active, the connected devices already have the elements prepared via MOS.
Rundown Updates and Reordering
Live broadcasts change constantly. Producers reorder segments, update sequencing, or shorten durations. MOS is built to handle this through messages like:
- roStorySend
- roStoryReplace
- roStoryDelete
- roStoryMove
- roRunningOrder
These allow devices to adjust instantly.
For example:
- If a producer drags a story from position 8 to position 3, the MOS gateway sends reorder messages.
- Graphics engines will reprioritize their templates.
- Video servers will move clip cues in the playlist.
- Automation systems will rebuild their execution timelines.
This is how MOS keeps everything in sync.
Story Locking and Timing Control
MOS also includes mechanisms for story locking, ensuring technical devices do not lose track of what is currently on air. When a story is marked active, devices shift into live execution mode.
Timing control is another key element. MOS enabled rundown systems send time updates to playout devices, allowing them to:
- anticipate transitions
- pre-roll video content
- prepare live graphics
- sync ticker data
- align remote cues
In modern broadcast rundown software, timing updates are tied to cloud timing engines. These engines calculate:
- target duration
- actual duration
- remaining time
- over/under flow
- live pacing
Through the gateway, this timing is fed back into the MOS environment.
New Challenges for MOS in Cloud Environments
As newsrooms move to cloud based editorial systems, MOS faces new technical demands. A MOS device inside a local studio cannot directly receive inbound connections from a cloud NRCS. Firewalls, NAT rules, and security policies make this impossible.
This is why modern rundown systems like Falcon Rundown use outbound-only MOS gateways. They establish:
- secure WebSocket tunnels
- persistent message buffers
- timeout recovery logic
- redundant endpoint fallback
These allow cloud based editorial changes to reach on-prem hardware instantly, without exposing the facility network.
Why MOS Still Matters
Even though newer broadcast APIs exist, MOS remains:
- stable
- predictable
- widely supported
- broadcast focused
- extremely reliable
Nearly every graphics engine, video server, and NRCS system supports MOS. Removing MOS would break thousands of studios.
Modern rundown software, including Falcon Rundown, continues to integrate MOS because no other protocol matches its blend of simplicity, determinism, and reliability.
Conclusion
MOS is the backbone of newsroom integration. It ensures every device in the broadcast pipeline remains in perfect sync with the rundown. In an era of cloud editorial tools, remote production, virtual control rooms, and hybrid workflows, MOS continues to play a vital role.
Modern MOS gateways make it possible for cloud-native rundown software like Falcon Rundown to communicate seamlessly with legacy broadcast equipment.
MOS is not going anywhere.
It still powers the global newsroom ecosystem.