FFmpeg

2.4GB

Tree: 00a63bfb87

Author	SHA1	Message	Date
Anton Khirnov	832ba44d8d	avconv: saner output video timebase. 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 `cd1ad18a65`	14 years ago
Anton Khirnov	cd1ad18a65	rawenc: switch to encode2(). 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.	14 years ago
Anton Khirnov	d2afbd9a56	frame{crc/md5}: set the stream timebase from codec timebase. 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.	14 years ago
Anssi Hannula	7c152a458d	lavf: inspect more frames for fps when container time base is coarse As per issue2629, most 23.976fps matroska H.264 files are incorrectly detected as 24fps, as the matroska timestamps usually have only millisecond precision. Fix that by doubling the amount of timestamps inspected for frame rate for streams that have coarse time base. This also fixes 29.970 detection in matroska. Signed-off-by: Michael Niedermayer <michaelni@gmx.at> (cherry picked from commit `78431098f9`) Tested with mplayer based on this report http://thread.gmane.org/gmane.comp.video.mplayer.user/66043/focus=66063 Signed-off-by: Reinhard Tartler <siretart@tauware.de>	15 years ago
Måns Rullgård	2fad097788	Add FATE tests 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	16 years ago

5 Commits (00a63bfb87af6cf7bcdf85848830a90c7e052d41)