1. 04 Sep, 2012 1 commit
    • Michael Niedermayer's avatar
      adpcmenc: Calculate the IMA_QT predictor without overflow · aa264da5
      Michael Niedermayer authored
      Previously, the value given to put_bits was 10 bits long for positive
      predictors, even though 9 bits were to be written. The extra bit could
      in some cases overwrite existing bits in the bitstream writer cache.
      
      This fixes a failed assert in put_bits.h, when running a version
      built with -DDEBUG.
      
      The fate test result gets slightly improved, thanks to getting rid
      of the overwritten bits in the bitstream writer cache.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
      aa264da5
  2. 30 Aug, 2012 1 commit
  3. 28 Aug, 2012 1 commit
  4. 26 Aug, 2012 1 commit
  5. 25 Aug, 2012 1 commit
  6. 22 Aug, 2012 1 commit
  7. 21 Aug, 2012 2 commits
  8. 20 Aug, 2012 2 commits
  9. 11 Aug, 2012 1 commit
  10. 10 Aug, 2012 1 commit
  11. 09 Aug, 2012 1 commit
  12. 08 Aug, 2012 1 commit
  13. 06 Aug, 2012 1 commit
  14. 04 Aug, 2012 2 commits
  15. 29 Jul, 2012 4 commits
    • Mans Rullgard's avatar
      70c8753d
    • Mans Rullgard's avatar
      tiny_psnr: support 32-bit float samples · 9f1280de
      Mans Rullgard authored
      Signed-off-by: default avatarMans Rullgard <mans@mansr.com>
      9f1280de
    • Anton Khirnov's avatar
      lavf: deprecate r_frame_rate. · aba232cf
      Anton Khirnov authored
      According to its description, it is supposed to be the LCM of all the
      frame durations. The usability of such a thing is vanishingly small,
      especially since we cannot determine it with any amount of reliability.
      Therefore get rid of it after the next bump.
      
      Replace it with the average framerate where it makes sense.
      
      FATE results for the wtv and xmv demux tests change. In the wtv case
      this is caused by the file being corrupted (or possibly badly cut) and
      containing invalid timestamps. This results in lavf estimating the
      framerate wrong and making up wrong frame durations.
      In the xmv case the file contains pts jumps, so again the estimated
      framerate is far from anything sane and lavf again makes up different
      frame durations.
      
      In some other tests lavf starts making up frame durations from different
      frame.
      aba232cf
    • Anton Khirnov's avatar
      lavf: use dts difference instead of AVPacket.duration in find_stream_info() · fe1c1198
      Anton Khirnov authored
      AVPacket.duration is mostly made up and thus completely useless, this is
      especially true for video streams.
      Therefore use dts difference for framerate estimation and
      the max_analyze_duration check.
      
      The asyncts test now needs -analyzeduration, because the default is 5
      seconds and the audio stream in the sample appears at ~10 seconds.
      fe1c1198
  16. 28 Jul, 2012 5 commits
  17. 26 Jul, 2012 1 commit
  18. 23 Jul, 2012 1 commit
  19. 22 Jul, 2012 2 commits
  20. 20 Jul, 2012 1 commit
  21. 14 Jul, 2012 2 commits
  22. 09 Jul, 2012 1 commit
  23. 04 Jul, 2012 6 commits