ffmpeg/tests/ref/fate/h264-conformance-cvfi2_sva_c

#tb 0: 1/25
0,          0,          0,        1,   518400, 0x4073cc0b
0,          1,          1,        1,   518400, 0x5f599a48
0,          2,          2,        1,   518400, 0xc6fe555a
0,          3,          3,        1,   518400, 0xe63ac345
0,          4,          4,        1,   518400, 0x9b4f0c5c
0,          5,          5,        1,   518400, 0x98aaba2d
0,          6,          6,        1,   518400, 0xd629bd09
0,          7,          7,        1,   518400, 0xe9796c37
0,          8,          8,        1,   518400, 0xba54d16e
0,          9,          9,        1,   518400, 0xe396c3eb
0,         10,         10,        1,   518400, 0x63ee4b81
0,         11,         11,        1,   518400, 0x68ac6986
0,         12,         12,        1,   518400, 0xe0d53000
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 13:20:43 +00:00			`#tb 0: 1/25`
avconv: replace -vsync cfr code with the fps filter. Invented timestamps for the h264 tests return to something resembling sanity. In the idroq-video-encode test when converting 25 fps -> 30 fps the fifth frame gets duplicated instead of the sixth. 2012-05-09 14:25:02 +00:00			`0, 0, 0, 1, 518400, 0x4073cc0b`
			`0, 1, 1, 1, 518400, 0x5f599a48`
			`0, 2, 2, 1, 518400, 0xc6fe555a`
			`0, 3, 3, 1, 518400, 0xe63ac345`
			`0, 4, 4, 1, 518400, 0x9b4f0c5c`
			`0, 5, 5, 1, 518400, 0x98aaba2d`
			`0, 6, 6, 1, 518400, 0xd629bd09`
			`0, 7, 7, 1, 518400, 0xe9796c37`
			`0, 8, 8, 1, 518400, 0xba54d16e`
			`0, 9, 9, 1, 518400, 0xe396c3eb`
			`0, 10, 10, 1, 518400, 0x63ee4b81`
			`0, 11, 11, 1, 518400, 0x68ac6986`
			`0, 12, 12, 1, 518400, 0xe0d53000`