Michael Fabian 'Xaymar' Dirks (12021-05-20): > There are plenty of reasons to know the actual frame rate with high > precision. > Editing software needs to know this to initialize effects, timelines > and projects.
I doubt they do that without building an index in the first place. > Players need it to queue the right amount of frames at the right time. No, they need to queue _enough_ frames, and for that timestamps are enough. > Transcoding requires it to encode at the right rate. Encoding mostly does not care about rate. > Remuxing requires it so that it doesn't end up as "variable" without Why would it be a problem? > requiring extensive extra parameters and scripting to get FFmpeg to > like the MKV file. Please be more specific. > I don't see a single reason to not offer users the choice to increase > the precision to their liking. I see no reason not to. But I also see no reason users should do it, and you have not convinced me. > I have yet to see anyone use timestamps wrong. I suggest you spend a little time doing support on the users mailing-list and you will see plenty. > Timestamps should be as accurate as possible, especially when you > consider that even with 1µs of precision in a 64-bit timestamp, you > can still mux for at least 584000 years before you have to wrap around > to zero again. You need to learn about the difference between accuracy and precision. Regards, -- Nicolas George
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-requ...@ffmpeg.org with subject "unsubscribe".
