aboutsummaryrefslogtreecommitdiffstats
path: root/tests/fate/gif.mak
diff options
context:
space:
mode:
authorMarton Balint <cus@passwd.hu>2024-03-17 23:35:24 +0100
committerMarton Balint <cus@passwd.hu>2024-03-25 21:30:51 +0100
commit5df901ffa56e0ff225fcc129c751befeb3b4d0d0 (patch)
tree4f48e7e648f2abf5fb9c8230e24a32437c549ea5 /tests/fate/gif.mak
parent7c003b63c85aadf57ca10be849bd9895a4eeeb87 (diff)
downloadffmpeg-5df901ffa56e0ff225fcc129c751befeb3b4d0d0.tar.gz
avutil/timestamp: introduce av_ts_make_time_string2 for better precision
av_ts_make_time_string() used "%.6g" format, but this format was losing precision even when the timestamp to be printed was not that large. For example for 3 hours (10800) seconds, only 1 decimal digit was printed, which made this format inaccurate when it was used in e.g. the silencedetect filter. Other detection filters printing timestamps had similar issues. Also time base parameter of the function was *AVRational instead of AVRational. Resolve these problems by introducing a new function, av_ts_make_time_string2(). We change the used format to "%.*f", use a precision of 6, except when printing values near 0, in which case we calculate the precision dynamically to aim for a similar precision in normal form as with %.6g. No longer using scientific representation can make parsing the timestamp easier for the users, we can safely do this because the theoretical maximum of INT64_MAX*INT32_MAX still fits into the string buffer in normal form. We somewhat imitate %g by trimming ending zeroes and the potential decimal point characters. In order not to trim "inf" as well, we assume that the decimal point string does not contain the letter "f". Note that depending on printf %f implementation, we might trim "infinity" to "inf". Thanks for Allan Cady for bringing up this issue. Signed-off-by: Marton Balint <cus@passwd.hu>
Diffstat (limited to 'tests/fate/gif.mak')
0 files changed, 0 insertions, 0 deletions