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>
15 lines
742 B
Plaintext
15 lines
742 B
Plaintext
abgr b04e3dfb0043f6eb04a573d2d13052eb
|
|
argb 257e33717d23298430025c0665642cd5
|
|
bgr24 3765d88f93d4ae8baa2cfbc64b0b32e1
|
|
bgr555be 81832e6269c509be55bba49bdd0ebed5
|
|
bgr555le 56772e91aefba4013890d156866730ce
|
|
bgr565be 0b3c420fbddcec5a420c285b3c4b8792
|
|
bgr565le 6cbded26d2bab8204afe2115384c09a8
|
|
bgra c81430c3d1465e37b6acaa19cc54e932
|
|
rgb24 9899359a817e705dc5b9cc363d35a625
|
|
rgb555be 9b60d9aa1f3c78edf9936894f37e3243
|
|
rgb555le 917fa8565f35882404a45fee3a947bf7
|
|
rgb565be 12edaab49440fbb3aa4c1835fd697745
|
|
rgb565le 5bf91cb1767066f23f0c672dedb4d476
|
|
rgba 71687289b6c3ab6fa727d468de459026
|