Opened 7 hours ago
Last modified 7 hours ago
#11287 new enhancement
Practicality enhancement for "volume" filter
| Reported by: | MasterQuestionable | Owned by: | |
|---|---|---|---|
| Priority: | normal | Component: | avfilter |
| Version: | git-master | Keywords: | volume |
| Cc: | MasterQuestionable | Blocked By: | |
| Blocking: | Reproduced by developer: | no | |
| Analyzed by developer: | no |
Description
͏ I find it quite troublesome to perform some rather frequently used simple task:
͏ (peak normalization)
͏ https://ffmpeg.org/ffmpeg-filters.html#volume
͏ https://trac.ffmpeg.org/wiki/AudioVolume
͏ https://superuser.com/questions/1697111/is-simple-peak-normalization-possible-using-ffmpeg#1697123
͏ https://superuser.com/questions/323119/how-can-i-normalize-audio-using-ffmpeg
͏ .
͏ See also:
͏ https://trac.ffmpeg.org/ticket/1649
͏ https://trac.ffmpeg.org/ticket/9613#comment:5
͏ Suggested fix:
͏ New volume expression parameter: "peak".
͏ Reflects directly the positive of what attained in "volumedetect" "max_volume".
Note:
See TracTickets
for help on using tickets.
͏ I also noted some quirkiness on the volume expression:
͏ Prefixed numbers ("±") mostly would intend for ± in dB: while the interpretation regardless parsed as multiplication factor.
͏ And required alike writing: https://trac.ffmpeg.org/ticket/11283#comment:1
͏ [ ^ That intends "volume=peak-0.001". ]
͏ Some clean-up in the parsing logic would be desirable.