1. Intellectual Property Rights
1.1. Disclaimer
This is a document made available by DASH-IF. The technology embodied in this document may involve the use of intellectual property rights, including patents and patent applications owned or controlled by any of the authors or developers of this document. No patent license, either implied or express, is granted to you by this document. DASH-IF has made no search or investigation for such rights, and DASH-IF disclaims any duty to do so. The rights and obligations which apply to DASH-IF documents, as such rights and obligations are set forth and defined in the DASH-IF Bylaws and IPR Policy, including but not limited to patent and other intellectual property license rights and obligations. A copy of the DASH-IF Bylaws and IPR Policy can be obtained at https://dashif.org/.
The material contained herein is provided on an "AS IS" basis and, to the maximum extent permitted by applicable law, this material is provided AS IS, and the authors and developers of this material and DASH-IF hereby disclaim all other warranties and conditions, either express, implied, or statutory, including but not limited to any (if any) implied warranties, duties, or conditions of merchantability, of fitness for a particular purpose, of accuracy or completeness of responses, of workmanlike effort, and of lack of negligence.
In addition, this document may include references to documents and/or technologies controlled by third parties. Those third-party documents and technologies may be subject to third-party rules and licensing terms. No intellectual property license, either implied or express, to any third-party material is granted to you by this document or DASH-IF. DASH-IF makes no warranty whatsoever for such third-party material.
Note: IPR declarations relevant to DASH-IF specifications are published at https://dashif.org/ipr-declarations/.
1.2. Modal Verbs Terminology
In the present document, shall, shall not, should, should not, may, need not, will, will not, can, and cannot are to be interpreted as described in the ETSI Drafting Rules (Verbal forms for the expression of provisions). must and must not are NOT allowed in DASH-IF deliverables except when used in direct citation.
2. Scope
This document specifies DASH-IF IOP v5 Part 8: Audio. It defines audio interoperability points, coding profiles, ISO BMFF packaging, MPD parameters, and audio-specific constraints for DASH-IF compliant services and clients.
The primary normative reference for supported audio codecs is the DASH-IF Codec Registry at https://dashif.org/codecs/. This part defines the general requirements for audio adaptation sets and provides normative baseline requirements for the most widely deployed audio codecs. For the complete and up-to-date list of registered codecs, services and clients shall consult the DASH-IF Codec Registry.
Services shall use only media codecs that are registered in the DASH-IF Codec Registry or explicitly defined in this part. Clients may support any set of codecs registered in the DASH-IF Codec Registry and shall not attempt to play back Representations for which they do not have codec support.
Note: ETSI TS 103 285 [DVBDASH] (the "DVB-DASH" profile) defines its own mandatory and optional audio codec set (HE-AACv2, AC-4, MPEG-H 3D Audio, DTS-UHD, and AVS3-P3) and NGA preselection signalling requirements that are narrower than the DASH-IF Codec Registry. Alignment notes with DVB-DASH are provided in the relevant clauses below.
3. References
The following referenced documents are necessary for the application of this part:
-
ISO/IEC 23009-1 [MPEGDASH].
-
ISO/IEC 23000-19 [MPEGCMAF].
-
ISO/IEC 14496-3, Coding of audio-visual objects — Part 3: Audio (MPEG-4 AAC family).
-
ISO/IEC 23003-1, MPEG Surround.
-
ISO/IEC 23008-3, MPEG-H 3D Audio.
-
DASH-IF IOP v5 Part 2, Core Principles and CMAF Mapping.
-
DASH-IF IOP v5 Part 12, Conformance and Reference Tools.
-
DASH-IF Codec Registry, https://dashif.org/codecs/introduction/ [DASHIF-CODECS].
-
DASH-IF Identifier Registry, https://dashif.org/identifiers/audio_source_metadata/ [DASHIF-IDENTIFIERS].
4. Terms and Definitions
Terms and definitions are inherited from ISO/IEC 23009-1, ISO/IEC 23000-19, and Part 2 unless defined in this part.
- audio adaptation set
-
An Adaptation Set that contains sound information to be rendered to the user, identified by
@mimeType="audio/mp4". - DASH-IF Codec Registry
-
The DASH-IF maintained registry of video and audio codecs supported for use in DASH-IF compliant services, available at https://dashif.org/codecs/.
5. DASH-IF Codec Registry
5.1. Overview
DASH-IF maintains a Codec Registry that serves as the authoritative and continuously updated reference for codecs supported in DASH-IF compliant services. The registry is available at:
-
Web interface: https://dashif.org/codecs/introduction/
-
Source data: https://github.com/Dash-Industry-Forum/Codecs
For audio codecs, the registry provides:
-
A structured list of supported audio codecs with their DASH MPD
@codecsstrings, CMAF profiles, and interoperability notes. -
Codec-specific requirements for
@mimeType,@codecs, AudioChannelConfiguration, and SAP type. -
Guidance on codec selection for different service scenarios (stereo, multichannel, immersive audio, speech, etc.).
-
A machine-readable dataset that can be integrated into validator tools and reference implementations.
Note: The DASH-IF Identifier Registry at
https://dashif.org/identifiers/audio_source_metadata/
provides the @schemeIdUri values for AudioChannelConfiguration elements.
This is a separate registry from the Codec Registry.
5.2. Using the Codec Registry
Services shall use @codecs strings that are registered in the DASH-IF Codec
Registry for the codec and profile being used. The registry defines the
canonical @codecs string format for each supported audio codec.
Clients should use the DASH-IF Codec Registry to determine which audio codecs they are expected to support for a given service scenario. The registry indicates which codecs are mandatory, recommended, or optional for different client categories.
Note: The DASH-IF Codec Registry is a living document that is updated as new codecs are registered and existing codec requirements are refined. Services and clients should consult the current version of the registry rather than relying solely on the static codec tables in this part.
6. Audio Adaptation Set Constraints
AdaptationSet@lang shall be present on every audio adaptation set.
@audioSamplingRate shall be present either on the adaptation set or
Representation level (but not both).
The AudioChannelConfiguration element shall be present either on the
adaptation set or Representation level (but not both). The scheme and value
shall conform to ChannelConfiguration as defined in ISO/IEC 23001-8.
7. Audio Codecs
7.1. General
The following clauses define normative baseline requirements for the audio codecs supported in DASH-IF compliant services. For the complete and up-to-date list of registered audio codecs, consult the DASH-IF Codec Registry.
7.2. HE-AACv2 audio (stereo)
The codec for basic stereo audio support is MPEG-4 High Efficiency AAC v2 Profile, level 2.
Note: HE-AACv2 is also standardized as Enhanced aacPlus in 3GPP TS 26.401.
An HE-AACv2 Profile decoder can also decode any content that conforms to MPEG-4 AAC Profile or MPEG-4 HE-AAC Profile. Therefore, services are free to use any AAC version. Typical clients are expected to play AAC-LC, HE-AAC and HE-AACv2 encoded content.
For content with SBR, i.e. @codecs=mp4a.40.5 or @codecs=mp4a.40.29,
@audioSamplingRate signals the resulting sampling rate after SBR is applied,
e.g. 48 kHz even if the AAC-LC core operates at 24 kHz.
For content with PS, i.e. @codecs=mp4a.40.29, the AudioChannelConfiguration
element signals the resulting channel configuration after PS is applied, e.g.
stereo even if the AAC-LC core operates at mono.
SAP type shall be 1. The @codecs string shall have a value from the below
table.
| Profile | @codecs
|
|---|---|
| MPEG-4 AAC Profile | mp4a.40.2
|
| MPEG-4 HE-AAC Profile | mp4a.40.5
|
| MPEG-4 HE-AAC v2 Profile | mp4a.40.29
|
Note: DVB-DASH [DVBDASH] mandates HE-AACv2 support as a baseline audio codec, consistent with the requirements in this clause. DVB-DASH additionally constrains permitted sampling rates and channel configurations for its base audio profile; services should consult ETSI TS 103 285 clause 6 for the complete set of DVB-DASH audio constraints.
7.3. HE-AACv2 audio (multichannel)
This clause extends HE-AACv2 requirements with multichannel scenarios. All constraints defined for the stereo scenario also apply here.
Support for multichannel content is available in the HE-AACv2 Profile, starting with level 4 for 5.1 and level 6 for 7.1. Decoders implementing MPEG-4 HE-AACv2 multichannel profiles are fully compatible with content encoded in conformance to the HE-AACv2 stereo requirements defined above.
Decoders shall support decoding of loudness and dynamic range related
information, i.e. dynamic_range_info() and MPEG4_ancillary_data() in the
bitstream.
7.4. Enhanced AC-3 (Dolby Digital Plus)
The @codecs parameter shall be ec-3. SAP type shall be 1.
The AudioChannelConfiguration element shall use
@schemeIdUri="tag:dolby.com,2014:dash:audio_channel_configuration:2011" with
@value as defined in the DASH-IF Identifier Registry.
7.5. Dolby TrueHD
The @codecs parameter shall be mlpa. SAP type shall be 1.
7.6. AC-4
The @codecs parameter shall be ac-4. SAP type shall be 1.
The AudioChannelConfiguration element shall use
@schemeIdUri="tag:dolby.com,2014:dash:audio_channel_configuration:2011" with
@value as defined in the DASH-IF Identifier Registry.
7.7. DTS-HD
DTS-HD comprises a number of profiles optimized for specific applications. For all DTS formats, SAP is always 1.
| Codec | @codecs
|
|---|---|
| DTS Digital Surround | dtsc
|
| DTS-HD High Resolution and DTS-HD Master Audio | dtsh
|
| DTS Express | dtse
|
| DTS-HD Lossless (no core) | dtsl
|
7.8. MPEG Surround
MPEG Surround is a scheme for coding multichannel signals based on a down-mixed signal of the original multichannel signal, and associated spatial parameters. The down-mix shall be coded with MPEG-4 High Efficiency AAC v2.
MPEG Surround used in DASH shall comply with level 4 of the Baseline MPEG
Surround profile. SAP type shall be 1. @codecs shall be mp4a.40.30.
7.9. MPEG-H 3D Audio
MPEG-H 3D Audio encoded content shall comply with Level 1, 2 or 3 of the MPEG-H Low Complexity (LC) Profile.
In addition to ISO/IEC 23008-3, the following constraints shall apply to storage of raw MPEG-H audio frames in DASH containers:
-
One audio ISO BMFF sample shall consist of a single
mpegh3daFrame()structure. -
The parameters carried in the
MHADecoderConfigurationRecord()shall be consistent with the configuration of the audio bitstream. In particular,mpegh3daProfileLevelIndicationshall be set to0x0B,0x0C, or0x0Dfor MPEG-H Audio LC Profile Level 1, Level 2, or Level 3, respectively. -
The
referenceChannelLayoutfield carried in theMHADecoderConfigurationRecord()shall be equivalent to what is signaled byChannelConfigurationaccording to ISO/IEC 23001-8. -
Each Media Segment shall start with a SAP of type 1 (e.g. a sync sample).
Note: DVB-DASH [DVBDASH] specifies MPEG-H 3D Audio and NGA (Next Generation
Audio) support using Preselection elements and DASH-IF-aligned
@schemeIdUri values for describing audio presets, consistent with the
mhm1 codec strings in this clause. Services offering MPEG-H content for
DVB-DASH compatibility should verify Preselection signalling against ETSI TS
103 285 clause 6.
| Codec | @codecs
|
|---|---|
| MPEG-H 3D audio LC profile level 1 | mhm1.0x0B
|
| MPEG-H 3D audio LC profile level 2 | mhm1.0x0C
|
| MPEG-H 3D audio LC profile level 3 | mhm1.0x0D
|
7.10. MPEG-D Unified Speech and Audio Coding
MPEG-D Unified Speech and Audio Coding (USAC) has been designed to provide consistently high audio quality with a variety of content that comprises a mixture of audio and speech signals, enabling adaptive switching capability from 12 kbps stereo up to transparency.
Usage of USAC in DASH presentations shall conform to the xHE-AAC media
profile, providing support up to 5.1 multichannel coding.
SAP type shall be 1. @codecs shall be mp4a.40.42.
Note: DVB-DASH [DVBDASH] does not currently mandate USAC/xHE-AAC support; services relying on this codec for DVB-DASH compatibility should provide an alternative codec (e.g. HE-AACv2 or AC-4) as a fallback Adaptation Set.
8. Open Issues and Work Items
| Topic | Status | Next action |
|---|---|---|
| Codec Registry integration | Open | Embed or link the DASH-IF Codec Registry audio table from https://github.com/Dash-Industry-Forum/Codecs into this part, either via a build-time include or a live reference. |
| Codec string verification | Open | Re-verify @codecs values and normative references against current codec registration authorities and the DASH-IF Identifier Registry before this part is finalized.
|
| Cross-part alignment | Open | Align terminology and references with Parts 1, 2, and 12. |
| Conformance mapping | Open | Add Part 12 conformance mapping for Part 8 (codec signalling, adaptation set constraints, AudioChannelConfiguration). |
| Validator-start tool | Open | Create tools/validation/validate_part8_audio_mpd.py covering codec signalling, adaptation set constraints, and Codec Registry compliance.
|
9. Change History
| Version | Date | Change |
|---|---|---|
| 0.1 | Initial | Created initial Bikeshed/Markdown shell for Part 8. |
| 0.2 | Migration | Migrated audio codec and audio adaptation set constraints from DASH-IF-IOP v5-old-draft. |
| 0.3 | Restructure | Added DASH-IF Codec Registry section (dashif.org/codecs, GitHub Codecs repo). Updated scope to reference registry as authoritative source. Added DASHIF-IDENTIFIERS reference for AudioChannelConfiguration. Updated open issues. |