HDR10+ AV1 Metadata Handling Specification

AOM Working Group Approved Draft,

This version:
Issue Tracking:
Paul Hearty (Samsung)
Bill Mandel (Samsung)
Cyril Concolato (Netflix)

This document is the release candidate for the next version of this specification. It awaits formal approval by the AOM. This specification is a draft of a potential new version of this specification and should not be referenced other than as a working draft.

Copyright 2021, AOM

Licensing information is available at http://aomedia.org/license/

The MATERIALS ARE PROVIDED “AS IS.” The Alliance for Open Media, its members, and its contributors expressly disclaim any warranties (express, implied, or otherwise), including implied warranties of merchantability, non-infringement, fitness for a particular purpose, or title, related to the materials. The entire risk as to implementing or otherwise using the materials is assumed by the implementer and user. IN NO EVENT WILL THE ALLIANCE FOR OPEN MEDIA, ITS MEMBERS, OR CONTRIBUTORS BE LIABLE TO ANY OTHER PARTY FOR LOST PROFITS OR ANY FORM OF INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES OF ANY CHARACTER FROM ANY CAUSES OF ACTION OF ANY KIND WITH RESPECT TO THIS DELIVERABLE OR ITS GOVERNING AGREEMENT, WHETHER BASED ON BREACH OF CONTRACT, TORT (INCLUDING NEGLIGENCE), OR OTHERWISE, AND WHETHER OR NOT THE OTHER MEMBER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.


This document specifies how to use HDR10+ metadata within [AV1] streams, including when carried in [CMAF].

1. Introduction

This document specifies how to use HDR10+ metadata within [AV1] streams, including when carried in [CMAF].

Various tools, services and devices support creation and use of HDR10+ metadata which can be easily utilized directly in [AV1] systems. Carriage of HDR10+ metadata in [AV1] leverages [ITU-T-T35] and [CTA-861]. HDR10+ metadata is placed in metadata OBUs of type ITU-T T.35 Metadata. This document covers details of the placement of these OBUs in AV1 streams.

2. Use of HDR10+ in AV1 streams

2.1. HDR10+ OBU

In this specification, HDR10+ Metadata is defined as data with the semantics defined in [SMPTE-ST-2094-40], using the syntax defined in [CTA-861]. HDR10+ Metadata OBU is defined as HDR10+ Metadata carried in an OBU of type ITU-T T.35 Metadata as defined in [AV1] and illustrated in Figure 1.

Figure 1. METADATA_TYPE_ITUT_T35 OBU Structure

NOTE: [AV1] defines the general Metadata OBU syntax for HDR10 Static Metadata and ITU-T T.35 Metadata.

2.2. Constraints

The following sections define constraints that apply to AV1 streams when carrying HDR10+ Metadata.

2.2.1. Color Configuration

Streams suitable for incorporating HDR10+ metadata as described in this specification shall use the following values for the AV1 color_config:

Additionally, the following recommendations apply:

2.2.2. Placement of OBUs

As defined in [AV1] and shown in Figure 2, an AV1 coded video sequence consists of one or more TUs. A TU contains a series of OBUs starting from a Temporal Delimiter, optional sequence headers, optional metadata OBUs, a sequence of one or more frame headers, each followed by zero or more tile group OBUs as well as optional padding OBUs.

Consequently, for each frame with show_frame=1 or show_existing_frame=1, there shall be one and only one HDR10+ metadata OBU preceding the Frame Header for this frame and located after the last OBU of the previous frame (if any) or after the Sequence Header (if any) or after the start of the TU (e.g. after the Temporal Delimiter, for storage formats where Temporal Delimiters are preserved).

HDR10+ Metadata OBUs are not provided when show_frame=0. For non-layered streams, there is only one HDR10+ Metadata OBU per TU. For AV1 streams encoded with multiple layers, HDR10+ Metadata may apply to one or more layers but the details are out of scope of this version of the specification.

Figure 2. Example of OBU_Frame Structure

HDR10 Static Metadata (defined as MDCV, MaxCLL and MaxFALL) may be present.

2.2.3. Provision for Film Grain Processing

