Start with a fresh-ear reset
The first evaluation tool is silence. If you judge a bounce immediately after four hours of looped chorus work, you are mostly judging ear fatigue. Take a break, then play the full song once without touching the mouse. Write down what pulls attention away from the song: buried vocal, harsh snare, unstable bass, dull chorus, weak kick, too much reverb, or no lift into the hook.
That first pass matters because it tells you what a listener will notice before they know anything about your session. After that, you can move into technical checks.
The six-pass pre-master evaluation
| Pass | Question | Fix in mix if... |
|---|---|---|
| Low volume | Does the song still communicate? | The vocal, hook, snare, or bass disappears. |
| Mono | Does the center hold? | Kick, bass, vocal, snare, or lead elements thin out. |
| Reference | Is the tonal target realistic? | Your mix is much darker, boomier, harsher, or flatter at matched loudness. |
| Dynamics | Does the groove still move? | The limiter is already doing the emotional work. |
| True peak and clipping | Is the bounce clean? | Peaks clip, inter-sample risk is high, or the waveform is visibly flattened. |
| Export | Can another engineer trust the file? | The file is lossy, normalized, mislabeled, or processed by accident. |
1. Low-volume balance
Turn the monitors down until you can talk over the track. The lead idea should still read. You should still feel the groove. The vocal does not need to be loud, but it should not vanish. Low-volume listening strips away excitement and reveals hierarchy.
If the chorus only works loud, the mix is probably relying on level rather than balance. Fix that before mastering. A mastering engineer can raise the whole track, but they cannot make a hidden hook important without affecting everything around it.
2. Mono compatibility
Fold the mix to mono and listen for losses, not perfection. Wide reverbs can shrink. Background pads can move. The core should stay alive: kick, bass, lead vocal, snare, and the main musical hook. If any core element disappears, the mix has a phase or arrangement problem.
Use Mix Analyzer stereo feedback as a second view. A low correlation flag does not automatically mean the mix is bad, but it does mean you should check which element is driving the sides. Wide low end is the first suspect. Chorus wideners, Haas delays, stereo synth patches, and reverb returns are next.
3. Level-matched reference check
A reference track is useful only after loudness matching. A mastered reference will usually be louder than your pre-master bounce, and louder will feel clearer, wider, and more finished even when it is not a fair comparison. Pull the reference down until the sections feel equally loud, then compare one trait at a time.
- Tone: is your mix heavier in the lows, cloudier in the low mids, or duller above 10 kHz?
- Punch: does the kick and snare movement survive at the same loudness?
- Vocal position: is the lead too forward, too buried, or too masked?
- Width: is the chorus wide because it has contrast, or because everything is pushed to the sides?
4. Dynamics and headroom
Headroom is not magic. It is simply space before the ceiling. The real question is whether the mix still has punch and clean peaks before mastering. If a limiter on the mix bus is reducing several dB because the bounce otherwise falls apart, print a limited reference for yourself but send the clean version for mastering.
Spotify and Apple guidance both point toward avoiding clipping and protecting true peak during delivery. That does not mean your premaster should chase the final platform loudness. The premaster should preserve the dynamics the mastering stage will shape.
5. Artifact and edit check
Listen to the start, end, dropouts, vocal edits, reverb tails, and transition points. Clicks and pops often hide under the full arrangement and become obvious after limiting. Noise floor and hum also become more annoying once the master raises quiet details. If Mix Analyzer flags noise or source quality issues, verify them before sending the file.
6. Export settings
Send a lossless stereo file. WAV or AIFF is the normal delivery. Use the project sample rate. Use 24-bit or 32-bit float if your workflow supports it. Do not normalize. Do not dither unless you are creating the final fixed-bit-depth delivery yourself. Label the file so the receiving engineer knows version, sample rate, bit depth, and limiter status.
A practical filename looks like Artist_Song_Mix03_48k_24bit_NoLimiter.wav. That small discipline prevents wrong-file mistakes during revisions.
Use the report as evidence, not a command list
After the listening passes, run the bounce through Mix Analyzer. Start with issues that repeat across your notes and the report. If you heard muddy low mids and the spectrum flags low-mid buildup, fix that first. If the report flags a small issue you cannot hear in context, park it. The goal is release confidence, not a perfect score.
A pre-master scorecard you can reuse
Use a scorecard when you are too close to the session. Give each area a simple pass, fix, or intentional label. Pass means the mix works and needs no action. Fix means the issue is audible and should be handled before mastering. Intentional means the choice is risky but deliberate, and you should tell the mastering engineer about it.
| Area | Pass | Fix | Intentional |
|---|---|---|---|
| Vocal or lead | Readable at low volume | Disappears, jumps, or masks | Buried vocal is part of the production |
| Low end | Kick and bass roles are clear | Sub eats headroom or bass vanishes | Club-first low end, with notes |
| Dynamics | Groove moves without heavy limiting | Flat, clipped, or over-compressed | Aggressive crushed sound is the target |
| Stereo | Center survives mono | Hook, bass, or vocal collapses | Wide effect is decorative, not core |
| Export | Lossless, labeled, no accidents | Wrong version, lossy file, clipped render | Printed processing is part of the sound |
Red flags that mean stop and reopen the session
Some problems should not go to mastering at all. Stop if the vocal balance changes wildly between sections, if the low end only works on one playback system, if mono removes the hook, if the mix bus limiter is saving the groove, or if you cannot tell which file is the latest version. These are not mastering preferences. They are production control problems.
The fastest recovery is to make one repair and export again. Do not start a full remix unless the song needs it. If the chorus vocal is 1 dB low, automate the chorus. If the bass vanishes on small speakers, add harmonic support or adjust the relationship with the kick. If the side channel carries too much of the hook, move some of that information back toward the center.
What notes to include with the mastering delivery
Good notes reduce revision loops. Keep them short and useful. Name the target, the references, the version, and any intentional risks. A mastering engineer does not need your whole mix history. They need to know what you are protecting and what you want improved.
- Target: streaming single, EP track, club master, sync cue, demo, or album sequence.
- References: one or two songs and what each reference represents: low end, vocal, brightness, punch, or space.
- Known risks: distorted vocal, noisy sample, wide bass, dark top end, heavy drum clipping, or printed mix-bus color.
- Versions: which file is the clean premaster and which file is the loud reference.
- Do not change: any creative choice that could look like a mistake from the outside.
Why this evaluation pays for itself
Mastering revisions cost time because they happen after the easiest fixes are no longer available. A 30 minute evaluation before delivery can prevent a full back-and-forth later. It also makes the conversation with a mastering engineer sharper. Instead of saying "make it sound professional," you can say "the mix is translating well, but I want the master to preserve the chorus punch and keep the top end smooth."
That level of clarity changes the result. It tells the engineer what success means and keeps the master from compensating for problems you could have fixed in the session.
Keep a decision log for the final two bounces
Write three lines beside each export: what changed, why it changed, and what you expect to hear. This prevents circular revisions. If Mix04 has less 250 Hz in the piano, the note should say whether you expected more vocal clarity, less mud, or both. When you compare Mix04 to Mix03, you can judge the actual decision instead of reacting to the whole song again.
FAQ
What should I check before sending a mix to mastering?
Check low-volume balance, mono compatibility, level-matched references, dynamics, true peak, clipping, noise, and export settings.
Should I leave a limiter on the mix bus?
If the limiter is part of the sound, send a clear limited reference and an unlimited premaster. Do not force the mastering engineer to work from a crushed file unless that is the final creative choice.
What is a good peak level before mastering?
A common practical range is around -6 to -3 dBFS peaks, but the important part is no clipping, no unnecessary limiting, and enough dynamics for mastering to work.
Can I send an MP3 for mastering?
No. Send a lossless WAV or AIFF. MP3 and AAC are useful for reference listening, not as source files for mastering.