WavRead 1.4.0 — Evidence-First Findings
Findings you can check instead of believe.
Listen to the evidence
Every finding that can be heard now carries the measurement, what it was compared against, and a Listen button that plays and loops exactly the range it stands on.
True peak reaches 1.4 dBTP — above full scale between samples.
1.4 dBTPagainst0 dBTP full scale· ▶ Listen
Press it and the track jumps to the loudest moment and loops there. Mono-compatibility findings play their worst stretch and tell you to switch Mono on while it repeats. The dynamic-arc finding plays the loudest section.
Findings also open the graph they came from — Show in Mix on the spectral ones, Stems on the arrangement one — so the number and the picture of the number are one press apart.
A finding is now three separable parts
- the measurement — what was found
- May mean — what it may indicate, always hedged, because a measurement rarely proves a cause
- Listen for — what to do with your ears
WavRead used to hand out processing recipes: "try a broad 2–4 dB cut around 200–400 Hz on the densest elements", "back off the limiter", "add a low sine layer". Seventeen of them are gone. WavRead measures; your DAW edits, and it has no idea what is in your session.
Where an action is offered it is one the app can actually perform — mono findings point at the Mono switch in the player, and the low-mid finding points at Suggested EQ, which stays the only place a change is proposed and is inspectable and level-matched.
Stems, named only when earned
Where separation data exists, a band finding says which stems carry the energy — "most of that energy is in the bass and other stems (64.6% of the band)" — weighted by how loud each stem actually is, so a quiet part that happens to be mostly low-mid is not blamed. When the energy is spread and no stem carries a clear majority, WavRead names nobody rather than guessing. Every attribution says separation is imperfect and is a pointer rather than proof.
Note
Analyses made by earlier versions keep their existing findings until you reanalyze — the new voice, the Listen buttons and stem attribution appear once a track has been analyzed by 1.4.0. Settings → Reanalyze all updates the whole library.
Free during development, still unsigned (right-click → Open on first launch).