-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
replaygain: R128_ALBUM_GAIN should use a Q7.8 number #3311
Comments
This is already fixed in #3065 (via commit f3f75b7), as I found it while testing my I guess, I should also add some tests. I will do that later. |
Got it; thanks for pointing this out! I actually think the right way to fix this might be in MediaFile. That's where we intermediate between the internal representation of the number (a Python |
Since commit 95e569a, mediafile takes care of the float -> Q7.8 conversion in R128 GAIN tags by itself. From `store_album_r128_gain` this conversion was already missing, remove it from `store_track_r128_gain`, too. fixes beetbox#3311
Since commit 31326eb beets stores the R128_ALBUM_GAIN formatted as a float, not as a Q7.8, as required by IETF RFC 7845, 5.3.1.
Problem
Running this command in verbose (
-vv
) mode onmaster
:Led to this problem:
On commit
1619761
the same command formats the value inR128_ALBUM_GAIN
differently:As far as I can determine, the old behaviour is correct, as it conforms to the aforementioned RFC.
Setup
master
The relevant part of my configuration is:
(The unmerged
ffmpeg
backend was tested aswell.)My configuration (output of
beet config
) is:The text was updated successfully, but these errors were encountered: