[FFmpeg-trac] #7875(undetermined:new): ffmpeg freezedetect filter output
FFmpeg
trac at avcodec.org
Mon Apr 29 21:23:37 EEST 2019
#7875: ffmpeg freezedetect filter output
-------------------------------------+-------------------------------------
Reporter: arianaa30 | Type:
| enhancement
Status: new | Priority: important
Component: | Version:
undetermined | unspecified
Keywords: | Blocked By:
Blocking: | Reproduced by developer: 0
Analyzed by developer: 0 |
-------------------------------------+-------------------------------------
Summary of the bug:
The ffmpeg freeze output is expected to output intervals of detections
'''always''' with start-duration-end tags. But we see sometimes, start tag
is missing, and duration shows right after previous end. For development
purposes, it is best to always have a start, even if start is equal to
previous end.
Example command:
{{{
ffmpeg -i freeze.mp4 -vf "freezedetect=n=-60dB:d=0.1" -map 0:v:0 -f null
-
}}}
How to reproduce:
{{{
% ffmpeg -i input ... output
ffmpeg version N-93649-gd0ca749adb Copyright (c) 2000-2019 the FFmpeg
developers
built with gcc 8.3.1 (GCC) 20190414
}}}
{{{
[freezedetect @ 0000016df6c06a00] lavfi.freezedetect.freeze_start: 0
[freezedetect @ 0000016df6c06a00] lavfi.freezedetect.freeze_duration:
0.9009
[freezedetect @ 0000016df6c06a00] lavfi.freezedetect.freeze_end: 0.9009
[freezedetect @ 0000016df6c06a00] lavfi.freezedetect.freeze_duration:
0.1001
[freezedetect @ 0000016df6c06a00] lavfi.freezedetect.freeze_end: 1.001
[freezedetect @ 0000016df6c06a00] lavfi.freezedetect.freeze_start: 5.005
[freezedetect @ 0000016df6c06a00] lavfi.freezedetect.freeze_duration:
2.03537
[freezedetect @ 0000016df6c06a00] lavfi.freezedetect.freeze_end: 7.04037
}}}
--
Ticket URL: <https://trac.ffmpeg.org/ticket/7875>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
More information about the FFmpeg-trac
mailing list