I imagine that this is due to the peak files being limited to 16-bit, so when it uses them to calculate the peak, it's getting an approximate value, which might be slightly off if the material is 24-bit... So maybe just live with it for now? It'll be close enough for all practical purposes. I suppose we could add a slow normalize action, which might take a few seconds depending on how long the media is.
|