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>
11 lines
530 B
Plaintext
11 lines
530 B
Plaintext
gray 25a7d1ccf1a06c1a8a0520c1e6cb30ff
|
|
yuv410p 17163d1b4f21d894598fc62e6aeb8141
|
|
yuv420p f8bbae33295741c1c17d33ff8ee16f7f
|
|
yuv422p 4fa67d1580d3453942bb0950c5784f6e
|
|
yuv444p f0558305fb7ca65b5b86d3ee88c4201e
|
|
yuva420p 7c76c0ca03a62275d25e8140c68da2b9
|
|
yuvj420p b5b7baf11946a2265fc56e48be5b0436
|
|
yuvj422p 2e70ab700851d12a773f926bb1785235
|
|
yuvj440p 93319f9c8a02ee793966fae40f7e42fd
|
|
yuvj444p 81a124fffe0214bee5205c90ae0dd201
|