Example analyzer reports
Three realistic examples showcasing how the analyzer responds to different mix quality levels: from release-ready (top) through iterative refinement to early-stage work.
Neon Horizons
A mix that's finished and ready to move forward. The analyzer shows confidence across all metrics, with only optional finishing touches suggested.
The quickest read on whether this bounce feels finished enough to protect in the next revision.
How safely this version should survive normalization, codec conversion, and smaller playback chains.
Whether the lead idea stays legible once the arrangement and playback system both get less forgiving.
The reference-aware read positions the bounce in context instead of leaving it as a disconnected measurement.
The overall read already feels close to release-ready, not like an early rough bounce.
Streaming translation looks controlled enough that normalization should not immediately expose a major weakness.
The lead idea is staying readable even when the arrangement gets denser.
This mix is in excellent shape and ready for delivery.
Minor optional: consider a touch more presence in the 3-4k range if seeking maximum vocal clarity on consumer earbuds, but current state translates safely across all platforms.
Kick and bass are well-separated with excellent mono compatibility. Low-end translation will remain solid across playback systems.
Start with this: This mix is in excellent shape and ready for delivery. Then export one new bounce and compare it against this version.
Your mix sits in the upper range of approved references, showing strong competitive loudness without aggressive limiting artifacts.
Compare this export to the previous version
Run one more bounce to unlock version-to-version movement instead of relying on ear fatigue alone.
Digital Dreams
A mix with a clear path to release. The analyzer identifies two specific issues (peak ceiling and midrange masking) that, when addressed, will lift the quality into competitive territory.
The quickest read on whether this bounce feels finished enough to protect in the next revision.
How safely this version should survive normalization, codec conversion, and smaller playback chains.
Whether the lead idea stays legible once the arrangement and playback system both get less forgiving.
The reference-aware read positions the bounce in context instead of leaving it as a disconnected measurement.
The bounce has a stable enough baseline to compare against the next revision instead of guessing from memory.
True peak is slightly over safe margin—lower limiter ceiling to -1.0 dBTP.
The 200-400 Hz is masking the midrange; try a -2dB notch at 280 Hz.
Clarity will lift 4-6 points once these two issues are addressed.
Start with this: True peak is slightly over safe margin—lower limiter ceiling to -1.0 dBTP. Then export one new bounce and compare it against this version.
Loudness is mid-range within the reference bucket, leaving room to add 1.5-2 dB before hitting competitive ceiling.
Compare this export to the previous version
Run one more bounce to unlock version-to-version movement instead of relying on ear fatigue alone.
Ambient Sketch
An early-stage mix showing what the analyzer surfaces when foundational work is still needed. All metrics are clearly lower, and the improvement suggestions focus on the three highest-impact fixes to prioritize.
The quickest read on whether this bounce feels finished enough to protect in the next revision.
How safely this version should survive normalization, codec conversion, and smaller playback chains.
Whether the lead idea stays legible once the arrangement and playback system both get less forgiving.
The reference-aware read positions the bounce in context instead of leaving it as a disconnected measurement.
The bounce has a stable enough baseline to compare against the next revision instead of guessing from memory.
This mix needs foundational work before mastering consideration.
Critical: True peak is clipping above safety zone (1.2 dBTP)—apply limiter at -1.0 dBTP immediately.
Second priority: Clarity is very low due to excessive reverb masking (too much 300-1k range); reduce room ambience and add EQ focus on lead elements.
Start with this: This mix needs foundational work before mastering consideration. Then export one new bounce and compare it against this version.
The mix is substantially quieter than reference profiles, suggesting either mixing technique drift or inadequate compression. Both factors should be reviewed.
Compare this export to the previous version
Run one more bounce to unlock version-to-version movement instead of relying on ear fatigue alone.
What these examples show
The analyzer adapts its language, focus, and urgency based on actual mix condition. Customers see not just numbers, but actionable next steps—whether they're at the finish line or in the early sketching phase.
The product delivers different insights based on the mix maturity: release polish for finished work, prioritized fixes for in-progress, and foundational guidance for early drafts.
Reference percentiles and genre confidence levels help users understand not just what to fix, but how much to trust the advice in their specific production context.
Whether it's a release-ready sign-off or a three-step corrective path, the output is always focused on what the user can do next, not what they did wrong.
.png&w=3840&q=75)