Orbit

ADM Basics ​

You don't need to be an ADM expert to use Orbit, but understanding a few key concepts will help you make sense of what you're seeing. This page covers the essentials — what ADM files contain, how beds and objects differ, and how Orbit interprets the format.

What is an ADM BWF file ​

An ADM BWF is a broadcast wave file that carries ADM (Audio Definition Model) metadata for immersive audio. It includes:

  • Programme information (what the mix is called, timing, and structure).
  • Beds (channel-based audio elements).
  • Objects (independent elements with positions that can change over time).

If you want deeper background, see the EBU ADM overview, the BW64 specification, and the Dolby Atmos Master ADM Profile:

Beds vs objects ​

  • Beds are a fixed channel layout that anchors the mix.
  • Objects move freely in 3D space and can be automated.

Bed format ​

7.1.2 is the standard maximum bed size for Dolby Atmos Master ADM, and Orbit is optimized for this format. The detected bed format is displayed as a badge in the sidebar header.

Using other bed formats?

Orbit is built to read smaller bed configurations (such as 5.1 or 7.1) and will map them using VBAP, but these are untested as they're difficult to access. If you're working with non-7.1.2 beds and encounter issues, get in touch — we'd love to chat and make sure Orbit reads your files correctly.

Why this matters in QC ​

  • Beds confirm channel mapping and overall stability.
  • Objects reveal motion errors, missing automation, or level issues.

How Orbit reads ADM (standards compliance) ​

  • Reads ADM metadata (AXML/CHNA) from inside the BWF container. Files without proper ADM metadata are rejected.
  • Follows ADM Cartesian coordinates per ITU-R BS.2076 (X=left/right, Y=back/front, Z=bottom/top), translating to the chosen monitoring output while preserving spatial intent.
  • Beds are mapped to the Dolby Atmos 7.1.4 speaker labels; objects include their position, gain, and metadata.
  • Automation is interpolated smoothly for playback and visualization, preserving the intent of jumps versus smooth moves.
  • Objects are distributed across the 7.1.4 speaker set (excluding LFE) using position-driven panning. Binaural and stereo outputs are derived from this same speaker field.

How Orbit differs from the Dolby Renderer ​

  • Orbit is a QC and playback tool; it does not author, encode, or export ADM/Atmos masters.
  • Uses its own rendering pipeline for 7.1.4 speakers, binaural, and stereo fold-down with clear channel mapping.
  • Not a replacement for Dolby's deliverable checks, encoding workflows, or certification processes.
  • Orbit is independent and not affiliated with or endorsed by Dolby. Always validate final deliverables in your Dolby toolchain if certification is required.

Dolby Atmos Master ADM Profile v1.1 ​

  • Orbit supports the Dolby Atmos Master ADM Profile v1.1, reading AXML/CHNA metadata from BWF containers.
  • Beds are mapped as DirectSpeakers to the 7.1.4 layout; objects maintain their position, gain, and metadata attributes.
  • Uses ADM Cartesian coordinates (ITU-R BS.2076) throughout, mapping to speakers and then to binaural or stereo outputs.
  • Automation is interpolated for smooth playback while preserving jump versus smooth move intent.
  • Supports RF64/BW64 containers. Files missing required ADM chunks are rejected at load.
  • Content plays without strict URN enforcement, but you should validate deliverables in Dolby tools for certification.
  • Orbit does not read the Dolby Audio metadata (dbmd) chunk — only Dolby licensed tools read this. Include and validate it in Dolby tools when preparing certified deliverables.

INFO

You do not need to edit or author ADM data in Orbit. The goal is to verify the playback behavior.

Orbit user documentation

© 2026 South Loop Studios