Spatial audio for independent artists

Dolby Atmos Music Mixing and Delivery Requirements

Bradley J Simons
Bradley J Simons
4x Juno-nominated producer · founder of Velveteen
The short answer

For Apple, create Dolby Atmos from multitracks or multitrack-derived stems, never a stereo upmix or de-mix. Approve and conform the immersive mix, then export BWF ADM with 24-bit 48 kHz LPCM, consistent frame rate, integrated loudness no higher than -18 LKFS, true peak no higher than -1 dB TP, valid LFE, timing, metadata, checksum, and the provider's immersive ISRC workflow.

Lead visual

Streaming master readout

Loudness meter

Integrated LUFS

-14target

True peak

-1dBTP

Bit depth

24bit

Waveform after normalization

dynamiccodec-safestreaming-ready
A meter-style image showing the practical mastering targets before exporting a streaming master.

Audio · Spatial

Playback spec map

Decision

Master for translation, not just for maximum loudness.

Evidence

LUFS, true peak, file format, headroom, codec behavior, and the final exported master.

Risk

A master that feels exciting in the room can distort, turn down, or lose impact after delivery.

Good outcome

A master that survives platform normalization and still feels intentional.

Part of the Spatial audio cluster.

Key takeaways

  • Apple requires multitracks or legitimate multitrack-derived stems and rejects stereo upmixes and de-mixes.
  • Lock project-wide sample rate, bit depth, frame rate, start, duration, edits, and stereo reference before mixing.
  • Validate BWF ADM, 24-bit 48 kHz, current loudness and peak ceilings, LFE, metadata, identifiers, and checksum.
  • Keep creative approval, technical QC, provider acceptance, and public playback as separate gates.
  • Archive the editable session and evidence, not only the final ADM file.

Which fields must pass before an Atmos master is delivered?

Atmos master specification

Fifteen controls from authority to public playback

authority

Recording rights, samples, contributors, catalogue approval, territories, credits, signer, and source access

Prevents an immersive derivative from exceeding actual authority.

source

Original multitracks or stems created from multitracks, never a stereo upmix or stereo de-mix

Meets Apple's current source boundary and preserves real mix control.

version

Artist, title, edit, clean or explicit state, stereo reference, release, UPC, dates, and approvals agree

Stops the immersive asset joining a different recording version.

session

Supported DAW and renderer, sample rate, bit depth, frame rate, tempo, start, routing, plug-ins, backup, and notes

Makes the creative master reproducible and revisable.

intent

Perspective, anchors, focus, beds, objects, movement, height, width, depth, ambience, LFE, and prohibited effects

Keeps technical capability subordinate to the song.

monitoring

Room or headphone profile, calibration where applicable, binaural, speaker, stereo, consumer, bass, vocal, and fatigue checks

Avoids approving one render as universal translation.

container

Broadcast Wave Format Audio Definition Model file with the exact approved master

Provides the current Apple immersive music delivery container.

audio

All audio is 24-bit LPCM at 48 kHz

Meets Apple's current immersive source resolution.

frame_rate

One documented frame rate across the project and provider-required timecode

Prevents timing mismatch, rejection, or album inconsistency.

conformance

Structure, start, end, silence, and duration match stereo within 50 milliseconds; gapless boundaries meet tighter rules

Keeps alternate playback versions aligned.

loudness

Integrated result does not exceed -18 LKFS under ITU-R BS.1770-4

Treats the value as a delivery ceiling rather than an exact creative target.

true_peak

True peak does not exceed -1 dB TP under ITU-R BS.1770-4

Meets the current receiving ceiling and reduces encoded overs.

lfe

No full-frequency content in LFE and intended low-frequency behavior translates

Prevents incorrect bass routing and receiving failure.

identity

Stereo ISRC, required immersive ISRC path, assignment record, UPC, provider ID, artist mapping, and credits

Separates recording identity from ownership and prevents linkage errors.

evidence

ADM checksum, QC report, approvals, payload, fee, acknowledgement, rejection, correction, badge, and public playback check

Makes every handoff and closure traceable.

What is the safest Atmos mixing and delivery sequence?

Atmos production runbook

