Author | SHA1 | Message | Date |
---|---|---|---|
|
4abc411b97 |
nutenc: choose for non audio streams a timebase with finer resolution.
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> |
12 years ago |
|
e3fb5bc147 |
nut: store and read the r_frame_rate
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> |
12 years ago |
|
3a621c9d99 |
nutenc: Support writing an index
The seek test improves in accuracy Fixes Ticket877 Signed-off-by: Michael Niedermayer <michaelni@gmx.at> |
12 years ago |
|
48f3d43113 | fate: add test for the unsharp video filter. | 13 years ago |