1. 12 6月, 2014 7 次提交
  2. 11 6月, 2014 7 次提交
  3. 10 6月, 2014 2 次提交
    • M
      x86: h264: Don't keep data in the redzone across function calls on 64 bit unix · 570d4b21
      Martin Storsjö 提交于
      We know that the called function (ff_chroma_inter_body_mmxext)
      doesn't touch the redzone, and thus will be kept intact - thus,
      this doesn't fix any bug per se.
      
      However, valgrind's memcheck tool intentionally assumes that the
      redzone is clobbered on every function call and function return
      (see a long comment in valgrind/memcheck/mc_main.c). This avoids
      false positives in that tool, at the cost of an extra stack pointer
      adjustment.
      
      The other alternative would be a valgrind suppression for this issue,
      but that's an extra burden for everybody that wants to run libavcodec
      within valgrind.
      Signed-off-by: NMartin Storsjö <martin@martin.st>
      570d4b21
    • M
      adpcm: Write the proper predictor in trellis mode in IMA QT · 0776e0ef
      Martin Storsjö 提交于
      The actual predictor value, set by the trellis code, never
      was written back into the variable that was written into
      the block header. This was accidentally removed in b304244b.
      
      This significantly improves the audio quality of the trellis
      case, which was plain broken since b304244b.
      
      Encoding IMA QT with trellis still actually gives a slightly
      worse quality than without trellis, since the trellis encoder
      doesn't use the exact same way of rounding as in
      adpcm_ima_qt_compress_sample and adpcm_ima_qt_expand_nibble.
      
      CC: libav-stable@libav.org
      Signed-off-by: NMartin Storsjö <martin@martin.st>
      0776e0ef
  4. 09 6月, 2014 2 次提交
  5. 07 6月, 2014 2 次提交
  6. 06 6月, 2014 8 次提交
  7. 04 6月, 2014 2 次提交
  8. 03 6月, 2014 5 次提交
  9. 02 6月, 2014 5 次提交