FFmpeg/tests/ref/fate/h264-conformance-frext-frext2_panasonic_b

#tb 0: 1/25
0,          0,          0,        1,   152064, 0x0147a2a9
0,          1,          1,        1,   152064, 0xe2365351
0,          2,          2,        1,   152064, 0xb5f9daee
0,          3,          3,        1,   152064, 0xd60818b2
0,          4,          4,        1,   152064, 0x21b528e5
0,          5,          5,        1,   152064, 0x9c9dda18
0,          6,          6,        1,   152064, 0x387fe7de
0,          7,          7,        1,   152064, 0x8f0c5a1e
0,          8,          8,        1,   152064, 0x02409694
0,          9,          9,        1,   152064, 0x2b36a7a7
0,         10,         10,        1,   152064, 0x3c6d3863
0,         11,         11,        1,   152064, 0xaa7835e1
0,         12,         12,        1,   152064, 0x6d105fe7
0,         13,         13,        1,   152064, 0x9a348732
0,         14,         14,        1,   152064, 0x96a3af13
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 16:20:43 +03:00			`#tb 0: 1/25`
			`0, 0, 0, 1, 152064, 0x0147a2a9`
			`0, 1, 1, 1, 152064, 0xe2365351`
			`0, 2, 2, 1, 152064, 0xb5f9daee`
			`0, 3, 3, 1, 152064, 0xd60818b2`
			`0, 4, 4, 1, 152064, 0x21b528e5`
			`0, 5, 5, 1, 152064, 0x9c9dda18`
			`0, 6, 6, 1, 152064, 0x387fe7de`
			`0, 7, 7, 1, 152064, 0x8f0c5a1e`
			`0, 8, 8, 1, 152064, 0x02409694`
			`0, 9, 9, 1, 152064, 0x2b36a7a7`
			`0, 10, 10, 1, 152064, 0x3c6d3863`
			`0, 11, 11, 1, 152064, 0xaa7835e1`
			`0, 12, 12, 1, 152064, 0x6d105fe7`
			`0, 13, 13, 1, 152064, 0x9a348732`
			`0, 14, 14, 1, 152064, 0x96a3af13`