DASH-IF Logo

DASH-IF IOP v5 Part 7: Video

Living Document,

This version:
https://dashif.org/Guidelines/iop-v5/part07-video.html
Issue Tracking:
GitHub
Currently open Part 7 issues
File a new Part 7 issue (then assign to Part 7 project)
Editor:
Stephan Schreiner (Dolby)
Document Status:
Working Draft 0.3.
See Annex A: Document Status for versioning and workflow.
Contributors:
Contributors are maintained via GitHub pull requests to the IOPv5 repository.
Contributing:
See Part 1 §1.4 Contributing and Reviewing.
Key Words:
Video, CMAF, Codecs, HDR, MPD Signalling

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 7: Video. It defines video interoperability points, CMAF media profiles, codec signalling, DASH MPD parameters, and video-specific constraints for DASH-IF compliant services and clients.

The primary normative reference for supported video codecs is the DASH-IF Codec Registry at https://dashif.org/codecs/. This part defines the general requirements for video adaptation sets and provides normative baseline requirements for the most widely deployed codecs (H.264/AVC and H.265/HEVC). 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 video codec set (H.264/AVC, HEVC, VVC, and AVS3), profile/level constraints, and HDR/HFR signalling that is 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:

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.

video adaptation set

An Adaptation Set that contains visual information for display to the user, identified by @mimeType="video/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:

The registry provides:

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 codec.

Clients should use the DASH-IF Codec Registry to determine which 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.

5.3. Codec Registration Process

New codecs may be proposed for registration via the GitHub repository at https://github.com/Dash-Industry-Forum/Codecs. The registration process requires:

6. Video Codecs

6.1. General

The following clauses define normative baseline requirements for the most widely deployed video codecs. For additional codecs, consult the DASH-IF Codec Registry.

6.2. H.264 (AVC)

The H.264 (AVC) codec may be used by services for video adaptation sets. Clients should support this codec.

For Representations up to 1280x720p resolution and up to 30 fps, the H.264 (AVC) Progressive High Profile Level 3.1 decoder shall be used.

For Representations up to 1920x1080p resolution and up to 30 fps, the H.264 (AVC) Progressive High Profile Level 4.0 decoder shall be used.

The encapsulation of H.264 data in DASH containers shall conform to ISO/IEC 14496-15.

Clients shall support SPS/PPS storage both in the Initialization Segment (sample entry avc1) and inband storage (sample entry avc3). Services may use either form.

Note: Use of avc3 is one of the factors that enables bitstream switching.

Example @codecs strings for H.264 (AVC).
Profile Level @codecs
H.264 (AVC) Progressive High Profile 3.1 avc1.64Y01F / avc3.64Y01F
4.0 avc1.64Y028 / avc3.64Y028

Note: Other @codecs strings may also be compatible (a higher level decoder can typically decode content intended for a lower level decoder). See the DASH-IF Codec Registry for the complete list of registered H.264 @codecs strings.

Note: DVB-DASH [DVBDASH] mandates support for H.264/AVC High Profile up to Level 4.0 (1920x1080p) for its base video profile, consistent with the H.264 Level 4.0 requirement in this clause. Services relying only on Level 3.1 for DVB-DASH compatibility should verify against the current DVB-DASH Content Provider Guidelines, as DVB-DASH devices are not required to support resolutions or levels beyond those mandated there.

6.3. H.265 (HEVC)

The H.265 (HEVC) codec may be used by services for video adaptation sets.

For Representations up to 1280x720p at up to 30 fps, the HEVC Main Profile Main Tier Level 3.1 decoder shall be used.

For Representations up to 2048x1080 at up to 60 fps at 8-bit frame depth, the HEVC Main Profile Main Tier Level 4.1 decoder shall be used.

For Representations up to 2048x1080 at up to 60 fps at 10-bit frame depth, the HEVC Main10 Profile Main Tier Level 4.1 decoder shall be used.

The encapsulation of H.265 data in DASH containers shall conform to ISO/IEC 14496-15.

Clients shall support VPS/SPS/PPS storage both in the Initialization Segment (sample entry hvc1) and inband storage (sample entry hev1). Services may use either form.

Note: Use of hev1 is one of the factors that enables bitstream switching.

Example @codecs strings for H.265 (HEVC).
Profile Level @codecs
HEVC Main 3.1 hev1.1.2.L93.B0 / hvc1.1.2.L93.B0
4.1 hev1.1.2.L123.B0 / hvc1.1.2.L123.B0
HEVC Main-10 4.1 hev1.2.4.L123.B0 / hvc1.2.4.L123.B0

Note: See the DASH-IF Codec Registry for HEVC HDR, UHD, and additional profile @codecs strings.

Note: DVB-DASH [DVBDASH] mandates support for HEVC Main and Main 10 Profile, Main Tier, up to Level 5.1, with additional constraints for UHD and HDR (HLG10 and PQ10) services, in some cases exceeding the baseline Level 4.1 requirement in this clause. Services targeting DVB-DASH UHD/HDR compatibility should consult ETSI TS 103 285 clause 5 directly rather than relying solely on this part’s baseline HEVC requirements.

6.4. Decoder configuration with H.264 and H.265

This clause applies only to video adaptation sets that use H.264 or H.265.

All Initialization Segments in the same video adaptation set shall use the same sample description (i.e. no mixing of avc1 and avc3 is allowed).

In Representations using avc1 or hvc1 sample description:

In Representations using avc3 or hev1 sample description:

6.5. Bitstream switching with H.264 and H.265

This clause applies only to bitstream-switching adaptation sets that use H.264 or H.265.

