PLAYOUT · CHANNEL-IN-A-BOX
Frame-accurate playout,
consolidated into one engine.
Kaster Playout integrates the scheduling engine, real-time transcoding, multi-layer CG overlay, and SDI / SMPTE ST 2110 signal output into a single server — replacing entire racks with software-defined, 24/7 automated transmission.
99.97%
Playout uptime · 12 months
↓60%
Hardware cost reduction
2–4 wks
Deployment cycle
SMPTE
ST 2110
Native IP infrastructure
WHY NOW
From multi-rack facilities to single-server automation,
this is the engineering shift broadcasters can't ignore.
Traditional playout rooms rely on operators on shift, SDI matrices, separate CG machines, and ad insertion appliances all working in lockstep — one node fails and you have black or wrong content on air. Channel-in-a-Box collapses that chain into one server, freeing engineers from the gallery to do higher-value work.
LEGACY · TRADITIONAL FACILITY
Multi-rack, multi-protocol, multi-shift
SDI matrix + scheduler + CG engine + ad inserter + monitoring — 5–7 distinct devices to maintain; any node failure risks black on air. Hardware refresh cycle: 7–10 years; engineering staffing requires 2–3 shifts of 24-hour coverage.
CHANNEL-IN-A-BOX · KASTER PLAYOUT
Consolidated, automated, zero-interrupt
Scheduling engine, real-time transcoding, CG overlay, and SDI / IP output all in one server; redundancy via hot-standby pairing; engineering coverage drops from 24-hour shifts to office-hours monitoring + on-call.
CAPABILITIES · THREE LAYERS
Three capability layers, threaded into one
fully automated playout chain.
Scheduling → ad & branding → signal routing. Each layer can be evaluated independently, licensed per channel, and scaled later.
Scheduling engine
Frame-accurate time alignment, automatic BXF rundown loading, and bidirectional integration with NRCS (ENPS / iNEWS) and traffic systems via XML/MOS. Schedule conflicts surface in real time, and break patterns can be dry-run before air.
- BXF / SCTE-104 standards
- NRCS / Traffic bidirectional sync
- Dry-run rundown preview
- Multi-channel parallel scheduling
Ad & branding · monetization
Multi-layer CG engine with dynamic logos, L-shape, tickers, sponsorship bars, and trailer beds. Ad insertion supports SCTE-35 cue tones and frame-accurate splice points so every frame can carry revenue.
- Up to 8 dynamic CG layers
- SCTE-35 frame-accurate splice
- L-shape / ticker / sponsorship templates
- HTML5 graphics templates
Enterprise signal routing
Seamless switching across SDI, NDI, UDP, SRT, and SMPTE ST 2110. Hot-standby redundancy, switching latency < 1 frame, and automatic failover when input signal is lost.
- SDI / NDI / UDP / SRT compatible
- SMPTE ST 2110 IP-native
- Hot-standby redundancy
- 4K UHD / FHD / HDR10 / HLG
WORKFLOW
From ingest to on-air ·
end-to-end automated media workflow.
Playout doesn't operate in isolation. It joins the other Point Media Tech systems into a complete on-air chain.
FIGURE 01 · End-to-end media workflow (INGEST → MAM → PLAYOUT → MASTER CONTROL → DELIVERY)
SPECIFICATIONS
Engineering specifications.
Full spec sheet and technical whitepaper available on request — book a session with our solution architects.
| Resolution | 4K UHD (2160p) · FHD (1080p/1080i) · HD (720p); upgrade path to 8K (4320p); mixed-resolution output from a single server |
|---|---|
| HDR | HDR10 · HLG · BT.709/BT.2020 colour space conversion |
| Broadcast infrastructure | Native SMPTE ST 2110-20/-30/-40 · compatible with SDI (HD-SDI / 3G-SDI / 12G-SDI) · NDI · SRT · UDP |
| Integration protocols | BXF (Broadcast Exchange Format) · XML/MOS (NRCS) · SCTE-35 / SCTE-104 · standard REST API |
| Redundancy | Hot-standby pairing; automatic failover on input loss; switching latency < 1 frame |
| Licensing | Per-channel licensing; single-channel up to large multi-channel deployments; perpetual + annual maintenance options |
| Deployment | Standard deployment 2–4 weeks; includes acceptance testing and engineer training |
HOW TO START
Three steps, from evaluation to go-live.
Request a trial
Submit the contact form. Our sales team responds within one business day and schedules a call with a solution architect.
Integration assessment
A solution architect reviews your existing playout architecture and confirms NRCS / Traffic / MAM integration requirements.
Deployment and go-live
After configuration we run acceptance testing (dry-run, failover, signal switching) and transition the system into production.
READY?
Ready to redefine your
on-air standard?
Step into the next era of automated playout.
FAQ
Frequently asked questions.
What is a playout system, and why do broadcasters need automated playout?
A playout system is the core on-air infrastructure for TV networks and OTT platforms, responsible for automatically airing programmes, ads, and CG graphics according to a rundown. Automated playout replaces manual operators, eliminates human error, and supports 24/7 continuous transmission — making it essential for modern broadcasters to reduce operating costs.
How does Channel-in-a-Box differ from a traditional playout facility?
Channel-in-a-Box (CiaB) consolidates scheduling, transcoding, CG overlay, and SDI output onto a single server. Compared to traditional multi-rack facilities, it reduces equipment cost and operator headcount by more than 60%, simplifies maintenance, and is well suited to broadcasters and OTT platforms running multiple channels in parallel.
How does Kaster Playout integrate with MAM and Master Control?
Kaster Playout exposes standard APIs that integrate with MAM systems, traffic/scheduling platforms, and Master Control rooms. The result is an end-to-end automated workflow from ingest to on-air delivery, with minimal manual intervention and faster deployment.
How is Kaster Playout priced?
Kaster Playout is licensed per channel and scales from single-channel deployments to large multi-channel facilities. Pricing options include perpetual software licenses and annual maintenance contracts. Final pricing depends on channel count, feature requirements, and deployment scale — contact a sales consultant for a detailed quote.
Does Kaster Playout support SMPTE ST 2110 IP broadcast infrastructure?
Yes. Kaster Playout provides full SMPTE ST 2110 support while remaining compatible with traditional SDI output, so it fits into both IP-native and hybrid facilities. It runs on standard server hardware, and our solution architects will help size the right configuration.
How should broadcasters evaluate playout vendors? What matters most?
Key selection criteria include: format compatibility (MXF, MP4, SMPTE ST 2110), stability and redundancy architecture, integration with existing MAM and Master Control systems, and the quality of local technical support. Contact our team to arrange a free requirements assessment with a solution architect.
Is Kaster Playout suitable for smaller broadcasters and OTT startups?
Yes. Kaster Playout uses modular licensing and scales from a single channel upward. Compared to traditional hardware-based playout rooms, a software-based playout system dramatically reduces capital expenditure. OTT startups typically begin with 1–2 channels, while larger broadcasters replace entire racks with Channel-in-a-Box. Most deployments recover the build cost within 12–24 months.
How does Kaster Playout integrate with newsroom (NRCS) and traffic systems?
Kaster Playout provides standard XML/MOS interfaces that integrate with leading NRCS platforms such as ENPS and iNEWS, plus BXF (Broadcast Exchange Format) for traffic systems. This allows programme schedules to flow automatically from traffic into the playout rundown. A typical integration, led by our solution architects, takes 2–4 weeks.
How does Kaster Playout achieve fully automated on-air delivery?
The Kaster Playout scheduling engine loads the rundown and triggers frame-accurate playback of programmes, ads, station IDs, and CG overlays. It supports multiple channels simultaneously, runs 24/7 without operator intervention, and — when integrated with Master Control and MAM — delivers a fully automated workflow from ingest through on-air.