- 01 Oct, 2012 2 commits
-
-
Michael Niedermayer authored
While a 25 fps stream can in general store frame durations in 1/25 units, this is not true for the timestamps. For example a 25fps and a 25000/1001 fps stream when they are stored together might have a matching 0 timestamp point but when for example a chapter from this is cut the new start is no longer aligned. The issue gets MUCH worse when the streams are lower fps, like 1 or 2 fps. This commit thus makes the muxer choose a multiple of the framerate as timebase that is at least about 20 micro seconds precise Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
Michael Niedermayer authored
With this, when we use a finer timebase than neccessary to store durations the demuxer still knows what the original timebase was. Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 26 Aug, 2012 1 commit
-
-
Michael Niedermayer authored
The seek test improves in accuracy Fixes Ticket877 Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 17 Apr, 2012 1 commit
-
-
Michael Niedermayer authored
Not fully investigated but thumbnail supports rgb and not yv12 so this is better ... Signed-off-by:
Michael Niedermayer <michaelni@gmx.at>
-
- 27 Feb, 2012 1 commit
-
-
Nicolas George authored
-