FFmpeg/tests/ref/fate/mpeg2-ticket6677

#tb 0: 1/30
#media_type 0: video
#codec_id 0: rawvideo
#dimensions 0: 720x480
#sar 0: 8/9
0,          1,          1,        1,   518400, 0xc1866f5f
0,          2,          2,        1,   518400, 0x9ba32764
0,          4,          4,        1,   518400, 0xa9031bb8
0,          5,          5,        1,   518400, 0x5e2c3502
0,          6,          6,        1,   518400, 0xe860027a
0,          7,          7,        1,   518400, 0xa9152430
0,          9,          9,        1,   518400, 0xb98dd9f7
fate: add a test for mpeg2 issue of ticket #6677 Signed-off-by: Zhong Li <zhong.li@intel.com> Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> 2017-10-23 09:18:12 +02:00			`#tb 0: 1/30`
			`#media_type 0: video`
			`#codec_id 0: rawvideo`
			`#dimensions 0: 720x480`
			`#sar 0: 8/9`
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, 1, 1, 1, 518400, 0xc1866f5f`
			`0, 2, 2, 1, 518400, 0x9ba32764`
			`0, 4, 4, 1, 518400, 0xa9031bb8`
			`0, 5, 5, 1, 518400, 0x5e2c3502`
			`0, 6, 6, 1, 518400, 0xe860027a`
			`0, 7, 7, 1, 518400, 0xa9152430`
			`0, 9, 9, 1, 518400, 0xb98dd9f7`