Feature · Loudness QC

Every episode, measured to
broadcast spec.

EBU R128 and ITU-R BS.1770-compliant LUFS measurement on every run. Pick a target profile — broadcast, streaming, podcast — and get pass/fail plus integrated LUFS, true peak, and loudness range the moment the file lands.

Start freeTalk to sales →
The problem

Loudness drifts. Partners reject.

Episode to episode, engineer to engineer, your delivery loudness wanders. A partner's ingestion spec requires −23 LUFS, you ship at −18, and the file bounces. You learn two days later. You re-master, re-deliver, and hope nothing else drifted.

Every file needs a numerical truth about its loudness — measured the same way every time, against the same spec — before it leaves your facility.

How it works

Measured by spec, reported on arrival.

01
Attach a loudness profile
Pick from built-in profiles — EBU R128 broadcast (−23 LUFS), AES streaming (−16 LUFS), podcast (−16 LUFS) — or define your own with custom target, peak, and range limits.
02
Worker measures on arrival
ffmpeg's ebur128 filter runs against the audio at ingest. Integrated LUFS, short-term, true peak (dBTP), and loudness range (LRA) are all captured with full BS.1770 R2 compliance.
03
Pass/fail on the Overview
Numeric card on every run's Overview tab. Runs-list chip shows compliance at a glance. Loudness JSON artifact downloadable for integration with other tools.
What you get

Numbers your partners will accept.

Integrated LUFS + true peak + LRA
The three numbers your partners actually check. Integrated loudness, true-peak in dBTP (not sample peak), and loudness range per BS.1770 R2.
Named target profiles
ebu_r128_tv, aes_streaming, podcast, podcast_mono, and custom. Profiles are defined once and applied across as many pipelines as you want.
Per-run overrides
Your pipeline targets broadcast R128, but this one episode needs to be delivered at −16 LUFS. Override on the run without touching the pipeline.
Downloadable JSON artifact
The full measurement is written to loudness.json as a standard artifact on every run — pipe it into your asset management system, ingest workflow, or partner handoff.
FAQ

Frequently asked questions

Is the measurement BS.1770-compliant?

Yes. ffmpeg's ebur128 filter implements ITU-R BS.1770 R2 and EBU R128. Integrated LUFS, short-term LUFS, momentary LUFS, loudness range, and true peak are all captured.

How is true peak reported — sample peak or actual true peak?

True peak in dBTP, measured via 4× oversampling inside ebur128. Sample peak is not sufficient for modern broadcast specs — we use the real thing.

Can I normalize to target, or is this measurement-only?

Measurement-only today. Normalization is on the roadmap — ping sales if you need it and we'll prioritize accordingly.

What about dialog loudness (LKFS) vs integrated?

Integrated loudness per BS.1770 is what's reported. For dialog-gated measurement (LKFS / ATSC A/85), contact sales — we can add it to a custom profile.

Does it work for multi-channel or 5.1 audio?

Yes. ebur128 handles multichannel via BS.1770 channel weighting. The integrated measurement combines channels correctly for stereo, 5.1, and beyond.

Stop discovering loudness failures at delivery.
Attach a loudness profile to your pipeline and every run tells you where it stands against spec.
Create your accountSign In →