|
|
I can confirm behavior, sample file is supplied in ticket. |
|
|
|
The problem is in the file - it contains track gain value, but does not contain track peak value. Our clipping prevention needs peak info for corrections. The solution is to reanalyze volume of affected files in MediaMonkey.
Assigning to Jiri to analyze, whether we could use some better clipping prevention algorithm also in case if no peak info (or wrong track gain and peak info) is present. |
|
|
|
Fixed related bug - wrong peak value rounding could cause noises too. |
|
|
|
Since there isn't a simple solution to the local clipping prevention, without rather significant changes to the audio workflow, deferring for further investigation of necessity and viability of such a feature. |
|
