4abc411b97
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>
4 lines
137 B
Plaintext
4 lines
137 B
Plaintext
56c403dd91ae1dd4569348381b2b43a4 *./tests/data/lavf/lavf.nut
|
|
319902 ./tests/data/lavf/lavf.nut
|
|
./tests/data/lavf/lavf.nut CRC=0x4780846b
|