FFmpeg/tests/ref/fate/yop

#tb 0: 1/12
0,          0,          0,        1,   302760, 0x78939253
0,          1,          1,        1,   302760, 0x534f5253
0,          2,          2,        1,   302760, 0x25eaa782
0,          3,          3,        1,   302760, 0x60861c3d
0,          4,          4,        1,   302760, 0x43552521
0,          5,          5,        1,   302760, 0x45abca02
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/12`
			`0, 0, 0, 1, 302760, 0x78939253`
			`0, 1, 1, 1, 302760, 0x534f5253`
yop: initialize palette to 0 The FATE sample contains some pixels with value 0, but the palette stored in the file contains only values from 16 up. Because the default and cmdutils get_buffer() initialize the data to 0x80, they appear as gray dots. After this commit they change to black dots, which is probably still incorrect but less visible and doesn't rely on get_buffer() initializing the data. 2013-01-30 16:33:53 +03:00			`0, 2, 2, 1, 302760, 0x25eaa782`
			`0, 3, 3, 1, 302760, 0x60861c3d`
			`0, 4, 4, 1, 302760, 0x43552521`
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			`0, 5, 5, 1, 302760, 0x45abca02`