Opened 4 years ago

Closed 4 years ago

#1133 closed defect (fixed)

Wrong conditioning of sps_sign_data_hiding_enabled_flag in SPS

Reported by: bbross Owned by:
Priority: major Milestone: VVC D10
Component: spec Version: VVC D9 vB
Keywords: Cc: ksuehring, bbross, XiangLi, fbossen, jvet@…


In SPS, the SDH flag is parsed conditioned on the DQ flag.

  if( !sps_dep_quant_enabled_flag )

If not present, the SDH flag is inferred to be equal to 1:
In SH there is a similar condition:

   if( sps_dep_quant_enabled_flag )
 if( sps_sign_data_hiding_enabled_flag   &&  !sh_dep_quant_enabled_flag )

At the Brussels meeting, it was decided to introduce that condition at the PH level (now SH) only, which makes sense.

"It was noted that dependent quantization can only be switched off at the PH level, whereas most coding tools can be disabled at a higher level. Decision (cleanup): Add an enable flag in the SPS, constrain the SPS flag according to the general_constraint flag, and condition the presence of the PH flag on the enable flag (and there are no other flags in other places). And do basically the same thing for sign data hiding. In the PH, don’t send the sign data hiding flag if the dependent quantization flag is 1."

The SPS conditioning was added by mistake during integration and should be removed in both spec and SW.

Change history (3)

comment:1 Changed 4 years ago by jonathang

To clarify:
Does this ticket assert that original design intention is reflected by replacing the SPS spec text

if( !sps_dep_quant_enabled_flag )



comment:2 Changed 4 years ago by bbross

Good point Jonathan, I forget to describe the fix and what you are suggesting is reflecting the original intent.

comment:3 Changed 4 years ago by bbross

  • Resolution set to fixed
  • Status changed from new to closed

This will be fixed in JVET-S2001-v7.

Note: See TracTickets for help on using tickets.