-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
metaflac --scan-replay-gain precision #536
Comments
If I run
If I then run So I don't seem to be able to reproduce the issue. The %1.8f is only used for the peaks, not for the gain. Also, I think having dB gain values with more than one than one decimal place is already pretty pointless, let alone 8. |
Okay, I misunderstood the question. I was under the impression you were comparing So, you would like more decimal places for the peak value? Why do you think these extra decimal places make sense? For 16 bit audio, the difference for one quantization step is only 0,000030, so adding more decimal places only makes sense for 24-bit audio. |
Thanks for the quick response, @ktmf01! My motivation for the request is to make it easier/faster to apply replaygain data to files conditionally, primarily to avoid writing any changes to the master files unless there are actual changes worth writing. (For me, this helps prevent lots of backup-related I/O for silly things like arbitrary changes to tag ordering.) At the moment, I copy the files from an album, run If |
The problem is that other applications might rely on the precision as it is right now. Also, I don't know what your primary use is here, but the algorithms |
Thanks @ktmf01, that makes sense. I'll take a look at some of the newer tools instead. |
Hi there!
It would be helpful if
metaflac --scan-replay-gain
formatted its values to the same precision as--add-replay-gain
, i.e.%1.8f
rather than just%f
.The more decimal places the merrier, I always say…
Thanks!
The text was updated successfully, but these errors were encountered: