Lossy encoding can create clipping that was absent from a clean PCM master, so the encoded derivative requires its own inspection. A session that played perfectly is not proof that the file you will upload is intact. The render may contain the wrong range, a muted channel, an unintended bus, clipped reconstruction peaks, or a damaged tail.
Even a self-mastering workflow that protects the finished mix remains unfinished until the exported asset passes quality control. Treat the file on disk as the product. Your open project is only the machine that made it.
That distinction changes the job. You are no longer choosing tone or dynamics. You are proving that the approved sound survived export and that the resulting file matches its intended delivery specification.
Start with identity. Confirm the filename and version, then inspect the file type, sample rate, bit depth, channel count, and duration. These are not clerical details. A stereo song accidentally rendered as mono, a truncated bounce range, or an older revision carrying a newer name can pass a casual listening test and still become the wrong release asset.
Look at the beginning and end at high waveform magnification. The opening should contain the intended amount of silence without a clipped first transient. The final decay should end naturally, followed by deliberate clearance rather than a hard cut or several unexplained seconds. Do not redraw fades during quality control. If the boundaries are wrong, correct the source and render again.
Play the imported file through the same hardware path used for approval, with no new gain changes. Compare its duration and channel orientation with your notes from the approved session. If the left and right channels have swapped, the center has shifted, or the file starts late, stop. Meter readings cannot rescue a structurally wrong asset.
Resist fixing anything during that pass. Rewinding after every suspicion breaks concentration and encourages you to judge the session again instead of the render. Note the location, finish the song, then revisit each timestamp with headphones and monitors. A noise that repeats on both systems at the same sample position strongly implicates the file rather than the room.
The second pass is technical. Analyze the imported asset, not a live output from the original project. Verify that its integrated loudness and true peak match the approved values within the meter's expected tolerance. Check left and right balance, polarity or phase correlation, digital silence where silence is intended, and the absence of sample or inter-sample clipping.
Measurements need interpretation. A channel imbalance may be a deliberate part of the arrangement, while one isolated peak does not describe the song's loudness. Compare every warning with the audible material and the approval notes. Quality control should detect a changed file, not reopen creative decisions that were already settled.
Match playback level before comparing the encoded copy with the lossless master. Listen closely to cymbal decays, exposed vocals, stereo ambience, and sharp attacks, but keep the lossless file as the delivery source unless a service explicitly requests otherwise. The compressed version is an audition of a likely playback path, not a replacement master.
Finally, play the exact file after copying it to the upload or handoff location. Confirm that it opens, runs for the recorded duration, and carries the same format and version name you approved. Archive that file with a simple QC log containing the listening date, measured properties, and any encoded checks performed. Every new render creates a new asset, so even a one-second repair resets the complete listening and verification process.
Even a self-mastering workflow that protects the finished mix remains unfinished until the exported asset passes quality control. Treat the file on disk as the product. Your open project is only the machine that made it.
That distinction changes the job. You are no longer choosing tone or dynamics. You are proving that the approved sound survived export and that the resulting file matches its intended delivery specification.
The exported file becomes the only truth
Close the mastering session before checking the final render. Open a blank project, disable every processing slot on its output, and import the exported file from its actual delivery folder. This clean path prevents a monitor plugin, master fader, sample-rate conversion setting, or forgotten limiter from coloring the check.Start with identity. Confirm the filename and version, then inspect the file type, sample rate, bit depth, channel count, and duration. These are not clerical details. A stereo song accidentally rendered as mono, a truncated bounce range, or an older revision carrying a newer name can pass a casual listening test and still become the wrong release asset.
Look at the beginning and end at high waveform magnification. The opening should contain the intended amount of silence without a clipped first transient. The final decay should end naturally, followed by deliberate clearance rather than a hard cut or several unexplained seconds. Do not redraw fades during quality control. If the boundaries are wrong, correct the source and render again.
Play the imported file through the same hardware path used for approval, with no new gain changes. Compare its duration and channel orientation with your notes from the approved session. If the left and right channels have swapped, the center has shifted, or the file starts late, stop. Meter readings cannot rescue a structurally wrong asset.
One pass listens while another verifies
A reliable check separates attention into a two-pass master inspection. During the first pass, play the whole file at a comfortable fixed level without touching the timeline. Keep a paper or text log and mark times for clicks, pops, dropouts, brief distortion, unexpected silence, rough edits, mouth noise, or a tail that collapses early. Continuous listening preserves musical context and catches the isolated failure that skipping between loud sections can miss.Resist fixing anything during that pass. Rewinding after every suspicion breaks concentration and encourages you to judge the session again instead of the render. Note the location, finish the song, then revisit each timestamp with headphones and monitors. A noise that repeats on both systems at the same sample position strongly implicates the file rather than the room.
The second pass is technical. Analyze the imported asset, not a live output from the original project. Verify that its integrated loudness and true peak match the approved values within the meter's expected tolerance. Check left and right balance, polarity or phase correlation, digital silence where silence is intended, and the absence of sample or inter-sample clipping.
Measurements need interpretation. A channel imbalance may be a deliberate part of the arrangement, while one isolated peak does not describe the song's loudness. Compare every warning with the audible material and the approval notes. Quality control should detect a changed file, not reopen creative decisions that were already settled.
Encoded copies expose a different class of failure
Create an AAC or MP3 audition from the approved lossless file, never from another compressed copy. Then inspect that encoded result separately. Encoding can raise reconstructed peaks beyond the PCM file's measured ceiling, and dense transients or sharp sibilance may reveal artifacts that the lossless playback did not contain.Match playback level before comparing the encoded copy with the lossless master. Listen closely to cymbal decays, exposed vocals, stereo ambience, and sharp attacks, but keep the lossless file as the delivery source unless a service explicitly requests otherwise. The compressed version is an audition of a likely playback path, not a replacement master.
Finally, play the exact file after copying it to the upload or handoff location. Confirm that it opens, runs for the recorded duration, and carries the same format and version name you approved. Archive that file with a simple QC log containing the listening date, measured properties, and any encoded checks performed. Every new render creates a new asset, so even a one-second repair resets the complete listening and verification process.