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

Author	SHA1	Message	Date
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
Reimar Döffinger	05741d70c7	Fallback to input timestamps for non-delay encoders. Causes FFmpeg to pass through the correct pts values, instead of clobbering all to AV_NOPTS_VALUE (the av_init_packet default) to then make up new ones based on only fps when muxing. Included are also the related FATE ref changes, which all some reasonable on quick investigation. Also set all H.264 references to us -vsync drop to reduce the diff for the ref files. Otherwise almost all H.264 references need to change, mostly due to now starting with negative pts values. About 20 additional H.264 conformance tests needed -vsync drop anyway because they create pts values that are out of order and thus not possible to mux otherwise. Signed-off-by: Reimar Döffinger <Reimar.Doeffinger@gmx.de>	13 years ago
Michael Niedermayer	8f5bb35f40	ffmpeg: fix video synchronization code to be exact on constant fps videos. Fixes Ticket137 Signed-off-by: Michael Niedermayer <michaelni@gmx.at>	13 years ago
Vitor Sessak	a58ed9a2e7	Add VP8 sign bias code regtest. Not tested by the official conformance suite. Originally committed as revision 24457 to svn://svn.ffmpeg.org/ffmpeg/trunk	15 years ago