What WavRead writes

Every analysis produces two documents. One holds what was measured. The other says what it might mean. They are kept apart on purpose, because a measurement and an opinion are not the same kind of thing.

Track Document

Everything measured, in words and tables — written to be read by a person or handed to an AI assistant. Markdown, yours to copy anywhere.

Feedback Report

What's working and what to check. Each finding carries the measurement it stands on, what it may mean, and what to listen for.

What the Track Document contains

SectionWhat's in it
Delivery contract Integrated loudness (LUFS), loudness range, true peak in dBTP by oversampling, sample peak per channel, crest factor, clipped samples, DC offset, sample rate and encoding.
Structure Detected sections with timestamps, tempo, key, and how the energy changes from one section to the next.
Frequency balance 1/3-octave spectrum grouped into named regions, with the share of measured energy each carries.
Over time Loudness, stereo width and mono compatibility measured across the track rather than averaged into one number.
Chords and melody Estimated chord events, and the vocal melody transcribed into timed note phrases.
Lyrics Transcribed from the vocal part when there is one, with timings.
Instrumentation (stems) Every part measured on its own — level, peak, true peak, clipping, when it enters, how busy it is, where its energy sits — plus an arrangement grid of what plays in which section.
What the master bus adds (captures) Delay times, how long the added tail takes to decay, and the tone change through the bus. Measured as the difference between your master and your parts.
Your markers Notes you wrote at a timestamp, kept separate from what WavRead measured and labelled as yours.
Provenance Which version of WavRead produced this, which DSP libraries, which models, when, and which mix the numbers describe.

A finding is three separable parts

WavRead never gives you a processing recipe. It measures; your DAW edits. Every finding in the Feedback Report is written so you can disagree with the interpretation while keeping the measurement:

3. This part reaches full scale before the mix bus: Lead (4,210 samples).
   May mean: Measured on each part's own file, across its real channels.
             Whatever the mix bus does afterwards, the damage is already
             in the part.
   Listen for: That instrument alone, at the loudest point — for a
               flattened transient or a crackle on the peaks.
   Heard at: 1:42–1:47

The measurement is a fact. What it may mean is an inference you can reject. What to listen for is how you check it yourself.

Written for AI assistants too

The Track Document is plain Markdown with stable headings and tables — hand it to any assistant and ask it questions about your mix. Nothing is uploaded by WavRead itself; sharing the document is your decision, and it contains only measurements, not your audio.

Anything unmeasurable says so

A dash in a WavRead document means unavailable, never zero. If a value could not be measured — an older analysis, a file too short for a particular window, a take with no quiet gap to measure a tail in — the document says which and why. A number that isn't there is more useful than a number that's wrong.