- Playout plays the schedule; automation drives playout and the other devices from the playlist.
- Start with the schedule and the outputs, not the feature list.
- Closed captions, audio description and loudness are requirements, not options.
- Redundancy decides how long the channel stays off air when something fails.
- Test with your own material and your own schedule before you sign.
On this page
Short answer
To choose a playout system, start with the channel, not the catalog: how many hours of schedule, how many channels, how many live inputs, what graphics, which outputs and how long the channel can be off air. Then check that the system reads your material's formats, integrates with your traffic and scheduling system, meets accessibility and loudness rules, offers real redundancy and has local support. The best choice is the one that actually runs your schedule, tested with your material, and that your team can operate at three in the morning.
Playout, automation and channel in a box
Playout is the part that plays files and live events and generates the channel signal. Automation is the software that reads the playlist and drives playout and other devices, such as the router, graphics and recorders. In the past these were separate machines. Today the so-called channel in a box is common: a single system, on standard servers, handles playback, graphics, captions and automation.
The criteria that matter
Seven criteria separate a playout that serves your channel from one that only looks good in the demo. Weigh each one with your schedule in mind.
Formats and material
Playout needs to play the codecs and containers that arrive from your edit suites, production companies and advertisers without manual conversion, in HD or 4K, with audio on the right tracks. Check ingest too: how material comes in, whether there is automatic quality control and whether the system integrates with your MAM and archive.
Schedule and traffic
The playlist is born in the scheduling and traffic system. Playout needs to import that schedule, accept last-minute changes and return the as-run log of what went to air, which proves delivery to advertisers. Manual integration by spreadsheet turns into on-air errors. Also ask how the system handles swapping a commercial at the last minute and how it confirms that it aired.
Live
How many live inputs the channel has, how the operator joins and leaves them and how the system handles shows that overrun. Channels with news and sports need easy switching between live and recorded, and tools to recalculate the schedule.
Graphics and branding
Logo bug, clock, promos, credits, sponsor tickers and content rating. Some systems have built-in graphics; others drive an external real-time graphics engine. See how much your team can change without calling the vendor.
Accessibility and audio
On Brazilian free-to-air TV, closed captions and audio description are accessibility requirements, with obligations that have grown over the years. Playout needs to carry or insert captions, carry the audio description track and control loudness, so volume does not jump between show and break.
Outputs
SDI, SMPTE ST 2110, NDI, SRT or internet streams. Channels going to free-to-air, pay TV and streaming at the same time may need different versions of the same schedule, with break markers for ad insertion, such as SCTE messages.
Redundancy and reliability
Ask what happens when the main server fails. The standard at broadcasters is main and backup playout running the same playlist in parallel, with automatic or manual changeover at an output switch. Look at redundant power supplies, mirrored storage, monitoring with alarms and the time to get back on air for each type of failure.
Ask the vendor for a test with your full day's schedule and real material, including the most problematic files you receive. A demo with the manufacturer's material does not show the problems you are going to have.
On premises, virtualized or in the cloud
- On premises: servers in the equipment room, lower latency for live inputs and full control. Needs space, power and maintenance.
- Virtualized: the software runs on the station's own IT infrastructure, more flexible for spinning up channels.
- Cloud: channels launched quickly, good for themed channels, internet channels and remote backup. Live inputs and egress costs need care.
- Hybrid: main playout on premises and backup in the cloud, or the other way around, is an increasingly common arrangement.
Questions to ask before you sign
- 01ScheduleDoes the system import the scheduling and traffic data I use today, and return the as-run log?
- 02MaterialDoes it read every format I receive, without manual conversion?
- 03LiveHow does the operator join and leave live inputs and recalculate the schedule when a show overruns?
- 04FailureWhat happens when the main system goes down, and how long until I am back on air?
- 05SupportWho answers in the middle of the night, in my operators' language, and with what contractual response time?
- 06Total costLicenses, annual renewal, servers, storage and updates for the coming years.
There are many playout manufacturers, from large enterprise systems to software-based options, such as those from Softron. What changes between them is scale, integration and support, not just the feature list.
When you choose, listen to the people who will operate it. The master control operator spends the whole shift in front of the playout interface, and a confusing screen turns into an on-air error at night.
How i9 works with playout
i9TV designs and integrates playout and automation inside master control, with redundancy, monitoring, captions and integration with the router and graphics. The choice of system starts from your schedule, your material and your team.
If you are launching a channel or replacing a station's playout, the systems integration team helps define the requirements, test the options and put the channel on air.
i9 does this every day: production, broadcast, engineering and equipment, with one team accountable from start to finish.