- 18 May, 2012 2 commits
-
-
Anton Khirnov authored
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.
-
Anton Khirnov authored
This makes lavf discard broken timestamps for non-B frames in samples/isom/vc1-wmapro.ism.
-
- 10 May, 2012 1 commit
-
-
Mans Rullgard authored
Converting the double to float for lrintf() loses precision when the value is not exactly representable as a single-precision float. Apart from being inaccurate, this causes discrepancies in some configurations due to differences in rounding. Note that the changed timestamp in the vc1-ism test is a bogus, made-up value. Signed-off-by: Mans Rullgard <mans@mansr.com>
-
- 26 Feb, 2012 2 commits
-
-
Anton Khirnov authored
Neither of those is guaranteed to be connected to framerate in any way (if it even exists). Fixes bug 56.
-
Anton Khirnov authored
r_frame_rate should in theory have something to do with input framerate, but in practice it is often made up from thin air by lavf. So unless we are targeting a constant output framerate, it's better to just use input stream timebase. Brings back dropped frames in nuv and cscd tests introduced in cd1ad18a
-
- 08 Feb, 2012 2 commits
-
-
Anton Khirnov authored
This changes a number of FATE results, since before this commit, the timestamps in all tests using rawenc were made up by lavf. In most cases, the previous timestamps were completely bogus. In some other cases -- raw formats, mostly h264 -- the new timestamps are bogus as well. The only difference is that timestamps invented by the muxer are replaced by timestamps invented by the demuxer. cscd -- avconv sets output codec timebase from r_frame_rate and r_frame_rate is in this case some guessed number 31.42 (377/12), which is not accurate enough to represent all timestamps. This results in some frames having duplicate pts. Therefore, vsync 0 needs to be changed to vsync 2 and avconv drops two frames. A proper fix in the future would be to set output timebase to something saner in avconv. nuv -- previous timestamps for video were wrong AND the cscd comment applies, one frame is dropped. vp8-signbias -- the file contains two frames with identical timestamps, so -vsync 0 needs to be removed/changed to -vsync 2 and avconv drops one frame. vc1-ism -- apparrently either the demuxer lies about timestamps or the file is broken, since dts == pts on all packets, but reordering clearly takes place.
-
Michael Niedermayer authored
This makes the code more similar to qatar And fixes decoding of the last frame of fate/vc1-ism Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
-
- 03 Feb, 2012 1 commit
-
-
Anton Khirnov authored
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.
-
- 29 Jan, 2012 1 commit
-
-
Reimar Döffinger authored
Causes FFmpeg to pass through the correct pts values, instead of clobbering all to AV_NOPTS_VALUE (the av_init_packet default) to then make up new ones based on only fps when muxing. Included are also the related FATE ref changes, which all some reasonable on quick investigation. Also set all H.264 references to us -vsync drop to reduce the diff for the ref files. Otherwise almost all H.264 references need to change, mostly due to now starting with negative pts values. About 20 additional H.264 conformance tests needed -vsync drop anyway because they create pts values that are out of order and thus not possible to mux otherwise. Signed-off-by: Reimar Döffinger <Reimar.Doeffinger@gmx.de>
-
- 09 Jan, 2012 1 commit
-
-
Alex Converse authored
-