Insights · Deliverables

What Producers Should Know About Final Mix Deliverables

The mix may be approved, but the job is not finished until the correct files reach the correct destination in the correct format. This is the part where a simple soundtrack occasionally turns into a small family of WAV files.

← ALL INSIGHTS

Audio deliverables vary by platform, broadcaster, distributor and project type. The safest approach is always to obtain the destination’s technical specification before final delivery rather than guessing what they probably want.

Still, there are several deliverable types producers encounter repeatedly.

The Full Mix

The full mix is the finished soundtrack containing dialogue, music and effects together. For many web and internal projects, this may be the primary audio master.

There can be more than one full mix if the project requires different destinations or channel layouts—for example, a broadcast version and a web version.

Stems

Stems are separate submixes of major soundtrack elements. The most common are:

  • DX: dialogue
  • MX: music
  • FX: sound effects and backgrounds

When played together at unity, the stems should reconstruct the approved full mix. They are useful for localization, revisions, alternate versions and downstream distribution.

Depending on the project, stems may be divided further—for example, separating VO from production dialogue or backgrounds from hard effects.

M&E

An M&E, or Music & Effects track, is typically used for international versions. It removes language-dependent dialogue while retaining music, effects and other appropriate non-dialogue material so another language can be added later.

Creating a proper M&E can involve more than simply muting the dialogue stem. Production dialogue tracks may contain footsteps, prop sounds, breaths or other useful material that must be rebuilt or replaced.

Alternate Versions and Cutdowns

Advertising and branded-content projects often require multiple durations, aspect-ratio versions or end cards. Every editorial version may need its own approved audio master.

A :30 and a :15 are not simply the same mix exported twice. Timing, music structure, sound effects and transitions may all need to be adjusted so the shorter version still feels intentional.

Loudness and Peak Requirements

Broadcast and distribution platforms may specify integrated loudness, dialogue loudness, true peak limits, channel layouts or other technical requirements. Those specifications vary, so the destination should determine the target.

This is why “make it as loud as possible” is not a delivery specification. It is more of a cry for help.

Producer takeaway: Ask for the delivery specification before the final mix whenever possible. The correct target depends on where the project is going, not on a universal number that applies everywhere.

Sample Rate and Bit Depth

Professional picture workflows commonly use 48 kHz audio, with 24-bit files frequently requested for masters. Specific requirements can vary, particularly for theatrical, broadcast or archival delivery, so follow the destination spec.

File Start, Timecode and Sync

Long-form deliverables may need to begin at a specified timecode and maintain exact sync with picture. Stems and full mixes should share the same start point and duration unless the spec says otherwise.

That consistency becomes especially important when the files move to online, localization, mastering or distribution teams.

File Naming Matters More Than It Seems

A clear naming convention should identify the project, version, duration, mix type and possibly date or revision. For example, a producer should be able to tell the difference between the full mix, dialogue stem and M&E without opening each file.

“FINAL.wav” is optimistic. “FINAL_USE_THIS_v3.wav” is emotionally honest but operationally less useful.

QC Before Delivery

Final files should be checked after export. QC typically includes confirming sync, duration, channel layout, loudness/peak compliance, clean heads and tails, correct fades, file names and the absence of glitches or missing elements.

If multiple versions are required, each version deserves its own check. The fact that the :30 passed QC does not guarantee the :06 social cutdown did.

What Producers Should Request Up Front

  • Destination or distributor specification
  • Required channel format
  • Full-mix requirements
  • Stem list
  • M&E requirements, if applicable
  • Alternate durations and versions
  • File naming convention
  • Required start time/timecode
  • Delivery deadline and transfer method

Deliverables are much easier when they are planned before the mix is finished. A five-minute conversation early in post can prevent an impressive amount of exporting later.

Related Service

Need Help With the Audio, Not Just the Checklist?

FINAL MIX
START A PROJECT