JCTVC-J0574 Report of BoG on high-level syntax for extension planning [Y.-K. Wang (Qualcomm)]
HEVC related HL syntax documents were discussed in a joint BoG of JCT-VC and JCT-3V. The discussions are reflected in this BoG report. The report was presented in a joint meeting of JCT-VC and JCT-3V Friday 8:00-9:00.
The BoG recommended to adopt the agreed two sets of VPS extension designs, one for each of the two approaches, as described in Section 3 of the BoG report, as the "straw man" designs.
The BoG suggested to discuss whether to include, in the "straw man" designs, the syntax and semantics for inclusion of profile and level information for operation points including at least one enhancement layer, as described in the BoG report.
During the discussion it was suggested to use the value 1 rather than zero for the byte alignment padding in the VPS extension syntax. It was suggested that a place in the text referred to as "unspecified" should be "reserved".
Question raised in the joint meeting: Would it be possible to support standalone decoding of depth? Currently not. This could however be desirable for certain applications e.g. automatic surveillance. The current assumption that depth follows the texture may not always be desirable.
A joint output document was planned: “Solutions considered for HL syntax hooks in scalable and 3D extensions of HEVC”. The MV-HEVC draft should currently refer to this and not prescribe a HL syntax which should be closely aligned to support both scalability and 3D needs.
It was agreed that the “solutions” output document will not include the yellow highlighted syntax elements of JCTVC-J0574r1.
Dostları ilə paylaş: |