How the checks work, what a failure actually means, and the occasional release note — written by the people building WaveLens.
Six checks, one verdict — a walkthrough of what Signal Alignment, Spectral Fidelity, Bit-Exactness, Level Fidelity, Distortion, and Loudness are actually measuring, and what a FAIL on each one really means for your file.
EngineeringTwo files can sound identical and still not be the same file. Why bit-exactness is a stricter, more literal claim than "passes a listening test" — and when you actually need it.
Case studyA nightly build comparison caught a level-fidelity drift that a listening pass missed entirely. What the report looked like, and how it changed the release checklist.
EngineeringLoudness can be technically "in spec" and still sound wrong, or vice versa. What the BS.1770 measurement actually integrates, and where the check has blind spots.
Guideswavsummary scans a directory of reports and exits non-zero on any failure. Gating a build on it, from a single CI step to a full release checklist.
EngineeringFolding six channels into two isn't just adding them together. What wavchan does during a downmix, and why comparing before/after needs its own tolerance.
Release notesThis release adds a full BS.1770 loudness check and a new Analysis Mode tile on every report, showing whether a comparison ran in time-domain or frequency-domain mode.
EngineeringThe two terms get used interchangeably and shouldn't be. A precise breakdown of what each one checks, and which one your QA process actually needs.
EngineeringTones, sweeps, and multitone material need to be exactly reproducible run to run. How wavgen seeds its generators, and why that matters for a regression suite.
GuidesA quick peak/level scan can mean two different things depending on which number you're reading. What wavscan reports, and when each measurement is the right one.
Case studyA delivery pipeline that used to need a full listening pass per episode now gates on six automated checks. What changed, and what still gets a human ear.
Release notesThis release speeds up the Spectral Fidelity check on large files and adds a --tolerance flag for teams that need more headroom than the strict default.
EngineeringSame sample rate, same bit depth, same waveform to the ear — and still a FAIL. The container-level differences that trip up a byte-for-byte comparison.