Marton Balint:
>
>
> On Wed, 20 Mar 2024, Andreas Rheinhardt wrote:
>
>> Andreas Rheinhardt:
>>> Marton Balint:
av_ts_make_time_string() used "%.6g" format in the past, but this
format was
losing precision even when the timestamp to be printed was not that
large. For
On Wed, 20 Mar 2024, Marton Balint wrote:
On Wed, 20 Mar 2024, Andreas Rheinhardt wrote:
Andreas Rheinhardt:
Marton Balint:
av_ts_make_time_string() used "%.6g" format in the past, but this format
was
losing precision even when the timestamp to be printed was not that
large. For
On Wed, 20 Mar 2024, Andreas Rheinhardt wrote:
Andreas Rheinhardt:
Marton Balint:
av_ts_make_time_string() used "%.6g" format in the past, 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
Andreas Rheinhardt:
> Marton Balint:
>> av_ts_make_time_string() used "%.6g" format in the past, 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
Marton Balint:
> av_ts_make_time_string() used "%.6g" format in the past, 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
On Mon, 18 Mar 2024, Marton Balint wrote:
av_ts_make_time_string() used "%.6g" format in the past, 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
av_ts_make_time_string() used "%.6g" format in the past, 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
