Feature · Broadcast Compliance

Know if your media passes spec,
before it ships.

Every run is probed and validated against a named delivery profile — broadcast HD 29.97, streaming 1080p 30, podcast audio — with per-rule pass/fail on the frame rate, resolution, codec, pixel format, color primaries, bit depth, and aspect. The moment the file lands, you know.

Start freeTalk to sales →
The problem

Delivery failures show up at air time.

A vendor ships you a file that looks fine. You don't find out the frame rate is 24 fps, not 29.97, until you hit the playout server. You don't find out the chroma subsampling is wrong until the encoder chokes. You don't find out the bit depth is 10-bit when your spec calls for 8, or the aspect is 16:9 anamorphic when it needed to be 1920×1080 square-pixel.

Manual QC is expensive and catches the problem too late. You need the spec check to be automatic, and you need the result the instant the file lands.

How it works

Probed on arrival, validated on the spot.

01
Pick a delivery profile
Attach a named profile to your pipeline, preset, or one-off run: broadcast HD 29.97 / 25, broadcast UHD, streaming 1080p / 720p, podcast audio. Per-run overrides welcome.
02
We probe the file
As soon as the file lands, we run ffprobe against every video and audio stream, normalize fractional frame rates, and check every rule in the profile.
03
Get pass/fail with receipts
Conformance chip on the run's Overview card. Per-rule breakdown lists expected vs measured. Filter the runs list by compliance status. Optional JSON / PDF report in the delivery package.
What you get

Per-rule clarity, packaged for your partners.

Named delivery profiles
broadcast_hd_2997, broadcast_hd_25, broadcast_uhd_2997, streaming_1080p_30, streaming_720p_30, podcast_audio_only — pick one, or layer a per-run override when an episode needs a different target.
Per-rule breakdown
Every rule reports expected vs measured plus a human-readable note. "Source is 24 fps; target is 29.97 fps." No ambiguity, no re-checking.
Filterable runs list
One toggle to show only compliant, only non-compliant, or only "no profile attached." Find problem deliveries across a whole channel or campaign in seconds.
Delivery-package report
Opt-in: each destination can include the conformance report (JSON or PDF) alongside the media asset when it ships. Partner sees the receipts with the file.
FAQ

Frequently asked questions

Which rules are checked?

Video: frame rate (including fractional 30000/1001), resolution, codec, pixel format, aspect ratio, bit depth, color primaries. Audio: codec, sample rate, channel count, bit depth. Container format. Per-rule tolerances are configurable on the profile.

Can I define my own profile?

Yes. The profile registry lives in config alongside the built-ins. Contact sales if you need a bespoke profile and we'll help you add it.

What if a file fails?

The run completes; compliance is a side-car report, not a blocker. You get the Overview chip, the per-rule report, and the ability to route or flag the run however you want — hold in review, reject in delivery, alert a channel, etc.

When is the probe run?

As part of the worker pipeline after media prep, before downstream analysis. No extra wait — it runs in parallel with loudness measurement and other QC steps.

Does it work with audio-only media?

Yes. Use the podcast_audio_only profile (or define your own) to validate bitrate, sample rate, channel count, and codec on podcast deliveries.

Stop catching spec failures at air time.
Attach a delivery profile to your pipeline and every run reports pass/fail the moment the file lands.
Create your accountSign In →