1. 08 Dec, 2017 1 commit
  2. 12 Sep, 2017 1 commit
  3. 20 Aug, 2017 1 commit
  4. 30 Jul, 2017 1 commit
  5. 24 Jun, 2017 1 commit
    • James Almer's avatar
      fate: update checksums for fate-lavf-ffm and fate-lavf-mxf · e5bce8b4
      James Almer authored
      <@jamrial> durandal_1707: 04aa09c4 broke fate-lavf-ffm and fate-lavf-mxf
      <@durandal_1707> how so?
      <@jamrial> one byte changes
      <@durandal_1707> jamrial: just update checksums
      <@jamrial> durandal_1707: but why did they change at all? the commit you reverted didn't affect them
      <@jamrial> why does reverting it affect these tests?
      <@jamrial> i don't think updating the checksum without knowing what changed is a good idea
      <@durandal_1707> jamrial: the lavfi core is in weird state after removal of recursive code
      <@durandal_1707> jamrial: the change is that older ones would get progressive flag set and new one doesnt
      <@jamrial> alright
      e5bce8b4
  6. 16 Mar, 2017 1 commit
  7. 08 Mar, 2017 1 commit
  8. 03 Mar, 2017 1 commit
    • Anton Khirnov's avatar
      ffmpeg: init filtergraphs only after we have a frame on each input · af1761f7
      Anton Khirnov authored
      This makes sure the actual stream parameters are used, which is
      important mainly for hardware decoding+filtering cases, which would
      previously require various weird workarounds to handle the fact that a
      fake software graph has to be constructed, but never used.
      This should also improve behaviour in rare cases where
      avformat_find_stream_info() does not provide accurate information.
      
      This merges Libav commit a3a0230a. It was previously skipped.
      
      The code in flush_encoders() which sets up a "fake" format wasn't in
      Libav. I'm not sure if it's a good idea, but it tends to give
      behavior closer to the old one in certain corner cases.
      
      The vp8-size-change gives different result, because now the size of
      the first frame is used. libavformat reported the size of the largest
      frame for some reason.
      
      The exr tests now use the sample aspect ratio of the first frame. For
      some reason libavformat determines 0/1 as aspect ratio, while the
      decoder returns the correct one.
      
      The ffm and mxf tests change the field_order values. I'm assuming
      another libavformat/decoding mismatch.
      Signed-off-by: 's avatarwm4 <nfxjfg@googlemail.com>
      af1761f7
  9. 01 Feb, 2016 1 commit
  10. 10 Nov, 2015 1 commit
  11. 01 Jun, 2015 1 commit
  12. 28 May, 2015 1 commit
  13. 22 May, 2015 1 commit
  14. 30 Mar, 2015 1 commit
  15. 23 Mar, 2015 1 commit
  16. 15 Mar, 2015 1 commit
  17. 10 Mar, 2015 1 commit
  18. 25 Oct, 2014 1 commit
  19. 06 Jun, 2014 2 commits
  20. 01 Apr, 2014 1 commit
  21. 07 Aug, 2013 1 commit
  22. 08 Jan, 2013 1 commit
  23. 04 Jan, 2013 1 commit
    • Alexander Strasser's avatar
      lswr: Improve default resampler's default parameters · ac25b31e
      Alexander Strasser authored
      After making some blind tests on a small collection of music
      samples for home usage. It turned out that the default cutoff
      was too low.
      
      The impact of filter_size was not clearly distinguishable (the
      results were on the edge) with the music samples but turned out
      to be clearly audible in some synthetic samples.
      
      Thanks to Daniel for helping out with the listening tests.
      Signed-off-by: 's avatarAlexander Strasser <eclipse7@gmx.net>
      ac25b31e
  24. 16 Nov, 2012 1 commit
  25. 26 Oct, 2012 1 commit
  26. 25 Oct, 2012 1 commit
  27. 27 Sep, 2012 1 commit
  28. 11 Aug, 2012 1 commit
  29. 04 Jul, 2012 1 commit
    • Nicolas George's avatar
      ffmpeg: rework checks for the -t option. · 2fc354f9
      Nicolas George authored
      This commit is based on libav's implementation and
      makes sure to compare output timestamps together.
      It also reduces the differences with avconv.
      
      The changes to the test reference files are caused
      by an additional packet at the end, the timestamp
      of the frame encoded by this packet is always
      strictly below the limit stated by the -t option.
      2fc354f9
  30. 06 Jun, 2012 1 commit
  31. 20 Apr, 2012 1 commit
  32. 02 Feb, 2012 1 commit
  33. 17 Jul, 2011 1 commit
  34. 17 Apr, 2011 2 commits
  35. 12 Apr, 2011 1 commit
  36. 02 Jul, 2010 1 commit
  37. 02 Apr, 2010 1 commit
  38. 02 Mar, 2010 1 commit