From 58d817dadc0d901ad12ce6f8fa0b44ca77a374ea Mon Sep 17 00:00:00 2001 From: Cyril Concolato Date: Tue, 24 Jan 2023 09:05:14 -0800 Subject: [PATCH] try to use better use of cross-references for terms, and for internal sections --- index.html | 100 ++++++++++++++++++++++++++++------------------------- 1 file changed, 53 insertions(+), 47 deletions(-) diff --git a/index.html b/index.html index 2f3a591..b0376df 100644 --- a/index.html +++ b/index.html @@ -21,6 +21,12 @@ publishDate: "2021-10-04", github: "AOMedia/av1-mpeg2-ts", localBiblio: { + "AV1-ISOBMFF": { + title: "AV1 Codec ISO Media File Format Binding, v1.2.0, AOM Final Deliverable, 12 December 2019", + href: "https://aomediacodec.github.io/av1-isobmff/", + status: "Standard", + publisher: "AOM", + }, "MPEG-2 TS": { title: "Information technology — Generic coding of moving pictures and associated audio information — Part 1: Systems", href: "https://www.iso.org/standard/83239.html", @@ -73,7 +79,7 @@

Identifying AV1 streams in MPEG-2 TS

## AV1 registration descriptor -The presence of a Registration Descriptor, as defined in [[!MPEG-2 TS]], is mandatory with the *format_identifier* field set to 'AV01' (A-V-0-1). The Registration Descriptor shall be the first in the PMT loop and included before the AV1 video descriptor. +The presence of a Registration Descriptor is mandatory. It shall be the first in the PMT loop and included before the AV1_video_descriptor. ### Syntax @@ -87,15 +93,15 @@

Identifying AV1 streams in MPEG-2 TS

### Semantics -**descriptor_tag** - This value shall be set to 0x05. +**descriptor_tag** - This value shall be set to 0x05. -**descriptor_length** - This value shall be set to 4. +**descriptor_length** - This value shall be set to 4. -**format_identifier** - This value shall be set to 'AV01' (A-V-0-1). +**format_identifier** - This value shall be set to AV01. -## AV1 video descriptor +## AV1 video descriptor {#AV1-video-descriptor} -The AV1 video descriptor provides basic information for identifying coding parameters, such as profile and level parameters of an AV1 video stream. The same data structure as **AV1CodecConfigurationRecord** in ISOBMFF is used to aid conversion between the two formats, EXCEPT that two of the reserved bits are used for HDR/WCG identification. The syntax and semantics for this descriptor appears in the table below and in the subsequent text. +The AV1_video_descriptor provides basic information for identifying coding parameters, such as profile and level parameters of an AV1 video stream. The same data structure as AV1CodecConfigurationRecord is used to aid conversion between the two formats, EXCEPT that two of the reserved bits are used for HDR/WCG identification. The syntax and semantics for this descriptor appears in the table below and in the subsequent text. ### Syntax @@ -127,13 +133,13 @@

Identifying AV1 streams in MPEG-2 TS

### Semantics -**descriptor_tag** - This value shall be set to 0x80. +**descriptor_tag** - This value shall be set to 0x80. -**descriptor_length** - This value shall be set to 4. +**descriptor_length** - This value shall be set to 4. -**marker** - This value shall be set to 1. +**marker** - This value shall be set to 1. -**version** - This field indicates the version of the AV1_video_descriptor. This value shall be set to 1. +**version** - This field indicates the version of the AV1_video_descriptor. This value shall be set to 1. **seq_profile**, **seq_level_idx_0** and **high_bitdepth** - These fields shall be coded according to the semantics defined in [[!AV1]]. If these fields are not coded in the Sequence Header OBU in the AV1 video stream, the inferred values are coded in the descriptor. @@ -148,7 +154,7 @@

Identifying AV1 streams in MPEG-2 TS

| 2 | Both HDR and WCG are to be indicated in the stream | | 3 | No indication made regarding HDR/WCG or SDR characteristics of the stream | -**reserved_zeros** - Will be set to zeroes. +**reserved_zeros** - Will be set to 0. **initial_presentation_delay_present** - Indicates **initial_presentation_delay_minus_one** field is present. @@ -160,20 +166,20 @@

Identifying AV1 streams in MPEG-2 TS

## General constraints For AV1 video streams, the following constraints apply: - * An AV1 video stream conforming to a profile defined in Annex A of [[!AV1]] shall be an element of an MPEG-2 program and the stream_type for this elementary stream shall be equal to 0x06 (MPEG-2 PES packets containing private data). + * An AV1 video stream conforming to a profile defined in Annex A of [[!AV1]] shall be an element of an MPEG-2 program and the stream_type for this elementary stream shall be equal to 0x06 (MPEG-2 PES packets containing private data). * An AV1 video stream shall have the low overhead byte stream format as defined in [[!AV1]]. - * The sequence_header_obu as specified in [[!AV1]], that are necessary for decoding an AV1 video stream shall be present within the elementary stream carrying that AV1 video stream. - * An OBU may contain the *obu_size* field. For applications that need easy conversion to MP4, using the *obu_size* field is recommended. - * OBU trailing bits should be limited to byte alignment and should not be used for padding. - * Tile List OBUs shall not be used - * Temporal Delimiters may be removed - * Redundant Frame Headers and Padding OBUs may be used. + * The sequence_header_obu as specified in [[!AV1]], that are necessary for decoding an AV1 video stream shall be present within the elementary stream carrying that AV1 video stream. + * An OBU may contain the obu_size field. For applications that need easy conversion to MP4, using the obu_size field is recommended. + * OBU trailing bits should be limited to byte alignment and should not be used for padding. + * Tile List OBUs shall not be used + * Temporal Delimiters may be removed + * Redundant Frame Headers and Padding OBUs may be used. -In addition, a start code insertion and emulation prevention process shall be performed on the AV1 Bitstream prior to its PES encapsulation. This process is described in section 3.2. +In addition, a start code insertion and emulation prevention process shall be performed on the AV1 Bitstream prior to its PES encapsulation. This process is described in [[[#start-codes]]]. -## Start-code based format +## Start-code based format {#start-codes} -Prior to carriage into PES, the AV1 **open_bitstream_unit()** is encapsulated into **ts_open_bitstream_unit()**. This is required to provide direct access to OBU through a start-code mechanism inserted prior to each OBU. The following syntax describes how to retrieve the **open_bitstream_unit()** from the **ts_open_bitstream_unit()** (tsOBU). +Prior to carriage into PES, the AV1 open_bitstream_unit is encapsulated into ts_open_bitstream_unit. This is required to provide direct access to OBU through a start-code mechanism inserted prior to each OBU. The following syntax describes how to retrieve the open_bitstream_unit from the ts_open_bitstream_unit. | Syntax | No. Of bits | Mnemonic | |:------------------------------------------------------------------|:-----------:|:----------:| @@ -190,27 +196,27 @@

Identifying AV1 streams in MPEG-2 TS

| open_bitstream_unit[NumBytesInObu++] | **8** | **uimsbf** | | } | | | -**obu_start_code** - This value shall be set to 0x000001. +**obu_start_code** - This value shall be set to 0x000001. **open_bitstream_unit[i]** - i-th byte of the AV1 open bitstream unit (As defined in section 5.3 of [[!AV1]]). -It is the responsability of the TS muxer to prevent start code emulation by escaping all the forbidden three-byte sequences using the **emulation_prevention_three_byte** (always equal to 0x03). The forbidden sequences are defined below. +It is the responsability of the TS muxer to prevent start code emulation by escaping all the forbidden three-byte sequences using the emulation_prevention_three_byte (always equal to 0x03). The forbidden sequences are defined below. -Within the **ts_open_bitstream_unit()** payload, the following three-byte sequences shall not occur at any byte-aligned position : -* 0x000000 -* 0x000001 -* 0x000002 +Within the ts_open_bitstream_unit payload, the following three-byte sequences shall not occur at any byte-aligned position : +* 0x000000 +* 0x000001 +* 0x000002 -Within the **ts_open_bitstream_unit()** payload, any four-byte sequence that starts with 0x000003 other than the following sequences shall not occur at any byte-aligned position : -* 0x00000300 -* 0x00000301 -* 0x00000302 -* 0x00000303 +Within the ts_open_bitstream_unit payload, any four-byte sequence that starts with 0x000003 other than the following sequences shall not occur at any byte-aligned position : +* 0x00000300 +* 0x00000301 +* 0x00000302 +* 0x00000303 ## The AV1 Access Unit -An AV1 Access Unit consists of all OBUs, including headers, between the end of the last OBU associated -with the previous frame, and the end of the last OBU associated with the current frame. With this definition, an Access Unit sometimes maps with a Decodable Frame Group (DFG) as defined in Annex E of [[!AV1]] and some other times to a Temporal Unit (TU) as defined in [[!AV1]], or both, as illustrated in the figure below. An illustration is provided in the figure below for a group of pictures with frames predicted as follows : +An AV1 Access Unit consists of all OBUs, including headers, between the end of the last OBU associated +with the previous frame, and the end of the last OBU associated with the current frame. With this definition, an Access Unit sometimes maps with a Decodable Frame Group (DFG) as defined in Annex E of [[!AV1]] and some other times to a Temporal Unit (TU) as defined in [[!AV1]], or both, as illustrated in the figure below. An illustration is provided in the figure below for a group of pictures with frames predicted as follows : Practical example of an AV1 Access Unit split
@@ -219,22 +225,22 @@

Identifying AV1 streams in MPEG-2 TS

## Use of PES packets -AV1 video encapsulated as defined in clause 4.2 is carried in PES packets as PES_packet_data_bytes, using the stream_id 0xBD (private_stream_id_1). +AV1 video encapsulated as defined in [[[#start-codes]]] is carried in PES packets as PES_packet_data_bytes, using the stream_id 0xBD (private_stream_id_1). -A PES shall encapsulate one, and only one, AV1 access unit as defined in clause 4.3. All the PES shall have data_alignment_indicator set to 1. Usage of *data_stream_alignment_descriptor* is not specified and the only allowed *alignment_type* is 1 (Access unit level). +A PES shall encapsulate one, and only one, AV1 access unit. All the PES shall have data_alignment_indicator set to 1. Usage of data_stream_alignment_descriptor is not specified and the only allowed alignment_type is 1 (Access unit level). -The highest level that may occur in an AV1 video stream, as well as a profile and tier that the entire stream conforms to, shall be signalled using the AV1 video descriptor. +The highest level that may occur in an AV1 video stream, as well as a profile and tier that the entire stream conforms to, shall be signalled using the AV1_video_descriptor. If an AV1 video descriptor is associated with an AV1 video stream, then this descriptor shall be conveyed in the descriptor loop for the respective elementary stream entry in the program map table. This specification does not specify the presentation of AV1 streams in the context of a program stream. ## Assignment of DTS and PTS -For AV1 video stream multiplexed into [[!MPEG-2 TS]], the *decoder_model_info* may not be present. If the *decoder_model_info* is present, then the STD model shall match with the decoder model defined in Annex E of [[!AV1]]. +For AV1 video stream multiplexed into [[!MPEG-2 TS]], the decoder_model_info may not be present. If the decoder_model_info is present, then the STD model shall match with the decoder model defined in Annex E of [[!AV1]]. -For synchronization and STD management, PTSs and, when appropriate, DTSs are encoded in the header of the PES packet that carries the AV1 video stream data setting the PTS_DTS_flags to '01' or '11'. For PTS and DTS encoding, the constraints and semantics apply as defined in the PES Header and associated constraints on timestamp intervals. +For synchronization and STD management, PTSs and, when appropriate, DTSs are encoded in the header of the PES packet that carries the AV1 video stream data setting the PTS_DTS_flags to 01 or 11. For PTS and DTS encoding, the constraints and semantics apply as defined in the PES Header and associated constraints on timestamp intervals. -There are cases in AV1 bitstreams where information about a frame is sent multiple times. For example, first to be decoded, and subsequently to be displayed. In the case of a frame being decoded but not displayed, it is desired to assign a valid DTS but without need for a PTS. However, the MPEG2-TS specification prevents a DTS from being transmitted without a PTS. Hence, a PTS is always assigned for AV1 access units and its value is not relevant for frames being decoded but not displayed. +There are cases in AV1 bitstreams where information about a frame is sent multiple times. For example, first to be decoded, and subsequently to be displayed. In the case of a frame being decoded but not displayed, it is desired to assign a valid DTS but without need for a PTS. However, the [[!MPEG-2 TS]] specification prevents a DTS from being transmitted without a PTS. Hence, a PTS is always assigned for AV1 access units and its value is not relevant for frames being decoded but not displayed. To achieve consistency between the STD model and the buffer model defined in Annex E of [[!AV1]], the following PTS and DTS assignment rules shall be applied : @@ -245,21 +251,21 @@

Identifying AV1 streams in MPEG-2 TS

| 0 | 1 | n/a |PresentationTime[frame] |ScheduledRemovalTiming[dfg]| | 1 | n/a | n/a |PresentationTime[frame] |ScheduledRemovalTiming[dfg]| -Note : The ScheduleRemovalTiming[] and PresentationTime[] are defined in the Annex E of [[!AV1]]. +Note : The ScheduledRemovalTiming and PresentationTime are defined in the Annex E of [[!AV1]]. ## Buffer considerations ### Buffer pool management -Carriage of an AV1 video stream over [[!MPEG-2 TS]] does not impact the size of the Buffer Pool. +Carriage of an AV1 video stream over [[!MPEG-2 TS]] does not impact the size of the Buffer Pool. -For decoding of an AV1 video stream in the STD, the size of the Buffer Pool is as defined in [[!AV1]]. The Buffer Pool shall be managed as specified in Annex E of [[!AV1]]. +For decoding of an AV1 video stream in the STD, the size of the Buffer Pool is as defined in [[!AV1]]. The shall be managed as specified in Annex E of [[!AV1]]. -A decoded AV1 access unit enters the Buffer Pool instantaneously upon decoding the AV1 access unit, hence at the Scheduled Removal Timing of the AV1 access unit. A decoded AV1 access unit is presented at the Presentation Time. +A decoded AV1 access unit enters the Buffer Pool instantaneously upon decoding the AV1 access unit, hence at the ScheduledRemovalTiming of the AV1 access unit. A decoded AV1 access unit is presented at the PresentationTime. -If the AV1 video stream provides insufficient information to determine the Scheduled Removal Timing and the Presentation Time of AV1 access units, then these time instants shall be determined in the STD model from PTS and DTS timestamps as follows: - 1. The Scheduled Removal Timing of AV1 access unit n is the instant in time indicated by DTS(n) where DTS(n) is the DTS value of AV1 access unit n. - 2. The Presentation Time of AV1 access unit n is the instant in time indicated by PTS(n) where PTS(n) is the PTS value of AV1 access unit n. +If the AV1 video stream provides insufficient information to determine the ScheduledRemovalTiming and the PresentationTime of AV1 access units, then these time instants shall be determined in the STD model from PTS and DTS timestamps as follows: + 1. The ScheduledRemovalTiming of AV1 access unit n is the instant in time indicated by DTS(n) where DTS(n) is the DTS value of AV1 access unit n. + 2. The PresentationTime of AV1 access unit n is the instant in time indicated by PTS(n) where PTS(n) is the PTS value of AV1 access unit n. ### T-STD Extensions for AV1