Can Channel Foundry run beside the playout system we already have?

Yes. Some customers start by sending an existing playout output into Edge Splice and Network Fabric, then move channels into Foundry when it is time to retire the old system.

How are ad breaks defined?

Breaks are part of the channel's structure. You set positions and durations, and Foundry inserts SCTE-35 cues at those points so downstream ad insertion can replace them.

Do we need to re-encode our library?

Not usually. Foundry ingests common mezzanine formats and conditions them for playout. Files that fail checks for format, loudness, or captions are flagged before they reach air.

Cloud playout and channel origination

Turn a content library into a 24/7 channel with its own ad breaks

Channel Foundry is the playout and scheduling layer. Programmers build the day, apply the channel's look, and place ad breaks once. The same channel then plays out to FAST platforms, your own apps, IPTV headends, and in-room TV without a second system.

Book a demo Technical specifications

What it does

Scheduling and EPG
Daypart grids, programming blocks, loops, and rules that auto-fill the schedule from tagged library content. Program guide data exports for each distribution partner.
Playout automation
Frame-accurate playlists that mix file-based programming with live windows. Secondary events trigger graphics, break signals, and source switches on time.
Branding and graphics
Channel bugs, lower thirds, up-next promos, and squeeze-backs rendered in the output, so every platform receives the same branded feed.
Break structure
Define break positions and durations once. Foundry writes SCTE-35 cues into the output, and unsold time falls back to promos or slate instead of dead air.
Content preparation
Ingest and normalize mezzanine files, set loudness to ATSC A/85 or EBU R128 targets, and carry captions through to every output.
As-run and compliance
As-run logs record what actually played, when, and on which output, ready for reconciliation with ad delivery and music or rights reporting.

How it works

Ingest
Load library files and rights windows; Foundry checks format, loudness, and captions.
Program
Build the schedule from blocks and rules, with live windows where events will air.
Brand
Attach graphics templates and break structure to the channel, not to each episode.
Play out
Originate the channel with SCTE-35 cues in the output and hand it to Network Fabric.

Technical specifications

Formats, protocols, and deployment targets. Exact versions and partner-specific profiles are confirmed during scoping.

Channel Foundry technical specifications
File ingest	MP4, MOV, MXF (mezzanine), with sidecar captions
Live inputs	SRT, RIST, RTMP, HLS pull, MPEG-TS over UDP/RTP
Outputs	HLS, MPEG-DASH, CMAF, MPEG-TS (SRT, UDP multicast)
Ad signaling	SCTE-35 splice_insert and time_signal with segmentation descriptors
Captions	CEA-608/708 passthrough; WebVTT and IMSC for streaming outputs
Loudness	ATSC A/85 (−24 LKFS) or EBU R128 (−23 LUFS) normalization
Program guide	XMLTV and partner-specific schedule exports
Deployment	Managed cloud, your cloud account, or on-prem

All standards and versions

Turn a content library into a 24/7 channel with its own ad breaks

What it does

Scheduling and EPG

Playout automation

Branding and graphics

Break structure

Content preparation

As-run and compliance

How it works

Ingest

Program

Brand

Play out

Technical specifications

Where Channel Foundry is used

Channel Foundry questions