The file that came out different
Your master is done. You spent two evenings on it, the mix was right and the final listen left you feeling calm. You export, you upload, and three weeks later you play the track back on your phone. It sounds duller than what was in your session, the fade-out has an edge of noise you do not recognize, and the file you sent to a label turns out to be at 44.1 kHz while your whole project ran at 48 kHz. None of that is a matter of taste. These are four decisions that sat in the export window and that you made on autopilot.
Mastering is not just processing a sum. It is also the point where music becomes a file, and that file travels without you.
What you will learn in this chapter
- You build a mastering chain as an order of problems, not as a row of plug-ins you copy from someone else.
- You know when stereo mastering is enough, when stems genuinely add something and where the boundary with mixing lies.
- You understand what dither solves, when it applies and why once is enough.
- You deliberately hold on to sample rate and bit depth instead of letting each export choose them again.
- You organize your master with the variants you will need later: instrumental, clean version and alternative lengths.
- You set up a delivery folder that lets someone else release your track without having to ask you anything.
Who this chapter is for
For anyone who has a finished mix and wants to take it to a master themselves, and just as much for anyone who delivers their music to a mastering engineer, label or distributor and wants to understand what is being asked there. You do not need an expensive chain. A DAW, a finished mix, a loudness meter and a way to compare at equal loudness are enough. The chapter on mastering fundamentals, loudness and true peak is recommended prior knowledge; concepts you are missing can be found in the free intro lessons of the earlier modules.
The core idea in one paragraph
A master is two things at once: a sonic decision and a file. The sonic decision takes shape in a chain that runs from correction to character to control, where every stage solves a problem you can name in one sentence. The file takes shape in a handful of choices about sample rate, bit depth, dither and variants, and there a simple rule applies: change nothing without a reason, and change it only once. In the next lessons you first build the chain, then the delivery form, and finally the archive that keeps your track releasable five years from now.