Custom Query (1442 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (40 - 42 of 1442)

Ticket Resolution Summary Owner Reporter
#1208 fixed 8.4.5.1 Uses incorrect coordinate system for various syntax elements davidf
Description

The following elements are all defined in terms of luma coordinates in syntax/semantics:

  • transform_skip_flag
  • explicit_rdpcm_flag
  • explicit_rdpcm_dir_flag

But in 8.4.5.1 are indexed using the component dependent coordinate system (xTb0, yTb0).

Use (xTbY, yTbY + yTbOffset * SubHeightC) as appropriate.

#1234 fixed 8.4.5.1 uses incorrect coordinate system assigning to xTb1 and yTb1 jackh
Description

Following on from ticket #1208, I think the following section in 8.4.5.1:

  1. The variables xTb1 and yTb1 are derived as follows:

– The variable xTb1 is set equal to xTb0 + ( 1 << ( log2TrafoSize − 1 ) ). – The variable yTb1 is set equal to yTb0 + ( 1 << ( log2TrafoSize − 1 ) ).

should say:

  1. The variables xTb1 and yTb1 are derived as follows:

– The variable xTb1 is set equal to xTb0 + ( ( 1 << ( log2TrafoSize ) ) / SubWidthC ). – The variable yTb1 is set equal to yTb0 + ( ( 1 << ( log2TrafoSize ) ) / SubHeightC ).

as xTb1 and yTb1 are in chroma coordinates.

#704 duplicate 8.5.2.1.3 combIdx is not initialized bbross conrad.ho
Description

combIdx is used but is not initialized beforehand.

Suggestion:
When numOrigMergeCand is greater than 1 and less than MaxNumMergeCand, the variable numInputMergeCand is set to numMergeCand, the variable combIdx is set to 0, the variable combStop is set to FALSE and the following steps are repeated until combStop is equal to TRUE.

Note: See TracQuery for help on using queries.