How to Listen Back to a Master (What to Listen For)
Published · updated · by Loopin
Casual listening after mastering misses more than people expect — a structured, specific listening pass catches problems that a single relaxed play-through won't reveal.
Start with the numbers, not your ears
Before subjective listening, check integrated LUFS and true peak against your target — roughly −14 LUFS and −1 dBTP for most streaming release scenarios. This objective check catches technical issues your ears might miss or rationalize away after a long session.
If the numbers are off, address that first — there's little point doing a detailed subjective listen on a file that isn't even hitting its basic technical target yet.
Listen to the loudest and quietest sections specifically
Rather than just playing the track start to finish, deliberately jump to the loudest section and listen for any harshness, distortion, or squashed quality, then jump to the quietest section and check that it still feels intentional and present, not buried.
These two extremes reveal more about mastering quality than the middle of the track usually does, since that's where processing decisions are most stress-tested.
Check each frequency range deliberately
Rather than listening generally, consciously direct attention to low end (is it controlled and appropriately weighted), midrange (is the vocal or lead clear), and top end (is there harshness or, alternatively, is it missing air). This deliberate, sectioned listening catches issues a general pass misses.
This takes more focus than casual listening, but it's a skill that improves with practice and becomes faster and more automatic over time.
Listen on more than one system, in the same session
Play the master on headphones, then a phone speaker, then ideally a third system if available, within the same listening session rather than spread across different days. This lets you directly compare how it translates rather than relying on memory across sessions.
If something sounds noticeably wrong on one system but fine on others, that's worth investigating specifically rather than dismissing as "just how that system sounds."
Take a break before the final decision
After a mastering session, your ears are fatigued and calibrated to whatever you've been listening to repeatedly — step away for at least a few minutes, ideally longer, before doing your final listening pass and calling the master finished.
A master that still sounds right after this break, with genuinely fresh ears, is a more reliable signal than one judged immediately at the end of a long working session.
Frequently asked questions
What should I check first when listening back to a finished master?
Objective numbers first -- integrated LUFS and true peak against your target. This catches technical issues before subjective listening, and there's little point doing a detailed listen on a file that isn't hitting its basic target yet.
Should I listen to the whole track or specific sections when evaluating a master?
Both, but deliberately check the loudest and quietest sections specifically -- they reveal more about mastering quality than the middle of a track usually does, since that's where processing decisions are most stress-tested.
Why does taking a break before the final listen matter?
Your ears get fatigued and calibrated to whatever you've been listening to repeatedly during a mastering session. A master that still sounds right after stepping away for a few minutes is a more reliable signal than an immediate judgment.