1. 13 Aug, 2013 1 commit
  2. 08 Aug, 2012 1 commit
  3. 29 Feb, 2012 1 commit
  4. 26 Feb, 2012 1 commit
    • Anton Khirnov's avatar
      avconv: saner output video timebase. · 832ba44d
      Anton Khirnov authored
      r_frame_rate should in theory have something to do with input framerate,
      but in practice it is often made up from thin air by lavf. So unless we
      are targeting a constant output framerate, it's better to just use input
      stream timebase.
      
      Brings back dropped frames in nuv and cscd tests introduced in
      cd1ad18a
      832ba44d
  5. 08 Feb, 2012 1 commit
    • Anton Khirnov's avatar
      rawenc: switch to encode2(). · cd1ad18a
      Anton Khirnov authored
      This changes a number of FATE results, since before this commit, the
      timestamps in all tests using rawenc were made up by lavf.
      
      In most cases, the previous timestamps were completely bogus.
      
      In some other cases -- raw formats, mostly h264 -- the new timestamps
      are bogus as well. The only difference is that timestamps invented by
      the muxer are replaced by timestamps invented by the demuxer.
      
      cscd     -- avconv sets output codec timebase from r_frame_rate
      and r_frame_rate is in this case some guessed number 31.42 (377/12),
      which is not accurate enough to represent all timestamps. This results
      in some frames having duplicate pts. Therefore, vsync 0 needs to be
      changed to vsync 2 and avconv drops two frames. A proper fix in the
      future would be to set output timebase to something saner in avconv.
      
      nuv      -- previous timestamps for video were wrong AND the cscd
      comment applies, one frame is dropped.
      
      vp8-signbias -- the file contains two frames with identical timestamps,
      so -vsync 0 needs to be removed/changed to -vsync 2 and avconv drops one
      frame.
      
      vc1-ism -- apparrently either the demuxer lies about timestamps or the
      file is broken, since dts == pts on all packets, but reordering clearly
      takes place.
      cd1ad18a
  6. 03 Feb, 2012 1 commit
    • Anton Khirnov's avatar
      frame{crc/md5}: set the stream timebase from codec timebase. · d2afbd9a
      Anton Khirnov authored
      Right now those muxers use the default timebase in all cases(1/90000).
      
      This patch avoid unnecessary rescaling and makes the printed timestamps
      more readable.
      
      Also, extend the printed information to include the timebases and packet
      pts/duration and align the columns.
      
      Obviously changes the results of all fate tests which use those two
      muxers.
      d2afbd9a
  7. 23 Nov, 2011 1 commit
    • Anton Khirnov's avatar
      crcenc: add flags · 0844b57c
      Anton Khirnov authored
      AVFMT_NOTIMESTAMPS for crc, as it ignores the timestamps.
      AVFMT_VARIABLE_FPS for framecrc, as it prints dts.
      
      Many FATE changes, because avconv is no longer duplicating frames in
      those tests.
      Also added -vsync 0 for some tests to prevent avconv from dropping
      frames until it can be fixed more properly.
      0844b57c
  8. 12 Apr, 2011 1 commit
  9. 15 Mar, 2010 1 commit
    • Måns Rullgård's avatar
      Add FATE tests · 2fad0977
      Måns Rullgård authored
      This adds a "fate" make target which runs the full FATE test suite.
      Individual tests can be run with "make fate-$testname".
      
      The location of the FATE test samples must be specified with the
      --samples=PATH option to configure.
      
      The tests/fate-update.sh script regenerates the references files and
      test list from the online FATE database.  These are checked in since
      generating them requires non-standard tools.
      
      Originally committed as revision 22552 to svn://svn.ffmpeg.org/ffmpeg/trunk
      2fad0977