Back to Search Document details
32nd Meeting: Hannover, DE, October 2023 2023-12-02 00:54
SEI processing order and processing order nesting SEI messages in VVC (draft 6)
Abstract
This document contains the draft text for changes to the Versatile Video Coding (VVC) standard (Rec. ITU-T H.266 | ISO/IEC 23090-3), to specify the SEI processing order SEI message.
JVET-AF2027 SEI processing order and processing order nesting SEI messages in VVC (draft 6) [G. J. Sullivan, M. M. Hannuksela, Y.-K. Wang] [WG 5 preliminary WD 5 N 246] (2023-12-01)

Primary editor: G. J. Sullivan

Updated from JVET-AF0049, JVET-AF0062, JVET-AF0070, JVET-AF0189, JVET-AF0310. The subsequent list was provided after the meeting by Y.-K. Wang, after consultation with relevant contributors.

  1. (SW change needed, Bytedance) Addition of po_id (JVET-AF0061, JVET-AF0174, JVET-AF0067, JVET-AF0310) [Bytedance/HHI/MediaTek/Nokia/Dolby]
  2. (not sure whether SW change is needed, Dolby) On the persistence scope of the SPO SEI message (JVET-AF0189, JVET-AF0049, JVET-AF0061, JVET-AF0174, JVET-AF0310) [Dolby/Nokia/Bytedance/HHI/MediaTek]
  3. (SW change needed, Nokia) Addition of the processing order nesting SEI message (JVET-AF0049, JVET-AF0174, JVET-AF0310) [Nokia/HHI/Dolby/Bytedance/MediaTek]. This includes:
    1. Removing the requirement for po_sei_processing_order[ i ] to be equal to 0 and the requirement for po_sei_processing_order[ i ] to be no larger than po_sei_processing_order[ i − 1 ] + 1 (see notes for JVET-AF0049 and item 5 of JVET-AF0310).
    2. Including a list of pon_target_po_id[ i ] values in the processing order nesting SEI message to identify associated PO SEI messages (item 6 of JVET-AF0310).
  4. (SW change not needed) Removal of the constraint requiring that there shall be at least two values of po_sei_processing_order[ i ] that are not equal, from JVET-AF0049 and JVET-AF0062 [Nokia/Bytedance]. This was originally a redundant constraint and thus purely an editorial change, but is also part of the technical change per item 9) below.
  5. (SW change needed, Dolby) The SEI prefix indications, when present, are signalled in units of bits instead of in units of bytes, same as in the SEI prefix indication SEI message, from JVET-AF0189, JVET-AF0062, and JVET-AF0049. [Dolby/Bytedance/Nokia]
  6. (SW change needed, Bytedance) Move po_sei_prefix_flag[ i ] from immediately before po_sei_payload_type[ i ] to be immediately after po_sei_payload_type[ i ], from JVET-AF0062. [Bytedance]
  7. (SW change not needed) Add a NOTE to clarify the following aspects: In the semantics of the SPO SEI message, two different types of SEI messages may have the same SEI payloadType value but are differentiated by some syntax elements in the SEI payload. For example, two NNPFC SEI messages with different nnpfc_id values are considered as having two different SEI message types. From JVET-AF0062. [Bytedance]
  8. (SW change needed, Dolby) Using separate loops for the payload type and processing order information, from JVET-AF0189. [Dolby]
  9. (SW change likely needed, Dolby) Removing the constraint that “The value of po_sei_processing_order[ po_num_sei_messages_‌minus2 + 1 ] shall not be equal to 0”, from JVET-AF0189. [Dolby]
  10. (SW change likely needed, Dolby) Modifying the use of SeiProcessingOrderSeiList such that it determines which SEI messages are allowed to appear in an SEI processing order SEI message, and update the values in the list, including disallowing the SEI payloadType value of the decoded picture hash SEI message from being included in the list, from JVET-AF0189 and JVET-AF0070. [Dolby/Sharp]
Remains valid – not updated: JVET-AE2028 Additional conformance bitstreams for VVC multilayer configurations [S. Iwamura, P. de Lagrange, I. Moccagatta] (2023-09-01)
Remains valid – not updated: JVET-AB2029 Visual quality comparison of ECM/VTM encoding [V. Baroncini, J.-R. Ohm, M. Wien] [AG 5 N 75]
Remains valid – not updated: JVET-AE2030 Optimization of encoders and receiving systems for machine analysis of coded video content (draft 3) [J. Chen, C. Hollmann, S. Liu] [WG 5 N 224)] (2023-09-15)

