Back to Search Document details
18th Meeting: Teleconference, April 2020 2020-04-03 21:07
AHG9: On decoding capability information
Abstract
This contribution proposes to move Decoding Capability Information (DCI) from parameter set to SEI message as the information is not necessary for decoding process. The proposed DCI SEI message carries the preferred decoding capability information applied to the entire bitstream.
JVET-R0260 AHG9: On decoding capability information [Y. He, V. Seregin, M. Coban, M. Karczewicz (Qualcomm)]

This contribution proposes to move decoding dapability information (DCI) from parameter set to an SEI message, as the information is not necessary for decoding process. The proposed DCI SEI message carries the preferred decoding capability information applied to the entire bitstream.

The proposal also suggests to change the DCI syntax.

It was noted that DCI is optional and that can be at the same place in the bitstream as an SEI message.

A technical benefit would be to avoid using a NAL unit type for DCI.

It was commented that the primary purpose of the DCI is for the system layer, for which it is important that the information can be easily located in the bitstream. The scope of the DCI is also broader than for an SEI message, or at least for the SEI messages that we have currently specified.

It was commented that although this seemed like it might be feasible, it does not seem necessary, so no action was taken on this.

The proponent indicated that it was not necessary to consider the proposed change of the syntax, in view of the above.

Decisions
The proponent indicated that it was not necessary to consider the proposed change of the syntax, in view of the above.
Citation