Opened 10 months ago
Last modified 7 months ago
#1629 new defect
mtt_split_cu_vertical_flag context uses undefined variable chType
Reported by: | peterderivaz | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | H.266/VVC v4 |
Component: | spec | Version: | H.266/VVC v3 |
Keywords: | Cc: | ksuehring, bbross, XiangLi, fbossen, jvet@… |
Description
The context derivation for mtt_split_cu_vertical_flag says it has an input of "the dual tree channel type chType" but it is not clear where this comes from.
mtt_split_cu_vertical_flag is read in the coding tree syntax which does not mention chType.
chType is mentioned in a different clause (the coding unit syntax), but it seems unlikely this is the value to be used because it has an apparent dependency on mtt_split_cu_vertical_flag via:
- mtt_split_cu_vertical_flag is used to compute MttSplitMode
- MttSplitMode is used to compute ModeTypeCondition
- ModeTypeCondition is used to compute modeType
- modeType is used to compute treeType
- treeType is used to compute chType.
What value should be used for chType when reading the mtt_split_cu_vertical_flag syntax element?
Change history (1)
comment:1 Changed 7 months ago by bbross
- Milestone set to H.266/VVC v4
- Version set to H.266/VVC v3
Note: See TracTickets for help on using tickets.
Thanks and this needs indeed clarification. Will look for a solution and update the post when I have cone up with one.