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>
25 lines
1.2 KiB
Plaintext
25 lines
1.2 KiB
Plaintext
0bgr 36ba5b43e0ac64d8daad4f897efd8cdf
|
|
0rgb cc3ca0f63885af19b3daa4504cadcc19
|
|
abgr 9ddb78f395d7d3f75b65b5309223c0c5
|
|
argb e5fbb7bb282a80897b8f730627f68876
|
|
bgr0 c55368036cccbb0af471d6bd82abe02a
|
|
bgr24 67f9fd70dc6d9896b7122976b33932b4
|
|
bgra c8dd017b5a3b55e8b9d0ac1cdcf327bd
|
|
gray b1abadae3718522aa57a7972da8cbe17
|
|
rgb0 b1977b45634c4db58a183a07feb2acff
|
|
rgb24 e73de9dc0fdd78f4853c168603cc7aba
|
|
rgba 5a36df3c5ba623b589728a5a442e98e2
|
|
yuv410p ff246b8b41d3d4a3eb90414ae3031123
|
|
yuv411p a82c606c665fa747679aa8bfffa8a5db
|
|
yuv420p 0fe4d9031999f83ca96292ec2025f272
|
|
yuv422p 5e0bffdac30b39f1bae9ec54fd9a6a34
|
|
yuv440p 5e338303cd89d1d76ab918e5bec1e90d
|
|
yuv444p 248bdf9747d5c3718580dc2279e2e273
|
|
yuva420p b5bdefbb0c5b302b6d18ee4df7c1d7c7
|
|
yuva422p 8b56b36d9eb3c382d2a5a695107e759d
|
|
yuva444p 389cf95e98bf24684a42d5d67b913e16
|
|
yuvj420p d182ac937d312e4894c1bc548883bf1c
|
|
yuvj422p 26ac91b5daf6f2f1f3c22be489e994a3
|
|
yuvj440p 63e2b94f81e0a6f2868055a4c8258b63
|
|
yuvj444p 64f103c7db8fc803d062db7ed2b8dc76
|