virtualenv/FFmpeg
1
0
Fork 0
mirror of https://github.com/FFmpeg/FFmpeg.git synced 2024-12-02 03:06:28 +02:00
Code Issues Releases Activity
ec0f4fa17c
FFmpeg/tests/ref/fate/dfa4

15 lines
768 B
Plaintext
Raw Normal View History

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.
2012-02-02 16:20:43 +03:00
#tb 0: 71/500
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.
2012-02-01 17:33:51 +03:00
0, 1, 1, 1, 921600, 0xe6309638
0, 2, 2, 1, 921600, 0xa99a7665
0, 3, 3, 1, 921600, 0x172ccfbb
0, 4, 4, 1, 921600, 0xcf676571
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.
2012-02-02 16:20:43 +03:00
0, 5, 5, 1, 921600, 0x6a5077f2
0, 6, 6, 1, 921600, 0x6a5077f2
0, 7, 7, 1, 921600, 0x6a5077f2
0, 8, 8, 1, 921600, 0x6a5077f2
0, 9, 9, 1, 921600, 0x6a5077f2
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.
2012-02-01 17:33:51 +03:00
0, 10, 10, 1, 921600, 0x6a5077f2
0, 11, 11, 1, 921600, 0xb83db404
0, 12, 12, 1, 921600, 0x997ceb90
0, 13, 13, 1, 921600, 0xd707157c
Reference in New Issue Copy Permalink