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

#tb 0: 1/25
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 720x480
#sar 0: 0/1
0,          0,          0,        1,   518400, 0x80dffda2
0,          1,          1,        1,   518400, 0x9450183b
0,          2,          2,        1,   518400, 0x85d429a7
0,          3,          3,        1,   518400, 0xe1f3b686
0,          4,          4,        1,   518400, 0x2180c761
0,          5,          5,        1,   518400, 0x30269c7c
0,          6,          6,        1,   518400, 0xe9aa575a
0,          7,          7,        1,   518400, 0x7b815a0a
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, 0x80dffda2`
fftools/ffmpeg: stop using fake dts for generating timestamps When no packet dts values are available from the container, video decoding code will currently use its own guessed values, which will then be propagated to pkt_dts on decoded frames and used as pts in certain cases. This is inaccurate, fragile, and unnecessarily convoluted. Simply removing this allows the extrapolation code introduced in the previous commit to do a better job. Changes the results of numerous h264 and hevc FATE tests, where no spurious timestamp gaps are generated anymore. Several tests no longer need -vsync passthrough. 2023-04-09 15:01:29 +02:00			`0, 1, 1, 1, 518400, 0x9450183b`
			`0, 2, 2, 1, 518400, 0x85d429a7`
			`0, 3, 3, 1, 518400, 0xe1f3b686`
			`0, 4, 4, 1, 518400, 0x2180c761`
			`0, 5, 5, 1, 518400, 0x30269c7c`
			`0, 6, 6, 1, 518400, 0xe9aa575a`
			`0, 7, 7, 1, 518400, 0x7b815a0a`