Opened 3 years ago

Closed 3 years ago

#1461 closed defect (fixed)

Enabling chroma dQP does not exercise the feature as expected

Reported by: delagrangep Owned by:
Priority: minor Milestone: VTM-12.1
Component: VTM Version: VTM-11.2
Keywords: Cc: ksuehring, XiangLi, fbossen, jvet@…


When enabled, the chroma dQP index is exercised in EncCu::xCompressCU, by scanning all possible index values, depending on CU position. The local offset is stored in m_cuChromaQpOffsetIdxPlus1.
The value is set only when possible, i.e. when the CU is the first of a chroma QG. However just before checking that condition, m_cuChromaQpOffsetIdxPlus1 is always reset to zero. The consequence is a spurious reset of m_cuChromaQpOffsetIdxPlus1 for any QG that contains several CUs, defeating the purpose of the feature.
The solution is to move the m_cuChromaQpOffsetIdxPlus1=0 statement to an else branch of above-mentioned condition.

Change history (1)

comment:1 Changed 3 years ago by fbossen

  • Milestone set to VTM-12.1
  • Resolution set to fixed
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.