All Representations shall be encoded using the avc3 or hev1 sample description.

The first presented sample’s composition time shall equal the first decoded sample’s decode time, which equals the baseMediaDecodeTime in the Track Fragment Decode Time Box (tfdt).

Note: This requires the use of negative composition offsets in a v1 Track Run Box (trun) for video samples, otherwise video sample reordering will result in a delay of video relative to audio.

7. Video Adaptation Set Constraints

All Representations in the same video adaptation set shall be alternative encodings of the same source content, encoded such that switching between them does not produce visual glitches due to picture size or aspect ratio differences.

The encoded picture shall only contain the active video area, so that clients can frame the height and width of the encoded video to the size and shape of their currently selected display area without extraneous padding in the decoded video, such as letterbox or pillarbox bars.

Representations in the same video adaptation set shall not differ in any of the following parameters:

If different video adaptation sets differ in any of the above parameters, these parameters should be signaled in the MPD on the adaptation set level by a Supplemental Property Descriptor or an Essential Property Descriptor with @schemeIdUri="urn:mpeg:mpegB:cicp:<Parameter>", with <Parameter> being one of ColourPrimaries, TransferCharacteristics, or MatrixCoefficients.

In any video adaptation set, the following shall be present:

Note: @width and @height indicate the number of encoded pixels. @par indicates the final intended display aspect ratio and @sar is effectively the ratio of aspect ratios (ratio of @width x @height to @par). The formula is: display aspect ratio = picture aspect ratio / sample aspect ratio.

Given a coded picture of 720x576 pixels with an intended display aspect ratio of 16:9:

In any video adaptation set, the following should not be present and shall be ignored by clients if present, as these values are trivial to determine at runtime:

@scanType should not be present and if present shall have the value progressive. Non-progressive video is not interoperable.

Note: DVB-DASH [DVBDASH] additionally requires HDR-capable Adaptation Sets to signal the applicable transfer characteristics (HLG or PQ) using the urn:mpeg:mpegB:cicp:TransferCharacteristics Supplemental/Essential Property descriptor referenced above, and imposes its own constraints on High Frame Rate (HFR) signalling via @maximumSAPPeriod and frame-rate-dependent profile/level selection. Services offering combined HDR/HFR content intended for DVB-DASH players should consult ETSI TS 103 285 clause 5 for the complete set of required descriptors.

8. Open Issues and Work Items

Part 7 open issues and topics to progress.
Topic Status Next action
Codec Registry integration Open Embed or link the DASH-IF Codec Registry table from https://github.com/Dash-Industry-Forum/Codecs into this part, either via a build-time include or a live reference.
Cross-part alignment Open Align terminology and references with Parts 1, 2, and 12.
Conformance mapping Open Add Part 12 conformance mapping for Part 7 (codec signalling, adaptation set constraints).
Validator-start tool Open Create tools/validation/validate_part7_video_mpd.py covering codec signalling, adaptation set constraints, and Codec Registry compliance.
Legacy codec profiles Deferred HDR, UHD 4K, Dolby Vision, VP9 profiles from IOP v4.x are documented in Annex A for reference. Future normative support should be driven by Codec Registry registration.

9. Change History

Part 7 change history.
Version Date Change
0.1 Initial Created initial Bikeshed/Markdown shell for Part 7.
0.2 Migration Migrated H.264/H.265 codec and video 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. Moved HDR/UHD/VP9 to informative Annex A. Added codec registration process description.

10. Annex A: Legacy Codec Profiles (Informative)

10.1. General

This annex documents codec profiles that were specified in earlier versions of DASH-IF IOP (v4.x and earlier). These profiles are provided for reference only and are not normative in IOP v5. Services wishing to use these codecs should consult the DASH-IF Codec Registry for current normative requirements.

10.2. HEVC HDR PQ10

Earlier IOP versions specified HEVC HDR PQ10 profiles including SMPTE 2094-10, SMPTE 2094-40, and TS 103.433 dynamic metadata. These profiles are now tracked in the DASH-IF Codec Registry at https://dashif.org/codecs/.

10.3. UHD HEVC 4K

Earlier IOP versions specified UHD HEVC 4K profiles (up to 3840x2160 at up to 60 fps). These profiles are now tracked in the DASH-IF Codec Registry.

10.4. Dolby Vision Dual-Stream

Earlier IOP versions specified Dolby Vision dual-stream profiles. These profiles are now tracked in the DASH-IF Codec Registry.

10.5. VP9

Earlier IOP versions specified VP9 codec requirements. VP9 support is now tracked in the DASH-IF Codec Registry.

Note: For all of the above legacy profiles, the DASH-IF Codec Registry at https://dashif.org/codecs/ is the authoritative and up-to-date reference. The GitHub repository at https://github.com/Dash-Industry-Forum/Codecs contains the registry source data and accepts contributions for new codec registrations.

Index

Terms defined by this specification

References

Normative References

[MPEGCMAF]
Information technology - Multimedia application format (MPEG-A) - Part 19: Common media application format (CMAF) for segmented media. 2024. URL: https://www.iso.org/standard/85623.html
[MPEGDASH]
Information technology - Dynamic adaptive streaming over HTTP (DASH) - Part 1: Media presentation description and segment formats. 2022. URL: https://www.iso.org/standard/83314.html

Non-Normative References

[DASHIF-CODECS]
DASH-IF Codec Registry. 2024. URL: https://dashif.org/codecs/introduction/
[DVBDASH]
ETSI TS 103 285: MPEG-DASH Profile for Transport of ISO BMFF Based DVB Services over IP Based Networks. 2024. URL: https://www.etsi.org/standards-search