Frame-accurate
Channel-in-a-Box playout automation.
Kaster Playout is Point Media Tech's playout automation system: the scheduling engine, real-time transcoding, multi-layer CG overlay, SCTE-35 ad insertion and SDI / SMPTE ST 2110 output run on a single server, with hot-standby redundancy behind 24/7 automated playout. Engineering coverage can move from 24-hour shifts to office-hours monitoring plus on-call.
99.9%System availability commitment
↓ 60%Hardware cost reduction
2–4 wksDeployment cycle
ST 2110Native IP infrastructure
Playlist, timeline, dual preview —
one screen runs the channel.
The Kaster Playout console is built around the playlist: channels on the left, a frame-accurate schedule and four-track timeline in the middle, PGM/PVW and the next-event countdown on the right. Operators maintain the list; the engine executes the take.
From separately maintained racks to single-server automated playout,
what goes away is the seams between boxes.
A Channel-in-a-Box playout system puts scheduling, CG, ad insertion and signal output on one server, removing the failure points behind dead air and wrong content. Traditional playout rooms rely on operators on shift, SDI matrices, separate CG machines and ad insertion appliances working in lockstep, and one node failing puts black or wrong content on air. After consolidation, engineers move from the desk to monitoring, maintenance and playlist quality.
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.
Consolidated, automated, with built-in redundancy
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.
Today · Separate rooms, separately maintained
- Engineers on rotating shifts
- An SDI matrix
- A standalone character generator
- A separate ad-insertion box to coordinate with
After · Automated, on one machine
- The whole chain on a single server
- Scheduling, graphics and ad insertion share one playlist
- Hot standby, switching in under a frame
- Engineers freed from sitting the desk
Three capability layers, threaded into one
fully automated playout chain.
Kaster Playout has three layers — scheduling, ad & branding, and signal routing — and each can be evaluated independently, licensed per channel, and scaled later.
Scheduling engine
The scheduling engine loads BXF rundowns automatically, fires each event with frame-accurate time alignment, and integrates bidirectionally 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
The multi-layer CG engine handles dynamic logos, L-shape, tickers, sponsorship bars and trailer beds. Ad insertion supports SCTE-35 cue tones and frame-accurate splice points, so breaks land on frame boundaries and sponsorship and ad inventory are managed from the same playlist.
- Up to 8 dynamic CG layers
- SCTE-35 frame-accurate splice
- L-shape / ticker / sponsorship templates
- HTML5 graphics templates
Signal routing & redundancy
The signal layer switches across SDI, NDI, UDP, SRT and SMPTE ST 2110 sources. Hot-standby redundancy, switching latency < 1 frame, and automatic failover to the backup source when input signal is lost.
- SDI / NDI / UDP / SRT inputs
- SMPTE ST 2110 IP-native
- Hot-standby redundancy
- 4K UHD / FHD / HDR10 / HLG
Primary · on air
Standby · hot, in sync
Input signal lost
Standby takes over (under one frame)
From ingest to on-air ·
end-to-end automated media workflow.
Kaster Playout shares one signal model and asset structure with Smart Ingest, MAM and Master Control, with no third-party integration layer between products.
- IngestAsset capture · BXF / MXF / MP4 transcoding and archive
- MAMAsset management · metadata, tagging, rights
- PlayoutScheduling + CG + ads + SDI / IP output
- Master ControlGallery monitoring · multi-channel oversight
- DeliverySDI / IP / OTT / DVB-T multi-path distribution
Engineering specifications.
The full specification is in the Kaster Playout v8.5 technical whitepaper; book a solution architect for a live demonstration.
| 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 |
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.
Frequently asked questions.
What is a playout system, and why do broadcasters need automated playout?
A playout system airs programmes, ads, station IDs and CG graphics automatically from the schedule, at the last stage of the on-air chain. Automation hands the take to the scheduling engine, so operators maintain the playlist and handle exceptions, which reduces human error and supports 24/7 transmission. Point Media Tech's Kaster Playout backs its 99.9% system availability commitment with hot-standby redundancy.
How does Channel-in-a-Box differ from a traditional playout facility?
Channel-in-a-Box (CiaB) consolidates scheduling, transcoding, CG overlay and SDI/IP output onto one server, replacing a separately maintained SDI matrix, CG engine and ad inserter. Fewer devices means fewer failure points and less maintenance, which suits broadcasters and OTT platforms running several channels in parallel. Compared with traditional multi-rack facilities, it reduces equipment cost and operator headcount by more than 60%.
How is a playout system priced, and does it suit smaller broadcasters or OTT startups?
Kaster Playout is licensed per channel, starts from a single channel and scales to multi-channel facilities, with software licences and annual maintenance contracts available. Pricing depends on channel count, feature requirements and deployment scale, so contact a sales consultant for a quote. OTT startups can evaluate with 1–2 channels, while broadcasters replace entire racks with Channel-in-a-Box and typically recover the build cost within 12–24 months.
Does the playout system support SMPTE ST 2110, and can it output 4K and HD at the same time?
Kaster Playout natively supports SMPTE ST 2110-20/-30/-40 and remains compatible with HD-SDI, 3G-SDI and 12G-SDI output. Resolutions cover 4K UHD (2160p), FHD (1080p/1080i) and HD (720p) with HDR10 and HLG, plus an upgrade path to 8K (4320p). One server can output several channels at different resolutions, for example a 4K UHD main channel and a 1080i backup.
How does the playout system integrate with NRCS, traffic, MAM and master control?
Kaster Playout connects to NRCS over XML/MOS, imports traffic schedules via BXF, and links to MAM and Master Control automation over a REST API. On the NRCS side it works with ENPS, iNEWS and similar newsroom systems, and it shares one signal model and asset structure with Point Media Tech's ingest, MAM and master control products. Integration is led by our solution architects and typically takes 2–4 weeks.
How should broadcasters evaluate playout vendors? What matters most?
Evaluate a playout system on format and signal compatibility (MXF, MP4, SDI, ST 2110), redundancy, MAM and master control integration, and local support. Point Media Tech's team comes from control rooms, OB vans and machine rooms, and as a Taiwan-based team provides Chinese-language support. For technical detail, download the Kaster Playout v8.5 whitepaper or use the contact form to arrange a free requirements assessment.
Evaluate your playout chain
with Kaster Playout.
Download the Kaster Playout v8.5 whitepaper, or book a solution architect to review NRCS, traffic and MAM integration in your facility.