1. 17 May, 2016 1 commit
  2. 04 May, 2016 1 commit
  3. 26 Feb, 2016 5 commits
  4. 22 Feb, 2016 1 commit
  5. 26 Oct, 2015 1 commit
  6. 02 May, 2015 2 commits
  7. 08 Mar, 2015 1 commit
  8. 14 Feb, 2015 1 commit
  9. 18 Dec, 2014 1 commit
  10. 17 Oct, 2014 1 commit
  11. 08 Oct, 2014 1 commit
  12. 07 Jul, 2013 2 commits
  13. 11 Apr, 2013 1 commit
  14. 07 Mar, 2013 1 commit
  15. 04 Jan, 2013 1 commit
  16. 02 Dec, 2012 1 commit
  17. 12 Oct, 2012 1 commit
  18. 08 Oct, 2012 1 commit
  19. 03 Oct, 2012 1 commit
  20. 01 Oct, 2012 1 commit
  21. 30 Aug, 2012 1 commit
  22. 27 Aug, 2012 1 commit
  23. 19 Aug, 2012 4 commits
  24. 18 Aug, 2012 1 commit
  25. 13 Aug, 2012 2 commits
  26. 07 Aug, 2012 1 commit
  27. 29 Jul, 2012 1 commit
    • 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
  28. 28 Jul, 2012 1 commit
  29. 05 Jun, 2012 1 commit
  30. 29 May, 2012 1 commit