Expect CDTR April 2024. Could later be defined as part of MPEG-AI, or MPEG-C

JVET-AF2027 SEI processing order and processing order nesting SEI messages in VVC (draft 6) [G. J. Sullivan, M. M. Hannuksela, Y.-K. Wang] [WG 5 preliminary WD 5 N 246] (2023-12-01)

Primary editor: G. J. Sullivan

Updated from JVET-AF0049, JVET-AF0062, JVET-AF0070, JVET-AF0189, JVET-AF0310. The subsequent list was provided after the meeting by Y.-K. Wang, after consultation with relevant contributors.

(SW change needed, Bytedance) Addition of po_id (JVET-AF0061, JVET-AF0174, JVET-AF0067, JVET-AF0310) [Bytedance/HHI/MediaTek/Nokia/Dolby]

(not sure whether SW change is needed, Dolby) On the persistence scope of the SPO SEI message (JVET-AF0189, JVET-AF0049, JVET-AF0061, JVET-AF0174, JVET-AF0310) [Dolby/Nokia/Bytedance/HHI/MediaTek]

(SW change needed, Nokia) Addition of the processing order nesting SEI message (JVET-AF0049, JVET-AF0174, JVET-AF0310) [Nokia/HHI/Dolby/Bytedance/MediaTek]. This includes:

Removing the requirement for po_sei_processing_order[ i ] to be equal to 0 and the requirement for po_sei_processing_order[ i ] to be no larger than po_sei_processing_order[ i − 1 ] + 1 (see notes for JVET-AF0049 and item 5 of JVET-AF0310).

Including a list of pon_target_po_id[ i ] values in the processing order nesting SEI message to identify associated PO SEI messages (item 6 of JVET-AF0310).

(SW change not needed) Removal of the constraint requiring that there shall be at least two values of po_sei_processing_order[ i ] that are not equal, from JVET-AF0049 and JVET-AF0062 [Nokia/Bytedance]. This was originally a redundant constraint and thus purely an editorial change, but is also part of the technical change per item 9) below.

(SW change needed, Dolby) The SEI prefix indications, when present, are signalled in units of bits instead of in units of bytes, same as in the SEI prefix indication SEI message, from JVET-AF0189, JVET-AF0062, and JVET-AF0049. [Dolby/Bytedance/Nokia]

(SW change needed, Bytedance) Move po_sei_prefix_flag[ i ] from immediately before po_sei_payload_type[ i ] to be immediately after po_sei_payload_type[ i ], from JVET-AF0062. [Bytedance]

(SW change not needed) Add a NOTE to clarify the following aspects: In the semantics of the SPO SEI message, two different types of SEI messages may have the same SEI payloadType value but are differentiated by some syntax elements in the SEI payload. For example, two NNPFC SEI messages with different nnpfc_id values are considered as having two different SEI message types. From JVET-AF0062. [Bytedance]

(SW change needed, Dolby) Using separate loops for the payload type and processing order information, from JVET-AF0189. [Dolby]

(SW change likely needed, Dolby) Removing the constraint that “The value of po_sei_processing_order[ po_num_sei_messages_‌minus2 + 1 ] shall not be equal to 0”, from JVET-AF0189. [Dolby]

(SW change likely needed, Dolby) Modifying the use of SeiProcessingOrderSeiList such that it determines which SEI messages are allowed to appear in an SEI processing order SEI message, and update the values in the list, including disallowing the SEI payloadType value of the decoded picture hash SEI message from being included in the list, from JVET-AF0189 and JVET-AF0070. [Dolby/Sharp]

Remains valid – not updated: JVET-AE2028 Additional conformance bitstreams for VVC multilayer configurations [S. Iwamura, P. de Lagrange, I. Moccagatta] (2023-09-01)

Remains valid – not updated: JVET-AB2029 Visual quality comparison of ECM/VTM encoding [V. Baroncini, J.-R. Ohm, M. Wien] [AG 5 N 75]

Remains valid – not updated: JVET-AE2030 Optimization of encoders and receiving systems for machine analysis of coded video content (draft 3) [J. Chen, C. Hollmann, S. Liu] [WG 5 N 224)] (2023-09-15)

Expect CDTR April 2024. Could later be defined as part of MPEG-AI, or MPEG-C

Decisions
JVET-AF2027 SEI processing order and processing order nesting SEI messages in VVC (Draft 6), also issued as WG 5 preliminary WD N 246
Expect CDTR April 2024. Could later be defined as part of MPEG-AI, or MPEG-C
Citation