A golden reference is a fixed, version-controlled clip together with the quality scores a known-good build produced on it, saved as the baseline a regression test compares against. Borrowed from software golden-master (characterization) testing, it does not measure whether an encode is good, only whether a new build is unchanged from the trusted one. In a pipeline, every change re-encodes the reference clips, scores them, and fails if the new scores drop beyond a tolerance band sized to the metric's noise rather than an exact line. The reference source must have headroom (a good encode landing high on the scale) so a drop is visible, and the source clip, the VMAF model file, and the tool versions must all be pinned. The key catch is to always compare against a frozen baseline, not the last build, or slow drift, fractions of a point each build, escapes the band until it sums to a visible loss. Re-baseline only by deliberate human approval, never on a red build.
The handbook · 7 volumes
Fora Soft Video Engineering Handbook
A golden reference turns quality into a regression test: fixed clips with expected scores reveal drift when an encoder or library changes. We wrote seven volumes covering the whole video stack, and for golden references start with Volume 1: VMAF, PSNR and SSIM, encoder versions and presets, with Volume 3 on QoE monitoring. Written by Nikolay Sapunov, CEO at Fora Soft.
Encoder updates changing quality and nobody notices until viewers do?
Share your pipeline and content mix: we build a golden reference set with thresholds and wire it into CI so drift blocks the release. 250+ video products shipped since 2005.
