FFmpeg/tests/ref/fate/iff-byterun1

#tb 0: 1/90000
0,          0,          0,        0,   230400, 0x35e51c62
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/90000`
ffmpeg: set muxer packet duration based on framerate only for CFR a set ost->frame_rate does not imply CFR in ffmpeg The changed fate tests had all wrong packet durations (like 1/1000 or 1/90000) There might be more cases in which is_cfr could be set Signed-off-by: Michael Niedermayer <michael@niedermayer.cc> 2015-11-10 23:53:29 +02:00			`0, 0, 0, 0, 230400, 0x35e51c62`