IAMF Validator

TERMINOLOGY GUIDE

IAMF and Eclipsa Audio.

Related terms do not make file structure, platform acceptance, and playback the same test.

IAMF describes an audio model and format

AOMedia’s IAMF specification defines an immersive audio model, descriptors, a standalone sequence format, and carriage in an ISO base media file container. The descriptors express how audio components relate and how a mix is presented.

A container track, an Audio Element, an audio substream, and a Mix Presentation describe different structures. A count of encoded substreams does not by itself tell you the output channel count.

Eclipsa Audio appears in delivery guidance

YouTube uses the Eclipsa Audio name in its immersive audio formatting guidance. That page explicitly identifies a music partner audience. Refer to each delivery document’s audience and wording before applying it to your workflow.

Finding IAMF descriptors helps establish what is in the file. It does not establish how YouTube will process the upload or which playback experience a device will provide.

Four questions to keep separate

  1. Can this parser identify IAMF? The structure is recognized within the tool’s supported input paths.
  2. Does the file conform to the standard? Full conformance requires more coverage than this limited descriptor parser provides.
  3. Will YouTube accept this delivery? That requires the actual platform, account, and delivery context.
  4. Will it play as intended? That requires playback and listening checks on the relevant setup.

What the validator contributes

It reads supported metadata locally, evaluates explicit rules, and keeps observed values with each finding. A successful result is limited to the checked scope. Audio payloads, measured loudness, actual channel content, platform ingestion, and device playback are outside this release.

Read the methodology or follow the upload preparation workflow.