Michael Fabian 'Xaymar' Dirks (12021-05-18): > while tracking some time stamp issues unique to FFmpeg I noticed > AV_Time_BASE(_Q) being present quite often, which appears to be a > value to define time stamps in milliseconds. Tracking it back to its > origin I could find very little to no information about why this value > was chosen. All I know so far is that it was chosen for compatibility > with very early versions of FFmpeg.
Microsecond timestamps are a good compromise that allows enough precision for almost everything while having a wide enough range on normal 64 bits arithmetic. Using nanosecond, for example, would let timestamps overflow after six centuries, which is too close for comfort. > Does FFmpeg require this value to be a full millisecond? Or is it > possible to adjust this to microseconds and "fix" many of the time > stamp issues that occur? While it seems to be possible to work-around > this issue on a muxer/demuxer level, the underlying issue in FFmpeg > would still be present. At the moment, most non-integer ms framerates > and sample rates end up performing weird without post-processing. Please tell what value you would recommend instead of a microsecond, and explain precisely which weirdness it would allow to fix and how. 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".
