Chiebot-Mirror/FFmpeg - FFmpeg - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Anton Khirnov	74b961db77	avconv: replace -vsync cfr code with the fps filter. Invented timestamps for the h264 tests return to something resembling sanity. In the idroq-video-encode test when converting 25 fps -> 30 fps the fifth frame gets duplicated instead of the sixth.	13 years ago
Anton Khirnov	755cd4197d	mov: enable parsing for VC-1. This makes lavf discard broken timestamps for non-B frames in samples/isom/vc1-wmapro.ism.	13 years ago
Mans Rullgard	4f1500689d	avconv: use lrint() for rounding double timestamps Converting the double to float for lrintf() loses precision when the value is not exactly representable as a single-precision float. Apart from being inaccurate, this causes discrepancies in some configurations due to differences in rounding. Note that the changed timestamp in the vc1-ism test is a bogus, made-up value. Signed-off-by: Mans Rullgard <mans@mansr.com>	13 years ago
Anton Khirnov	7929e22bde	lavf: don't guess r_frame_rate from either stream or codec timebase. Neither of those is guaranteed to be connected to framerate in any way (if it even exists). Fixes bug 56.	13 years ago
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`	13 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.	13 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.	13 years ago
Alex Converse	cd6e34d369	fate: Add tests for vc1/wmapro in ism.	13 years ago