Opened 5 years ago
Closed 5 years ago
#6968 closed defect (fixed)
`silencedetect` only logs start of silence – not end and duration
| Reported by: | annoying | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | avfilter |
| Version: | git-master | Keywords: | silencedetect |
| Cc: | Blocked By: | ||
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
not sure if this is a bug or expected behavior. for an audio file that only contains silence, this command only logs the beginning of silence (– no end and duration):
[silencedetect @ 0x7ff3977000c0] silence_start: -0.00628118
command:
ffmpeg -i silence-31s.mp3 -af "silencedetect=n=-50dB:d=1" -f null -
ffmpeg version:
3.4.1
Attachments (1)
Change History (4)
by , 5 years ago
| Attachment: | silence-31s.mp3 added |
|---|
comment:1 by , 5 years ago
comment:2 by , 5 years ago
| Component: | undetermined → avfilter |
|---|---|
| Keywords: | silencedetect added; silence removed |
| Version: | unspecified → git-master |
comment:3 by , 5 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed in 759381d96b221abb663627dc25135b76d8c2106a.
Note:
See TracTickets
for help on using tickets.
End time and duration are updated by the filter when it gets to the next non-silent sample. For a fully silent file, that will never happen.
This could be considered a bug since a segment of silence has to end sometime even if at the end of file.