Custom Query (1440 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (1 - 3 of 1440)

1 2 3 4 5 6 7 8 9 10 11
Ticket Resolution Summary Owner Reporter
#722 fixed 8.5.2.1.7 : Collocated derivation, Confusing reference to "every" reference picture list. bbross AlexisLefebvre
Description

In chapter 8.5.2.1.7, mvCol, refIdxCol and listCol are derived according to following sentence:

"If PicOrderCnt( pic ) of every picture pic in every reference picture lists is less than or equal to PicOrderCntVal"

"Every reference picture lists" may refer to 1) picture lists L0 and L1 associated to the current luma prediction block 2) picture lists L0 and L1 associated to the collocated luma prediction block

#729 fixed 7.4.5.4: Unclear LumaWeightLX / ChromaWeightLX range bbross AlexisLefebvre
Description

Hi, In chapter 8.5.2.2.3.2, weighted predictions is performed according to LumaWeightLX and ChromaWeightLX.

In chapter 7.4.5.4 those values are defined by:

"The variable LumaWeightL0[ i ] is specified by (1 << luma_log2_weight_denom ) + delta_luma_weight_l0[ i ]. When luma_weight_l0_flag[ i ] is equal to 1, the value of delta_luma_weight_l0[ i ] shall be in the range of −128 to 127, inclusive. When luma_weight_l0_flag[ i ] is equal to 0, LumaWeightL0[ i ] is inferred to be equal to 2luma_log2_weight_denom for RefPicList0[ i ]."

I suspect a typo here. Is the following more accurate ? :

"The variable LumaWeightL0[ i ] is specified by (1 << luma_log2_weight_denom ) + delta_luma_weight_l0[ i ]. When luma_weight_l0_flag[ i ] is equal to 1, the value of LumaWeightL0[ i ] shall be in the range of −128 to 127, inclusive. When luma_weight_l0_flag[ i ] is equal to 0, LumaWeightL0[ i ] is inferred to be equal to 2luma_log2_weight_denom for RefPicList0[ i ]."

Same remark for ChromaWeightLX definition. Regards, Alexis

#733 fixed 8.5.2.1.7 : Behavior when collocated PB cross right picture boundary. bbross AlexisLefebvre
Description

Hi, In chapter 8.5.2.1.7, the collocated coordinates are derived according to the vertical position "( yP >> Log2CtbSizeY ) is equal to ( yPRb >> Log2CtbSizeY )" to know whether to select central luma location or bottom-right luma location.

This force to work always with the same Ctb row in the collocated picture and in the current picture.

But it is not explained what to do when the collocated Pb cross the right picture boundary. For example the top-right Pb of the current Ctb can have its collocated Pb outside the picture boundary if the current Ctb is the last Ctb of a picture row and it respect the "( yP >> Log2CtbSizeY ) is equal to ( yPRb >> Log2CtbSizeY )" equation.

In this case I see 2 solutions : 1) Central luma location is used instead. 2) The collocated Pb is marked as unavailable.

Regards, Alexis

(Pb: prediction block, Ctb: coding tree block )

1 2 3 4 5 6 7 8 9 10 11
Note: See TracQuery for help on using queries.