It is possible that some [AV1] coded bitstreams may contain both HDR10+ Metadata and film grain synthesis information. It is recommended that decoders in such scenarios perform the film grain synthesis prior to any HDR10+ Metadata processing.

3. Storage and Transport considerations

3.1. Constraints on AV1CodecConfigurationRecord

For formats that use the AV1CodecConfigurationRecord when storing AV1 streams (e.g. ISOBMFF and MPEG-2 TS), HDR10+ Metadata OBUs shall not be present in the configOBUs field of the AV1CodecConfigurationRecord.

3.2. ISOBMFF Constraints

AV1 Metadata sample group defined in [AV1-ISOBMFF] shall not be used.

[AV1-ISOBMFF] indicates that Metadata OBUs may be protected. This specification requires that HDR10 Static Metadata and HDR10+ Metadata OBUs be unprotected.

An ISOBMFF file or CMAF AV1 track as defined in [AV1-ISOBMFF] that also conforms to this specification (i.e. that contains HDR10+ metadata OBUs and complies to the constraints from this specification) should use the brand cdm4 defined in [CTA-5001] in addition to the brand av01. If the brand cdm4 is used in conjunction with AV1 streams, the constraints defined in this specification shall be respected.

3.3. HTTP Streaming Constraints

The value of the codecs parameter for AV1 streams that is used when using HTTP streaming technologies shall remain unchanged when HDR10+ Metadata OBUs are included in the AV1 stream.

Additionally, [DASH] content following [DASH-IOP] should include a Supplemental Descriptor with a @schemeUri set to "http://dashif.org/metadata/hdr" and a @value set to "SMPTE2094-40" in manifest files to aid players to identify tracks containing HDR10+ Metadata OBUs.

4. Example Streams and Tools

Information on this topic is found in the Wiki for this project.


Conformance requirements are expressed with a combination of descriptive assertions and RFC 2119 terminology. The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this document are to be interpreted as described in RFC 2119. However, for readability, these words do not appear in all uppercase letters in this specification.

All of the text of this specification is normative except sections explicitly marked as non-normative, examples, and notes. [RFC2119]

Examples in this specification are introduced with the words “for example” or are set apart from the normative text with class="example", like this:

This is an example of an informative example.

Informative notes begin with the word “Note” and are set apart from the normative text with class="note", like this:

Note, this is an informative note.


Terms defined by this specification

Terms defined by reference


Normative References

AV1 Bitstream & Decoding Process Specification. Standard. URL: https://aomediacodec.github.io/av1-spec/av1-spec.pdf
AV1 Codec ISO Media File Format Binding. Standard. URL: https://aomediacodec.github.io/av1-isobmff/
Information technology — Multimedia application format (MPEG-A) — Part 19: Common media application format (CMAF) for segmented media.. Standard. URL: https://www.iso.org/standard/71975.html
CTA-5001-C. Standard. URL: https://shop.cta.tech/products/web-application-video-ecosystem-content-specification
ANSI/CTA-861-H. Standard. URL: https://shop.cta.tech/products/a-dtv-profile-for-uncompressed-high-speed-digital-interfaces-cta-861-h
Information technology — Dynamic adaptive streaming over HTTP (DASH) — Part 1: Media presentation description and segment formats. Standard. URL: https://www.iso.org/standard/79329.html
ITU-T T.35. Standard. URL: https://www.itu.int/rec/T-REC-T.35-200002-I/en
S. Bradner. Key words for use in RFCs to Indicate Requirement Levels. March 1997. Best Current Practice. URL: https://datatracker.ietf.org/doc/html/rfc2119
SMPTE ST 2086:2018. Standard. URL: https://ieeexplore.ieee.org/document/8353899
SMPTE ST 2094-40:2020. Standard. URL: https://ieeexplore.ieee.org/document/9095450

Informative References

BT.2020. Standard. URL: https://www.itu.int/rec/R-REC-BT.2020
BT.2100. Standard. URL: https://www.itu.int/rec/R-REC-BT.2100
Guideline for Implementation: DASH-IF Interoperability Points V4.3: On-Demand and Mixed Services, HDR Dynamic Metadata and other Improvements.. Standard. URL: https://dashif.org/guidelines/
SMPTE ST 2084:2014. Standard. URL: https://ieeexplore.ieee.org/document/7291452