[MLA] Lossy encoder clipping
Grimm | Eelco
eelco at grimmaudio.com
Fri Oct 12 18:10:02 CEST 2018
Hi Kevin and Bob,
> Robert from Fraunhofer was just complaining because Ian claimed that the clipping was "baked in" to the encoder. Which is untrue to the best of my knowledge. The encoder/decoder are in a closed floating point relationship and so if you intercept the decode in the floating point domain, attenuate it and dither it to 24 bits and then send it on to the DAC or file or whatever, there will be no clipping.
>
I got a reply from my Spotify contact. Please treat this as confidential information!
"I've also found out the float/int situation, and unfortunately it was as I feared, we're using int:s throughout the pipeline. The decoder(s) is/are float, but we clamp them to int right after the decode step. This is also, for sure, on our roadmap to change, but no promises on timeline there either, I'm afraid."
So at the moment there’s not much they can do. But at least they are aware of the problem and the opportunities now.
All the best,
Eelco
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://grimmaudio.nl/pipermail/mla_grimmaudio.nl/attachments/20181012/25ac8b7e/attachment.html>
More information about the MLA
mailing list