On Wednesday, March 27, 2019, 11:19:23 AM PDT, Michael Niedermayer
wrote: > this breaks make fate> > also if fate is
updated it should be ensured it still checks enough precission> and that it
does produce the same results (fate passes) on all relevant> platforms. This
change may bring non s
On 27.03.2019 23:13, Allan Cady via ffmpeg-devel wrote:
On Tue, Mar 26, 2019 at 10:07:10PM +, Allan Cady via ffmpeg-devel wrote:
When the silencedetect filter is run against very large files, the
output timestamps gradually lose precision as the scan proceeds
further into the file. This i
2019-03-27 23:13 GMT+01:00, Allan Cady via ffmpeg-devel
:
> On Tue, Mar 26, 2019 at 10:07:10PM +, Allan Cady via ffmpeg-devel
> wrote:
>
>> When the silencedetect filter is run against very large files, the
>> output timestamps gradually lose precision as the scan proceeds
>> further into the
On Tue, Mar 26, 2019 at 10:07:10PM +, Allan Cady via ffmpeg-devel wrote:
> When the silencedetect filter is run against very large files, the
> output timestamps gradually lose precision as the scan proceeds
> further into the file. This is because the output is formatted (in
> libavutil/time
