Skip to content

Platform

From storage to screen, step by step.

APlayout is a cloud playout service for 24/7 linear TV and FAST channels. Eight steps, one service, one console.

01 · Store

A media library that resumes, not restarts

Upload in the browser or drop files over SFTP. Large uploads resume after a dropped connection.

  • Resumable uploads
  • SFTP
  • Per-channel assignment
The Store step in the APlayout console

02 · Ingest

Catalogues, not copies

Add an MRSS feed as a catalogue. Each video is fetched shortly before air and released afterwards.

  • MRSS
  • Just-in-time fetch
  • Release after air
  • Conform
  • Loudness
MRSS Just-in-time fetch Release after air Conform Loudness

03 · Programme

Decide what may air, per channel

Allow titles, feeds and collections per channel, block what must never air, and keep age-rated titles out of daytime.

  • Allow lists
  • Blocks
  • Genre and language
  • Watershed
Allow lists Blocks Genre and language Watershed

04 · Schedule

A rundown that never runs dry

A rolling 24/7 rundown with automatic gap filling, standby slate and logo bug.

  • Rolling rundown
  • Gap filling
  • Standby slate
  • Logo bug
  • As-run log
The Schedule step in the APlayout console

05 · Monetise

Ad breaks to the frame

Mark cue points at HH:MM:SS:FF. Breaks follow your rules and fill with pods, signalled with SCTE-35.

  • Cue points
  • Commercial pods
  • Advertiser separation
  • splice_insert
  • HLS ad markers
The Monetise step in the APlayout console

06 · Guide

The guide travels in the stream

DVB EIT now/next and schedule in the transport stream, and an XMLTV guide for FAST platforms.

  • DVB EIT p/f
  • EIT schedule
  • XMLTV
  • Metadata rules
The Guide step in the APlayout console

07 · Play out

An engine of your own

Each customer’s channels run on a dedicated playout engine, controlled from the console over an authenticated API.

  • Dedicated server
  • Authenticated API
  • Live output frame
The Play out step in the APlayout console

08 · Deliver

SRT, HLS and multicast

SRT caller or listener, HLS with ad markers, and MPEG-TS over UDP multicast with DVB service information.

  • SRT
  • HLS
  • UDP multicast
  • DVB subtitles
  • Alternate audio
SRT HLS UDP multicast DVB subtitles Alternate audio

Built in at launch.

  • Resumable browser uploads and SFTP drop folders
  • MRSS catalogues with just-in-time media fetch, released after air
  • Automatic conform to the channel standard with loudness normalisation
  • Channel programming rules: allow lists, feeds, collections, blocks, genre, age and watershed filters
  • 24/7 rolling rundown with gap filling, standby slate and logo bug
  • Frame-accurate cue points (HH:MM:SS:FF) with CSV import and black/silence suggestions
  • Commercial pods with break rules, advertiser separation and rotation
  • SCTE-35 splice_insert in the transport stream and HLS ad markers
  • DVB EIT present/following and schedule, and XMLTV export
  • Guide metadata automation with provenance and a completeness score
  • DVB subtitles from programme subtitle files and alternate audio
  • SRT caller and listener with passphrase, HLS, and MPEG-TS over UDP multicast
  • A dedicated playout engine per customer, controlled over an authenticated API
  • Every output analysed for PSI/SI tables, PCR and continuity

Not in the first release

  • Live inputs
  • 1+1 or N+1 playout redundancy
  • 4K / UHD output
  • SCTE-104
  • SDI and SMPTE ST 2110
  • FAST distribution or ad sales

Questions.

How does media get into APlayout?
Three ways: upload in the browser (large files resume after a dropped connection), drop files into your SFTP folder, or add an MRSS feed. Everything is checked and conformed to your channel standard — resolution, frame rate and loudness — before it can air.
Can I build a channel from an MRSS feed without copying my whole catalogue?
Yes. APlayout treats an MRSS feed as a catalogue: titles and guide metadata are imported, but each video is fetched only shortly before it is scheduled to air and released again afterwards. You schedule from thousands of titles without paying to store them twice.
Can I control what may air on each channel?
Yes. Each channel has programming rules: which titles, feeds and collections it may use, what is blocked, genre, length and language filters, and a watershed that keeps age-rated titles out of daytime. Automatic gap filling follows the same rules.
Which outputs does APlayout deliver?
SRT (caller or listener, with passphrase), HLS with ad markers, and MPEG-TS over UDP multicast with DVB service information. Every output is analysed for PSI/SI tables, PCR timing and continuity.
Is my playout engine shared with other customers?
No. Each customer gets a playout engine on a dedicated server. The console controls it remotely over an authenticated API, so one customer’s load never touches another’s channel.
What is the difference between playout and a CDN?
Playout makes the channel: it schedules programmes and ads and produces the continuous signal. A CDN distributes a finished stream to many viewers. APlayout’s HLS and SRT outputs can feed any CDN or FAST platform.

Be first on air.

Join the waitlist. One confirmation e-mail, then only launch news.

Join the waitlist