ffmpeg/tests/ref/fate/vp8-sign-bias

0, 0, 614880, 12ce23b288485be3ddbc1db28c21517f
0, 7500, 614880, ce352e1079535ea058c0e9ad50f7cdb8
0, 11250, 614880, 9f6bf2739a027dfd12c81586cf75d3a3
0, 15000, 614880, 7593a85ab7790eb39d65fc53f769ed8b
0, 18750, 614880, 52f47f1e0348f3297d9f233fb5405e8b
0, 22500, 614880, cd51d2c200bfd66e8e1b0fd6b404570f
0, 26250, 614880, cf535cf0a53e903cd98a9a944b72da6d
0, 30000, 614880, 1b270fd2b56daa7892102c2885d23201
0, 33750, 614880, ff373c0c8a4a319c84e72b1c3d76b399
Add VP8 sign bias code regtest. Not tested by the official conformance suite. Originally committed as revision 24457 to svn://svn.ffmpeg.org/ffmpeg/trunk 2010-07-23 12:09:46 +02:00			`0, 0, 614880, 12ce23b288485be3ddbc1db28c21517f`
Fallback to input timestamps for non-delay encoders. Causes FFmpeg to pass through the correct pts values, instead of clobbering all to AV_NOPTS_VALUE (the av_init_packet default) to then make up new ones based on only fps when muxing. Included are also the related FATE ref changes, which all some reasonable on quick investigation. Also set all H.264 references to us -vsync drop to reduce the diff for the ref files. Otherwise almost all H.264 references need to change, mostly due to now starting with negative pts values. About 20 additional H.264 conformance tests needed -vsync drop anyway because they create pts values that are out of order and thus not possible to mux otherwise. Signed-off-by: Reimar Döffinger <Reimar.Doeffinger@gmx.de> 2012-01-22 11:23:47 +01:00			`0, 7500, 614880, ce352e1079535ea058c0e9ad50f7cdb8`
			`0, 11250, 614880, 9f6bf2739a027dfd12c81586cf75d3a3`
			`0, 15000, 614880, 7593a85ab7790eb39d65fc53f769ed8b`
			`0, 18750, 614880, 52f47f1e0348f3297d9f233fb5405e8b`
			`0, 22500, 614880, cd51d2c200bfd66e8e1b0fd6b404570f`
			`0, 26250, 614880, cf535cf0a53e903cd98a9a944b72da6d`
			`0, 30000, 614880, 1b270fd2b56daa7892102c2885d23201`
			`0, 33750, 614880, ff373c0c8a4a319c84e72b1c3d76b399`