Tonal Auto-Correction (Beta) and Honest A/B Comparison
We studied how the market leaders (iZotope Ozone, LANDR, eMastered, BandLab, Masterchannel, RoEx) handle automatic tonal-balance correction — and shipped two features based on what we learned. Both are built around one principle: your sound changes only with your consent, and you always see exactly what changed.
Tonal auto-correction — beta, strictly opt-in
Science has long described the "reference spectrum" of commercial releases (Pestana/Reiss and Elowsson's AES research across hundreds of chart hits). Our analyzer already compares your track against that curve and shows deviations in the passport. Now there's correction too — built carefully:
- half of the deviation is corrected, not all of it: your track's character matters more than formally hitting the curve;
- at most ±1.5 dB per zone — delicate shelf and bell filters;
- only by your choice: a BETA·PRO toggle in the settings, off by default;
- the passport stays honest: it shows the reference-match metric before and after correction.
Why not "always on"? The research was clear: engineers call full spectrum-matching an anti-pattern ("a starting point, not a recipe"), and "over-brightened" sound is the #1 complaint about auto-mastering. Ozone — the industry benchmark — gives you a strength slider; we took the same deliberate-choice path.
Honest A/B: "= loudness"
The oldest trick in audio: make it louder and it sounds better. In a before/after comparison the master is always louder than the original, so such an A/B says nothing honest about the processing character.
The A/B player now matches loudness by LUFS: the "= loudness" checkbox (on by default) attenuates the louder version down to the quieter one. You hear the difference in density, balance and space — not a trivial "it's louder". Want the old behavior — one click removes the checkbox.
We trust our processing enough to let you compare it honestly.
For developers
POST /api/v2/master accepts tonal_autocorrect=true; the job status returns a tonal_autocorrect block with before/after metrics. Docs: magicmaster.pro/developers.
Try it: magicmaster.pro/app?lang=en — 1 free basic mastering per UTC day.
Questions and answers
What does tonal auto-correction do?
It gently pulls your track's spectral balance toward a data-derived reference curve of commercial releases (based on AES research): half of the deviation is corrected, at most ±1.5 dB per zone. It's a delicate adjustment, not a 'repaint' of your track.
Why is it off by default?
We researched the market: every leader (Ozone, LANDR, eMastered) does curve-based correction, but professionals are unanimous — full matching without a control knob erases a track's character and is the #1 complaint about auto-mastering. So with us it's the user's deliberate choice: switch it on — it applies, and the passport shows the before/after metric.
What is loudness-matched A/B?
Psychoacoustics: 'louder' almost always reads as 'better', even at worse quality. Our A/B player now matches the loudness of the original and the master by LUFS (the '= loudness' checkbox, on by default) — you compare the character of the processing, not the level.
How do I enable auto-correction?
The 'Tonal auto-correction BETA·PRO' toggle in the mastering settings. Also via API: tonal_autocorrect=true in POST /api/v2/master. The applied correction is reported in the track passport.
Upload a track — a finished master in seconds.
Open mastering →AI mastering onlineLUFS analyzer