Understanding ADM and BWF Format for Dolby Atmos Delivery

ADM BWF is not simply a multichannel WAV with extra labels. It carries the bed audio, object audio and metadata needed to reconstruct a Dolby Atmos presentation, so a valid export must preserve both the sound and the renderer state that describes it.

A dependable handoff begins before export: lock the frame rate, sample rate, programme start, bed configuration and object assignments against the delivery specification. Last-minute routing changes are the fastest way to create an ADM that opens but does not represent the approved mix.

What the ADM Must Preserve

The file must retain the relationship between beds, objects, object metadata and the programme timeline. Confirm that every active object has a valid input, that unused object paths are inactive, and that dialogue, music and effects remain in the intended beds or objects.

Programme metadata matters as much as channel audio. Check programme name, language, content kind, frame rate, start timecode and duration. If the receiving platform supplies a naming sheet, copy its values exactly rather than translating them into local studio shorthand.

• 48 kHz project sample rate unless the delivery document explicitly states otherwise
• Stable programme start and end with the requested handles or leader
• No unintended muted, orphaned or duplicated object feeds
• Downmix and binaural metadata reviewed before the final export

Export and Re-Import Verification

Create the ADM from the approved printmaster session, not from an editorial copy. After export, bring the file into a clean verification session or renderer and compare duration, start timecode, bed layout, object count and loudness with the source.

Listen to representative transitions, dense object movement and the final programme tail. A waveform spot-check alone cannot reveal wrong object metadata, an unexpected bed fold-down or a scene whose objects have lost automation.

Companion Deliverables

Many deliveries require more than the ADM: a loudness report, encoded or rendered reference, stereo and 5.1 versions, and sometimes separate M&E or dialogue-led versions. Derive them from the same approved source and keep their timecode and duration sample-aligned.

Use unambiguous filenames with title, episode, version, language, format and revision. Keep the checksum or transfer report with the delivery so a later upload problem can be distinguished from a mix problem.

Practical QC Checklist

• ADM opens successfully in a fresh renderer or compatible DAW
• Bed and object assignments match the approved session
• Start timecode, frame rate and duration match picture
• Integrated loudness and true peak are measured from the delivered file
• Rendered reference and ADM remain in sync

Treat the ADM as a reconstructable mix package rather than a bounce. A disciplined re-import check catches metadata and routing errors while they are still inexpensive to correct.