What is a mix review?
Last updated 6 min readTags:MixingFundamentals
What a mix review checks, how to run one step by step, and where measurements help before you approve a mix for mastering.
A mix review is a check of a track’s balance, dynamics, stereo image and technical condition before you approve the mix. It combines listening with measurements to identify problems worth fixing in the session.
The aim is to decide what still needs attention. Does the vocal remain clear in the chorus? Does the bass lose weight in mono? Is the exported file free from unwanted distortion?
You can review your own mix, ask another engineer for feedback, or use analysis software alongside your listening.
Mix review and mastering
A review identifies changes to consider. Mastering processes an approved mix and prepares it for release.
Some problems are easier to address while you still have access to the individual tracks. If a guitar masks the vocal, you can adjust that guitar without changing everything else in the same frequency range. A mastering engineer has less control over those relationships in a stereo file.
Review the mix before mastering, and repeat the relevant checks after substantial revisions.
How to review a mix
1. Take a break and choose a reference
Return after a break, preferably the following day if time permits. Familiarity and listening fatigue can make problems harder to notice.
Choose one or two reference tracks with a similar arrangement and intended sound. Compare equivalent passages, such as a full chorus against a full chorus.
Turn the reference down to roughly the same perceived loudness as your mix. A loudness meter or matching plugin can provide a starting point; check the match by ear. Do not limit your mix just to match the reference’s level.
2. Listen to the musical balance
Play the whole track without making adjustments. Check whether the important parts remain audible and the sections develop as intended.
- Can you follow the lead vocal or melody throughout?
- Do the kick and bass remain distinct when they play together?
- Does the chorus have the intended impact?
- Do any notes, fills or effects distract from the main part?
Try a quieter listening level too. If the vocal disappears, or one instrument dominates, note the passage for closer inspection.
3. Check the tonal balance
Compare the bass, midrange and treble with your references. A spectrum analyser can show differences worth investigating, but the curves need not match. Different instruments and arrangements produce different spectra.
Listen for specific problems:
- Indistinct bass: kick and bass notes are difficult to tell apart.
- Crowded low mids: instruments lose definition when the arrangement becomes busy.
- Harsh upper mids or sibilance: certain notes or consonants become uncomfortable at a sensible listening level.
- Excessive sub-bass: deep bass dominates on a capable system or drives heavy compression and limiting.
Frequency ranges are clues, not diagnoses. Extra energy around 200–400 Hz may contribute to muddiness, but it may also give an instrument its body. Check the source before cutting the whole mix.
If bass disappears on small speakers, inspect its audible harmonics and level relative to the other instruments. More sub-bass will not make those speakers reproduce deeper frequencies.
4. Check dynamics and transients
Listen for drum attacks, sustained notes and changes between sections. Does compression support the intended sound, or does the track pump, lose impact or become tiring?
If you suspect a compressor or limiter, compare it with bypass at a similar perceived loudness. The louder version can otherwise seem better simply because of its level.
Meters provide supporting evidence:
- Integrated LUFS describes average loudness over the track.
- Crest factor describes the difference between peak and RMS levels, in decibels.
- Loudness range (LRA) describes variation in loudness over time.
None provides a universal pass mark. A low crest factor can reflect dense, sustained material as well as heavy processing. There is no compulsory LUFS target for a mix awaiting mastering.
5. Check stereo and mono playback
Listen for the intended placement of instruments and any unwanted bias towards one side. Then sum the mix to mono. Some loss of spaciousness is expected; check whether important parts become much quieter, thin out or disappear.
A correlation meter can flag possible cancellation. Sustained negative readings deserve investigation, but a brief dip does not automatically mean the mix is faulty. A full-band reading also cannot tell you exactly what is happening in the bass. Use a band-limited check if you need to inspect that region separately.
Narrow or mono bass is often intentional. Widen it only if the change serves the track and survives the mono check.
6. Check clipping and peak levels
Check levels through the signal chain and inspect the exported file. Unwanted distortion may come from a recording, a plugin or the final output.
If distortion has already been introduced upstream, turning down the master fader will only make it quieter. Correct it at its source where possible.
For a mix awaiting mastering, follow the engineer’s delivery requirements. Peaks around −6 to −3 dBFS are a common practical margin, rather than a compulsory target. Lower gain creates more peak headroom; it does not restore transients lost to compression or clipping.
A true peak meter estimates peaks between stored samples and reports them in dBTP. For a release master, −1 dBTP is a common precaution for lossy encoding. It is not a universal requirement for every mix or delivery format.
7. Test other playback systems
Check the mix on headphones and a familiar consumer system, such as earbuds, a laptop or a small speaker.
Expect each system to sound different. Listen for changes that obscure the music: an inaudible bass line, lost lyrics or an excessively sharp snare. A phone speaker cannot reproduce deep bass, so do not judge sub-bass balance from it.
Investigate problems that recur across systems before making large changes in response to one device.
8. Write specific notes and check the export
Record the location, the sound and the problem:
2:34, second chorus: the bass notes become difficult to follow when the kick enters. Check their levels and overlapping frequencies.
Address the most disruptive issue first. Make one change, compare at matched loudness, then check the passage in context.
After revisions, listen to the exported file from start to finish. Check for clicks, missing audio, cut-off reverb tails and unintended changes to processing. Confirm the requested format and sample rate before delivery.
Where Sonalix fits
Sonalix measures tonal balance, loudness, dynamics and stereo characteristics, then suggests issues to check and changes to try.
Use the report to direct your listening. A measurement can flag unusually strong low-mid energy, but you must establish whether it sounds muddy and which instrument needs attention. A suggestion is something to test in the session, rather than an instruction to apply regardless of what you hear.
A mix is ready to approve when its balance and character serve the track, unwanted technical faults have been addressed, and the export meets the intended delivery requirements.
Related articles
Related pages
Was this page helpful?