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 Spectral Fidelity, Bit-Exactness, Level Fidelity, Artifact Detection, Distortion, and Loudness are actually measuring (plus the Signal Alignment step that runs before all of them), 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.
EngineeringLoudness can be technically in spec and still sound wrong, or vice versa. What the BS.1770 measurement integrates, why a WaveLens report shows it without failing the verdict, 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.
Engineeringwavelens compares one mono or stereo pair at a time, so 5.1 content has to be taken apart first. How to split it with wavchan, compare each pair, and why wavchan doesn't downmix.
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. Why wavgen's output is repeatable, and how that holds up a regression suite.
Guideswavscan reports peaks, but not the kind a level meter does. What it measures at one moment in a file, how the window size changes what you see, and where to look for whole-file peak and loudness.
EngineeringSame sample rate, same sound to the ear — and still a FAIL. What actually breaks a sample-for-sample comparison, and what doesn't.