Closed canchanchara closed 2 years ago
This seems to be an upstream bug.
[loudnorm @ 000001dcfcfb2700] Value 115.400000 for parameter 'measured_tp' out of range [-99 - 99]
It measured a true peak of 115.4 in the first pass, but the filter itself only accepts an input in a smaller range for the second pass.
Do you have any idea for an workaround in ffmpeg-normalize?
I constrain these values now. Feels like an ugly workaround but it should rarely happen in practice. Release will come in a minute.
:warning: Please read this carefully and edit the example responses! If you do not fill out this information, your bug report may be closed without comment.
Checklist (please tick all boxes)
ffmpeg-normalize
(runpip3 install --upgrade ffmpeg-normalize
)ffmpeg
or a recent build from Git masterExpected behavior I would like to normalize a mp3 file. It works with a lot of files, but this in attachment for example does not work.
Actual behavior I got this error:
[loudnorm @ 00000277a5ff3780] Value 115.400000 for parameter 'measured_tp' out of range [-99 - 99] [loudnorm @ 00000277a5ff3780] Error setting option measured_tp to value 115.4. [Parsed_loudnorm_0 @ 00000277a5fdd800] Error applying options to the filter. [AVFilterGraph @ 00000277a5fdf800] Error initializing filter 'loudnorm' with args 'i=-14.0:lra=11.0:tp=-2.0:offset=0.88:measured_i=0.0:measured_lra=0.0:measured_tp=115.4:measured_thresh=-10.0:linear=true:print_format=json' Error initializing complex filters. Result too large
Command The exact command you were trying to run:
File to reproduce: 42db7abc61a4c7d58873f95a4de335094c633406.zip
Any output you get when running the command with the
--debug
flag:Environment (please complete the following information):
python3 --version
orpython --version
): 3.10.6ffmpeg -version
) N-108116-g50a4dff69f-20220913