Ten gates before the project is closed

  1. 01

    Gate 1

    Intake

    Resolve authority, project scope, sources, versions, credits, deadlines, provider, destinations, approvals, budget, and stop conditions.

  2. 02

    Gate 2

    Prepare

    Clean and consolidate multitracks, preserve effects and automation decisions, lock edits, stereo reference, timing, naming, and checksums.

  3. 03

    Gate 3

    Configure

    Set DAW, renderer, bed and object routing, sample rate, frame rate, monitoring, plug-ins, backups, and version labels.

  4. 04

    Gate 4

    Mix

    Establish anchors and listener perspective, then make deliberate depth, height, width, movement, ambience, and LFE decisions.

  5. 05

    Gate 5

    Translate

    Review binaural, headphones, speakers where available, stereo fallback, vocal, bass, transients, reverbs, motion, and listener fatigue.

  6. 06

    Gate 6

    Conform

    Match final stereo structure, start, end, duration, silence, clean or explicit state, and intended gapless boundaries.

  7. 07

    Gate 7

    Export

    Create the approved BWF ADM and contracted renders with named versions, checksums, notes, identifiers, credits, and archive.

  8. 08

    Gate 8

    Validate

    Open the master in supported tools and check container, audio, frame rate, loudness, peak, LFE, objects, beds, metadata, timing, and integrity.

  9. 09

    Gate 9

    Deliver

    Submit stereo and immersive assets through the verified provider path and preserve payload, fee, acknowledgement, rejection, and fixes.

  10. 10

    Gate 10

    Public QC

    Check correct attachment, badge, territory, tier, device, playback setting, stereo fallback, level, start, end, translation, and recurrence.

Provider acceptance is not the final QC step

The file can pass upload checks and still attach to the wrong track, appear only in some territories or tiers, fall back to stereo, or reveal translation problems. Close only after a named public playback matrix is complete.

lock version identity and delivery evidence

Which sources define Atmos master and Apple delivery requirements?

Frequently asked questions

What are Apple's current Dolby Atmos music file requirements?+

Apple currently requires a BWF ADM file made from multitracks or multitrack-derived stems, with 24-bit LPCM audio at 48 kHz and one consistent frame rate across the project. The immersive file must conform to the stereo reference. Integrated loudness should not exceed -18 LKFS and true peak should not exceed -1 dB TP under ITU-R BS.1770-4, with no full-frequency content in LFE.

How closely must Dolby Atmos match the stereo master?+

Apple says the most recently delivered stereo and immersive durations must differ by no more than 50 milliseconds. They should represent the same track structure, edits, version, clean or explicit state, start, end, and intended gapless boundaries. This does not mean their spatial balance or creative mix is identical. Conform against named final files and preserve a duration, boundary, silence, and checksum report.

Is -18 LKFS an exact Dolby Atmos mastering target?+

No. Apple's current language says integrated loudness should not exceed -18 LKFS and true peak should not exceed -1 dB TP, measured under ITU-R BS.1770-4. Treat those values as receiving ceilings, not a command to force every song to exactly -18. The mix still needs musical dynamics, translation, focal clarity, bass control, and consistency with the approved creative intent.

What should be included in a Dolby Atmos master archive?+

Keep the DAW session, renderer version and settings, I/O map, beds and objects, automation, plug-in versions, multitracks or stems, tempo and frame references, stereo reference, binaural and speaker renders where contracted, ADM BWF, checksums, loudness and peak report, LFE and duration checks, identifiers, credits, approvals, distributor payload, acknowledgement, correction history, and public-service verification.

How do I quality-check a Dolby Atmos music release?+

Verify source authority and exact version, then review creative translation on the project's named monitoring paths. Validate ADM structure, 24-bit 48 kHz audio, frame rate, objects and beds, loudness, true peak, LFE, start, end, duration, gapless boundaries, metadata, checksum, and immersive ISRC. After provider acceptance, inspect the correct public track, territory, tier, device, playback setting, stereo fallback, badge, level, timing, and sound.

Bradley J Simons

About the author

Bradley J Simons

Bradley J Simons is a 4x Juno-nominated producer who makes music as Babbage and founded Velveteen. A former touring musician, he writes about releasing, pitching, and getting paid for music from the artist's side of the desk.

Velveteen notes

Get better release strategy in your inbox

Release planning checklists, royalty explainers, and artist strategy notes from Velveteen. No daily noise.

Improve this page

Was this useful? Send a signal or flag a correction.

Keep reading

Free tool · no signup

Check your metadata before your distributor does

Run your titles, credits, copyright lines, and ISRC and UPC codes through the free checker and catch the rejection-bait errors before you upload. It all runs in your browser.