Opened 4 years ago

Closed 4 years ago

#1010 closed defect (fixed)

Spec and VTM mismatch on chroma QT split at picture boundary

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

Description

In VTM-8.0, when x0 + cbWidth is greater than pic_width_in_luma_samples and y0 + cbHeight is greater than pic_height_in_luma_samples and cbWidth is equal to MinQtSizeC in the chroma tree, quad split is derived as implicit split. But in the VVC draft 8, both horizontal binary split and quad split are allowed.

If align spec with VTM, the text change is as follows, with added text highlighted:

– if all of the following conditions are true, allowBtSplit is set equal to FALSE

– x0 + cbWidth is greater than pic_width_in_luma_samples
– y0 + cbHeight is greater than pic_height_in_luma_samples
– cbWidth is greater than minQtSize and treeType is not equal to DUAL_TREE_CHROMA

– if all of the following conditions are true, allowBtSplit is set equal to FALSE

– x0 + cbWidth is greater than pic_width_in_luma_samples
– y0 + cbHeight is greater than pic_height_in_luma_samples
– cbWidth is greater than (minQtSize* SubHeightC / SubWidthC) and treeType is equal to DUAL_TREE_CHROMA


Change history (3)

comment:1 follow-up: Changed 4 years ago by bbross

  • Milestone set to VVC D10
  • Version changed from VVC D8 vB to VVC D9 vB

Thanks for reporting!

Can someone confirm the suggested fix?

comment:2 in reply to: ↑ 1 Changed 4 years ago by hanhuang

This is solved by adoption of JVET-R0131.
Replying to bbross:

Thanks for reporting!

Can someone confirm the suggested fix?

comment:3 Changed 4 years ago by bbross

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

Thanks so this is fixed in D9.

Note: See TracTickets for help on using tickets.