git.videolan.org Git - ffmpeg.git/rss log

Les articles publiés sur le site

• avcodec/ppc/mpegvideo_altivec : Don't process coeffs as scalars

  22 mars, par Andreas Rheinhardt

  avcodec/ppc/mpegvideo_altivec: Don't process coeffs as scalars
  
  block_last_index and nCoeffs is an optimization designed
  to avoid processing unnecessarily many coefficients; yet
  it would be legal to always process all coefficients
  (all coefficients beyond nCoeffs are zero anyway and
  zeros are always unquantized to zeros). Therefore
  one does not need a scalar tail.
  
  Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/ppc/mpegvideo_altivec.c

• avcodec/ppc/mpegvideo_altivec : Don't process unnecessarily many coeffs

  22 mars, par Andreas Rheinhardt

  avcodec/ppc/mpegvideo_altivec: Don't process unnecessarily many coeffs
  
  Use the same number as the C version.
  
  Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/ppc/mpegvideo_altivec.c

• avcodec/ppc/mpegvideo_altivec : Use correct inter scantable

  22 mars, par Andreas Rheinhardt

  avcodec/ppc/mpegvideo_altivec: Use correct inter scantable
  
  This affected the WMV1/2 encoders (but not when running FATE because
  the encoding part uses the fastint dct, so this code isn't used
  then anyway).
  
  It did not affect anything else, because a) only WMV1/2 use different
  scantables, b) ff_msmpeg4_decode_block() (and therefore the WMV1
  decoder) already unquantize inter macroblocks as they are parsed
  c) the WMV2 decoder does not use the unquantize functions for inter
  macroblocks at all.
  
  Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/ppc/mpegvideo_altivec.c

• avcodec/ppc/mpegvideo_altivec : Set unquantize functions unconditionally

  22 mars, par Andreas Rheinhardt

  avcodec/ppc/mpegvideo_altivec: Set unquantize functions unconditionally
  
  Don't do it depending upon dct_algo, as this is not supposed
  to influence the unquantize function selection.
  (This check originated in 05c4072b45f3cde1185de6eccfe7febf91d9f8fd
  where it was used for the dct_quantize function only.)
  
  Signed-off-by: Andreas Rheinhardt <andreas.rheinhardt@outlook.com>
  

  • [DH] libavcodec/ppc/mpegvideo_altivec.c

• checkasm : Implement helpers for defining and checking padded rects

  21 mars, par Martin Storsjö

  checkasm: Implement helpers for defining and checking padded rects
  
  This backports similar functionality from dav1d, from commits
  35d1d011fda4a92bcaf42d30ed137583b27d7f6d and
  d130da9c315d5a1d3968d278bbee2238ad9051e7.
  
  This allows detecting writes out of bounds, on all 4 sides of
  the intended destination rectangle.
  
  The bounds checking also can optionally allow small overwrites
  (up to a specified alignment), while still checking for larger
  overwrites past the intended allowed region.
  
  Signed-off-by: Martin Storsjö <martin@martin.st>
  

  • [DH] tests/checkasm/checkasm.c
  • [DH] tests/checkasm/checkasm.h