WaveLens Docs
Documentation

Everything for building an audio QA pipeline with WaveLens.

WaveLens is an objective audio testing toolkit — command-line tools for comparing audio files, generating test signals, and automating audio QA in CI. This is the full set of guides, command references, and report walkthroughs — from generating test signals to reading a failure down to the sample.

v0.7.0-beta Release notes

Audio QA has usually meant one of two things: a person listening carefully and hoping they catch the regression, or a pass/fail script that tells you something changed without telling you what. WaveLens is built for objective audio testing instead — six independent checks, one report, and a verdict backed by numbers instead of an opinion.

As an audio QA tool it's meant to sit in a pipeline, not just on a desk: generate test material with wavgen, compare reference against device-under-test with wavelens, and roll many reports into one CI-friendly pass/fail summary with wavsummary.

From comparison to verdict, one command

What you actually get back

$ wavelens analyze \
    --ref reference.wav \
    --dut device_under_test.wav \
    --out report.html

wrote report.html (bit_exact: FAIL, level_fidelity: PASS)
The one-line stdout summary — the full picture is in the report itself.
report.html
Overall Verdict PASS
Analysis Mode
Frequency Domain
Alignment
0.998
Spectral
PASS
Signal Alignment Spectral Fidelity Bit-Exactness Level Fidelity Distortion Loudness
Illustrative — every report is a real, self-contained HTML file, no viewer required.

How wavelens works

One engine, two files in, a verdict out

$ wavelens analyze --ref reference.wav --dut device_under_test.wav
reference.wav
The known-good source
device_under_test.wav
The processed copy
wavelens
Six independent checks, one pass
Signal Alignment Spectral Fidelity Bit-Exactness Level Fidelity Distortion Loudness (BS.1770)
report.html
Self-contained, always written
report.json
Optional — add --json for the raw numbers
Input: 16 or 24-bit PCM WAV, up to 96 kHz sample rate.
Output: an HTML report every run, plus JSON on request.

How the toolkit fits together

1. Generate
wavgen
Synthesize reference test material — tones, sweeps, noise — or use real content you already have.
2. Compare
wavelens
Compare reference against device-under-test, produce a self-contained HTML verdict.
3. Roll up
wavsummary
Aggregate many reports into one pass/fail summary with an exit code, built for CI.

wavchan splits/joins channels before a comparison — it slots in around the core compare step, not into the main pipeline itself.

The toolkit

5 command-line tools, one license

Popular pages

Frequently asked

Product & licensing — for per-tool questions, see each guide above

Is there a free trial?

Yes — a TRIAL license runs for 30 days by default. It behaves identically to a paid license; nothing is feature-limited during the trial.

Which platforms are supported?

macOS, Windows, and Linux — each tool ships as a single self-contained executable per platform, no runtime or installer required.

Does WaveLens need an internet connection to run?

No. License verification is fully local (an embedded public key checks your .lic file's signature) — no network call is ever made, at any point.

What audio formats does it accept?

16-bit or 24-bit PCM WAV, 22,050–96,000 Hz, mono or stereo. Other formats are rejected at load time with a clear error, never silently converted.

Can I run WaveLens in CI?

Yes — wavsummary scans a directory of wavelens reports and rolls them into one pass/fail summary with an exit code built for pipeline gating.

How does licensing work for a team?

Three license types — Trial, Personal, and Enterprise — each tied to one signed .lic file. See License setup for how a tool resolves which license it's running under.