Skip to content
Advanced

Mastering and Delivery Verification

Review mix masters, process with an explicit delivery brief, measure loudness and true peak, and verify every encoded release file.

mastering learnersproducers

Workflow

  1. Collect final mixes and delivery specifications

    Confirm the approved mix revision, track order, titles, spacing and required masters. Record each destination’s codec, sample rate, channel layout, loudness and peak requirements where specified. Identify separate releases that need different masters; a platform playback normalization target is not automatically a mandatory mastering target.

  2. Listen and document source problems

    Listen through the source files for clipping, dropouts, edit clicks, unwanted noise and inconsistent tone. Inspect peak and RMS measurements using named conventions. Ask for a revised mix when a source problem cannot be repaired acceptably; retain the original source and a precise issue location.

  3. Make restrained processing decisions

    Compare tonal adjustments, dynamics and limiting with an unprocessed reference at matched level. Use the static compressor model only to inspect its steady-state curve. Recheck the loudest transients and quiet tails after processing rather than assuming a nominal ratio guarantees peak control.

  4. Measure the complete processed program

    Measure integrated loudness and true peak over the required program scope in audio software. Use the loudness-gain mode to compare a constant gain change with the chosen ceiling. If the proposed gain would exceed that ceiling, revise the processing or target, then measure the result again.

  5. Export and audition each delivery format

    Export masters and distribution encodes according to the actual brief, making sample-rate or bit-depth changes deliberately in the audio application. Check the encoded output for overs, artifacts, tags, starts, ends and channel compatibility. Use bitrate or PCM calculations for storage planning and actual bytes for delivery records.

  6. Approve and archive the release package

    Compare the final file list with the approved order and naming scheme, then play every release file. Save final measurements, settings, source revision, release notes and an editable project. Keep a clear distinction between approved masters and earlier review exports.

Tools Used

Checklist

0 / 6 completed

Loading your checklist…

Collect final mixes and delivery specifications

Listen and document source problems

Make restrained processing decisions

Measure the complete processed program

Export and audition each delivery format

Approve and archive the release package

Reference Materials

Destination audio guidanceStandard

Use the actual destination’s published requirements and distinguish its playback normalization behavior from the delivery specification.

Compressor controls and limitsStandard

A static compressor transfer curve describes level mapping; transient and limiter behavior require the real processor.

Mastering release manifestTable

Keep the following evidence with the actual version used for this task.

RecordIncludeCheck
SourceApproved mix and project revisionNo draft mixed into the release
MeasurementProgram scope, meter and loudness/true peakMeasure after final processing
DeliveryCodec, channels, bytes, tags and filenameListen after encoding
  • Measure the final file

    Encoding and sample-rate conversion can change peaks; the pre-export meter is only part of verification.

  • Retain alternatives clearly

    Keep destination variants named so they cannot be confused during upload.