FFmpeg/tests/ref/fate/h264-conformance-sharp_mp_paff_1r2

#tb 0: 1/25
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 720x480
#sar 0: 0/1
0,          0,          0,        1,   518400, 0xc93c7c47
0,          1,          1,        1,   518400, 0xfb452a9c
0,          3,          3,        1,   518400, 0x2f7a35bd
0,          4,          4,        1,   518400, 0xe63e30b9
0,          5,          5,        1,   518400, 0x39628205
0,          6,          6,        1,   518400, 0x17fa1ea4
0,          7,          7,        1,   518400, 0xd5ee83e2
0,          8,          8,        1,   518400, 0x611ee98d
0,          9,          9,        1,   518400, 0x07c1eeb8
0,         10,         10,        1,   518400, 0x9dff3418
0,         11,         11,        1,   518400, 0x87cd2f56
0,         12,         12,        1,   518400, 0x88675628
0,         13,         13,        1,   518400, 0x9bb8c9a0
0,         14,         14,        1,   518400, 0xe6c1df00
0,         15,         15,        1,   518400, 0xfcaab7a7
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: 1/25`
avformat/framecrc: enable new output Reviewed-by: Michael Niedermayer <michael@niedermayer.cc> Signed-off-by: James Almer <jamrial@gmail.com> 2016-04-13 16:18:59 +02:00			`#media_type 0: video`
			`#codec_id 0: rawvideo`
			`#dimensions 0: 720x480`
			`#sar 0: 0/1`
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, 0, 0, 1, 518400, 0xc93c7c47`
			`0, 1, 1, 1, 518400, 0xfb452a9c`
tests: stop using -vsync drop It depends on the muxer generating the timestamps, which is deprecated and scheduled for removal on next bump. A bunch of tests change timestamps, because of ffmpeg.c is not generating them correctly. This should be fixed later. 2020-11-30 15:13:51 +02:00			`0, 3, 3, 1, 518400, 0x2f7a35bd`
			`0, 4, 4, 1, 518400, 0xe63e30b9`
			`0, 5, 5, 1, 518400, 0x39628205`
			`0, 6, 6, 1, 518400, 0x17fa1ea4`
			`0, 7, 7, 1, 518400, 0xd5ee83e2`
			`0, 8, 8, 1, 518400, 0x611ee98d`
			`0, 9, 9, 1, 518400, 0x07c1eeb8`
			`0, 10, 10, 1, 518400, 0x9dff3418`
			`0, 11, 11, 1, 518400, 0x87cd2f56`
			`0, 12, 12, 1, 518400, 0x88675628`
			`0, 13, 13, 1, 518400, 0x9bb8c9a0`
			`0, 14, 14, 1, 518400, 0xe6c1df00`
			`0, 15, 15, 1, 518400, 0xfcaab7a7`