Custom Query (1442 matches)
Results (31 - 33 of 1442)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#302 | fixed | Proofreading issues | bbross | eugene.kuznetsov |
Description |
A few minor proofreading issues I found in WD9. Section 8.4.2.1.6 (p.127): incorrect references: it refers to 8.4.2.1.6, 8.4.2.1.7, and 8.4.2.1.10; it should say 8.4.2.1.7, 8.4.2.1.8, and 8.4.2.1.9 Variable yA1 is defined differently in 8.4.2.1.2 and 8.4.2.1.7 (as yP+nPSH-1 and yP+nPSH-MinPuSize); is there a practical difference between the two definitions?
8.4.2.2.2 (8-95) and (8-96) should be referring to mvCLX instead of mvLX 8.4.3.1 (page 141) if InterTUSplitDirection is equal to 2, yB1 and xB2 are undefined 8.4.3.1 (page 142) and 8.4.3.2 (page 143): "– The variable log2TrafoWidth1 is set equal to (log2TrafoWidth – 2) * InterTUSplitDirection. – The variable log2TrafoHeight1 is set equal to (log2TrafoHeight - 2) * (1 - InterTUSplitDirection)." Should be: "– The variable log2TrafoWidth1 is set equal to log2TrafoWidth – 2 * InterTUSplitDirection. – The variable log2TrafoHeight1 is set equal to log2TrafoHeight - 2 * (1 - InterTUSplitDirection)." |
|||
#303 | fixed | Table 1.1 – Structure of Tools in HM5 Configurations inaccurate | bbross | rkaliski |
Description |
Table 1.1 does not accurately reflect the configurations tested. LM Chroma is not used in Low Complexity configuration. The field "Chroma intra prediction separate from or using luma samples" is unclear as to chroma intra-prediction. Suggest this field be divided into two sections, one for high efficiency and one for low complexity. In High Efficiency use "Chroma intra prediction separate from or using luma samples", in Low Complexity "Chroma intra prediction separate from luma samples" |
|||
#304 | fixed | in the AMVP list derivation the scaled MVP can overwrite non-scaled MVP on top when the left side is mepty | bbross | zhou |
Description |
Solution:
Replace
With
|