Scenarios
Three common mixing problems — and how Audit Audio would catch them. These aren’t fabricated testimonials. They’re technically-grounded walkthroughs of what the diagnostics would actually find, what the numbers would show, and what you’d do about it. If you’ve ever mixed a track, you’ve faced at least one of these.
The Problem
A common scenario: you've dialed in a deep, sub-heavy kick drum that rattles the room on your monitors. The fundamental sits around 42Hz, with a long decay that fills the low end beautifully. You export the track, play it on your phone — and the kick is gone. Not quieter. Gone. What happened? The phone speaker physically cannot reproduce 42Hz. Most phone speakers roll off sharply below 200-300Hz. If your kick's only defining characteristic is its sub-frequency fundamental, there's nothing left for small speakers to reproduce. The kick exists only as inaudible air movement.
What Spectrum Analysis + Variance Map Would Detect
Audit Audio's Spectrum Analysis loads your mix alongside a reference track in the same genre. The analysis reveals that while your sub energy (20-60Hz) matches the reference almost identically, your mix is deviating by -6.2dB in the 100-250Hz range where the reference has strong kick harmonic content. The Variance Map flags the LOW band (60-250Hz) as Critical with a -5.8dB deviation, while the SUB band (20-60Hz) shows Minor deviation — confirming that all the kick energy is concentrated below the audible range of most consumer playback systems.
Diagnostic Readings
How to Fix It
The solution isn't to boost 100-250Hz with EQ — that would muddy the entire mix. Instead, add harmonic saturation to the kick drum to generate upper harmonics (100-400Hz) that give small speakers something to latch onto. Alternatively, layer a short, clicky transient sample that provides attack in the 1-3kHz range without affecting the sub weight. A third option: pitch the kick fundamental up to 55-60Hz, which is still deep enough for club systems but has enough harmonic structure to survive phone playback. After these changes, re-running the analysis should bring the LOW band deviation within ±1.5dB of the reference.
The Problem
You've pushed the master bus limiter hard. The waveform looks like a solid brick. The peak meter barely moves. You upload to Spotify, and — somehow — the track sounds quieter than professionally mastered songs in the same playlist. Worse, it feels flat. The chorus doesn't hit any harder than the verse. There's no emotional contrast. The loudness war promised that louder masters win, but streaming normalization turned that logic on its head. Crushing your dynamics doesn't make you louder on Spotify — it makes you quieter with less impact.
What Dynamic Range Would Detect
Audit Audio's Dynamic Range tool measures your track at DR 4 with -7.2 LUFS Integrated and a PLR of 5.1. The analysis compares against a genre-appropriate reference (electronic/pop) sitting at DR 7.8 with -10.1 LUFS Integrated and PLR 9.2. When Spotify normalizes both tracks to -14 LUFS, the reference retains its transients and dynamics — it still sounds punchy and alive. Your track, already crushed to -7.2 LUFS, loses 6.8dB of level during normalization but gets zero transients back. The limiter already flattened them. The Dynamic Range tool also detects 47 inter-sample peaks above 0dBFS that will cause audible distortion after lossy encoding, despite your limiter ceiling being set to -0.3dBFS.
Diagnostic Readings
How to Fix It
Back off the limiter threshold by 2-3dB. Set the limiter ceiling to -1.0dBFS (not -0.3) to catch inter-sample peaks. Target -10 LUFS Integrated instead of -7 — this gives the limiter room to preserve transients while still hitting competitive loudness for streaming. After these adjustments, re-run the Dynamic Range analysis. The DR value should climb to 6-7, PLR should reach 8-9, and ISP detections should drop to zero. The track will measure quieter on a peak meter but will sound louder and more impactful after platform normalization — because the transients survived.
The Problem
You've used a stereo widening plugin on your master bus, panned synth layers hard left and right, and applied a mid-side EQ that boosts the side channel across the entire spectrum. In headphones, the mix sounds enormous — like it's happening outside your head. Then you hear it on a club system (mono), a Bluetooth speaker (mono), or a phone (mono), and the mix collapses. The synth pads that sounded cinematic are now thin and phasey. The kick has lost half its weight. The lead vocal is quieter than it was. All that width came at the cost of mono compatibility — and mono is how most people actually hear music outside of headphones.
What Stereo Field Would Detect
Audit Audio's Stereo Field tool displays a goniometer (Lissajous) pattern with significant energy on the horizontal axis — a classic sign of anti-phase content. The Phase Correlation meter reads -0.42 below 150Hz, meaning the low end is actively canceling itself in mono. Stereo width analysis shows the SUB band (20-60Hz) at 38% width, well above the safe threshold of 30%. The HI-MID band (2-8kHz) measures 94% width with 12% anti-phase content. The Mono Compatibility check flags three frequency bands as "will cause significant cancellation in mono playback."
Diagnostic Readings
How to Fix It
Insert a mid-side EQ on the master bus and apply a high-pass filter on the side channel at 150Hz with a 12dB/octave slope. This immediately mono-izes the sub-bass where phase issues are most destructive. On the stereo widening plugin, reduce the width below 80Hz to 0% and taper the widening effect above 8kHz to prevent anti-phase buildup in the high frequencies. Replace the mid-side EQ boost on the side channel with targeted boosts above 500Hz only — below 500Hz, keep the side channel subtle. After these changes, re-run Stereo Field. Phase correlation below 150Hz should read +0.7 or above, SUB width should drop below 30%, and mono compatibility should pass.
A Note on These Scenarios
These are hypothetical scenarios based on common mixing challenges that producers face every day. The diagnostic readings described are what Audit Audio would detect if you loaded your track alongside an appropriate reference. No customer names, no fake testimonials — just the objective data the tool produces. When beta users start submitting real before/after comparisons, we’ll replace these with actual results.
Join the beta and run your own tracks through the full diagnostic suite. Find out what your mix is actually doing — not what you think it’s doing.