ffmpeg/tests/ref/lavfi/tinterlace_merge

gray                c996e583bbc5a6f380463142eb77b7c6
yuv410p             c9bad1317b496071d6d895238638e07d
yuv420p             9794d11e59ec7bcdf9e30a433e4137b1
yuv422p             e852e61e455db8ee3981ea942d510b0f
yuv444p             a38a3f65d2f358cde5e9547c897cfcd5
yuva420p            c1dc15d6ee78587d9f825acd795673d7
yuvj420p            3ee7014727ee64b45292a4f15ba028d8
yuvj422p            4f990d5473f15571276adb5770b3b773
yuvj440p            9a005e8b8431aaa762fde8d942fd11a9
yuvj444p            e29bf9f42e3a3632e09df529979e0040
nutenc: choose for non audio streams a timebase with finer resolution. While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by: Michael Niedermayer <michaelni@gmx.at> 2012-10-01 21:51:35 +00:00			`gray c996e583bbc5a6f380463142eb77b7c6`
			`yuv410p c9bad1317b496071d6d895238638e07d`
			`yuv420p 9794d11e59ec7bcdf9e30a433e4137b1`
			`yuv422p e852e61e455db8ee3981ea942d510b0f`
			`yuv444p a38a3f65d2f358cde5e9547c897cfcd5`
			`yuva420p c1dc15d6ee78587d9f825acd795673d7`
			`yuvj420p 3ee7014727ee64b45292a4f15ba028d8`
			`yuvj422p 4f990d5473f15571276adb5770b3b773`
			`yuvj440p 9a005e8b8431aaa762fde8d942fd11a9`
			`yuvj444p e29bf9f42e3a3632e09df529979e0040`