Custom query (105 matches)

Filters
 
or
 
  
 
Columns

Show under each result:


Results (31 - 33 of 105)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Ticket Resolution Summary Owner Reporter
#76 fixed TComDataCU::getBaseColCU has signed/unsigned error Vadim johnnyVidyo
Description

The following bit of code in function TComDataCU::getBaseColCU does not handle negative values properly.

  Int iBX = (((uiPelX - leftStartL)*g_posScalingFactor[refLayerIdc][0] + (1<<15)) >> 16) + windowRL.getWindowLeftOffset();
  Int iBY = (((uiPelY - topStartL )*g_posScalingFactor[refLayerIdc][1] + (1<<15)) >> 16) + windowRL.getWindowTopOffset();

The unsigned variables, uiPelX and uiPelY, need to be cast to signed variables as follows.

  Int iBX = ((((Int)uiPelX - leftStartL)*g_posScalingFactor[refLayerIdc][0] + (1<<15)) >> 16) + windowRL.getWindowLeftOffset();
  Int iBY = ((((Int)uiPelY - topStartL )*g_posScalingFactor[refLayerIdc][1] + (1<<15)) >> 16) + windowRL.getWindowTopOffset();
#75 fixed Semantics of max_vps_dec_pic_buffering_minus1 jlchen Vadim
Description

max_vps_dec_pic_buffering_minus1[ i ][ k ][ j ] plus 1, when NecessaryLayerFlag[ i ][ k ] is equal to 1, specifies the maximum number of decoded pictures, of the k-th layer for the CVS in the i-th OLS, that need to be stored in the DPB when HighestTid is equal to j.

Semantics is ambiguous when saying "k-th layer for the CVS in the i-th OLS". It can be understood as a layer with index k in CVS in the i-th OLS, however it is a layer with index k, where the k is the index within layers included into i-th OLS.

Probably, "for the CVS" can be removed or moved after OLS.

#74 fixed Wrong layer ID is used in multiple places Vadim eeehey
Description

layer ID, instead of layer index, is mistakenly used in multiple places such as m_acLayerCfg, m_EhGOPList, m_extraRPSs, affectedLayerList, getLayerEnc(), m_ppcTEncTop, m_acTEncTop. Patch attached.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Note: See TracQuery for help on using queries.