FFmpeg/tests/ref/fate/apng-osample

#tb 0: 3/50
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 116x135
#sar 0: 0/1
0,          0,          0,        3,    62640, 0x31eb581d
0,          3,          3,        3,    62640, 0x29e11b82
0,          6,          6,        3,    62640, 0x207ed588
0,          9,          9,        3,    62640, 0x3845c906
0,         12,         12,        3,    62640, 0x6797fe69
0,         15,         15,        3,    62640, 0x1f086a09
fate/apng : add test for apng decoding Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> 2016-07-02 17:48:45 +02:00			`#tb 0: 3/50`
			`#media_type 0: video`
			`#codec_id 0: rawvideo`
			`#dimensions 0: 116x135`
			`#sar 0: 0/1`
fftools/ffmpeg_enc: avoid breaking exactly integer timestamps in vsync code The code will currently add a small offset to avoid exact midpoints, but this can cause inexact results when a float timestamp is exactly representable as an integer. Fixes off-by-one in the first frame duration in multiple FATE tests. 2023-05-28 16:22:58 +02:00			`0, 0, 0, 3, 62640, 0x31eb581d`
fftools/ffmpeg: propagate frame durations to packets when encoding Remove now-obsolete code setting packet durations pre-muxing for CFR encoded video. Changes output in the following FATE tests: * numerous adpcm tests * ffmpeg-filter_complex_audio * lavf-asf * lavf-mkv * lavf-mkv_attachment * matroska-encoding-delay All of these change due to the fact that the output duration is now the actual input data duration and does not include padding added by the encoder. * apng-osample: less wrong packet durations are now passed to the muxer. They are not entirely correct, because the first frame duration should be 3 rather than 2. This is caused by the vsync code and should be addressed later, but this change is a step in the right direction. * tscc2-mov: last output frame has a duration of 11 rather than 1 - this corresponds to the duration actually returned by the demuxer. * film-cvid: video frame durations are now 2 rather than 1 - this corresponds to durations actually returned by the demuxer and matches the timestamps. * mpeg2-ticket6677: durations of some video frames are now 2 rather than 1 - this matches the timestamps. 2023-04-14 11:16:02 +02:00			`0, 3, 3, 3, 62640, 0x29e11b82`
			`0, 6, 6, 3, 62640, 0x207ed588`
			`0, 9, 9, 3, 62640, 0x3845c906`
			`0, 12, 12, 3, 62640, 0x6797fe69`
			`0, 15, 15, 3, 62640, 0x1f086a09`