Set it up

Before a channel runs it is described, not coded. One form builds every playout channel as a single route through the channel’s own mental model — Sources, Programme, Outputs, Ship — with a live ‘This channel’ manifest down the side that restates what will be built and updates on every edit. The output is a launchable product template the daemon runs; the same form is what the runner embeds when you configure a channel in place.

01 Name the inputs

The live inputs feeding the switched programme. The one-feed case is there on arrival; a second input is one click — here an RTMP remote alongside the SRT studio — and the manifest counts both immediately.

02 Compose the programme

How items are switched, formatted and composited on air: normalised switching and the flagship ladder by default, with an ad-splice axis and a branding layer each one click away. The manifest lists every axis the moment it turns on.

03 Choose the delivery

Where the channel is delivered — CMAF HLS/DASH for players and an SRT mezzanine egress for downstream contribution, delivered together. At least one route must be on, and the manifest flags it if none is.

04 Build the template

With every stop satisfied the manifest reads Valid and Build is enabled — one click produces the launchable product template. A stop that isn’t ready keeps its check dark and the manifest names what is left to fix.

Seen in: Sources, On Air, Outputs, One SRT feed, Two feeds, switched