Opened 3 months ago

Last modified 3 months ago

#429 new defect

Mismatch with spec on allow binary/ternary split process

Reported by: forayr Owned by:
Priority: minor Milestone:
Component: spec Version: VVC D6 vE
Keywords: Cc: ksuehring, XiangLi, fbossen, jvet@…

Description

In the specification, this processes use MaxBtSizeY, which is now variable. Whereas in the function canSplit in the VTM, the constant MAX_TB_SIZEY is used, instead of the variable value present in the sps.

Change history (5)

comment:2 Changed 3 months ago by adamjw

As far as I remember, this constraint is not really directly connected to the actual allowed MaxTbSize, but rather the VPDU size (which is fixed as 64, or MAX_TB_SIZEY). So I think the software actually represents the intended behavior and this should be fixed in the spec to match 64.
The canSplit function for TU_MAX_TR_SPLIT correctly respects the now variable maximal transform size, so if a block is larger than the maximal allowed transform size, it would be sub-split into smaller TUs. There is no reason to restrict BT/TT splits depending on maximal allowed transform size.

Last edited 3 months ago by adamjw (previous) (diff)

comment:3 follow-up: Changed 3 months ago by bbross

  • Version changed from VTM-5.2 to VVC D6 vE

Changing the ticket to spec since the spec should be changed as follows:

In "6.4.2 Allowed binary split process", replace "MaxTbSizeY" with the VPDU size 64.

comment:4 Changed 3 months ago by forayr

  • Component changed from VTM to spec

comment:5 in reply to: ↑ 3 Changed 3 months ago by adamjw

Replying to bbross:

Changing the ticket to spec since the spec should be changed as follows:

In "6.4.2 Allowed binary split process", replace "MaxTbSizeY" with the VPDU size 64.

The same should be done "6.4.3 Allowed ternary split process"

Note: See TracTickets for help on using tickets.