-
Notifications
You must be signed in to change notification settings - Fork 24
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
[BUG]: Picard plugin unable to normalize volume #113
Comments
Can you explain exactly how it's not working? Are you getting error messages? etc. Also, if you can upload a sample file, that may help in the diagnosis. |
I do not think uploading is such a viable idea, since it would mean uploading 2 copyrighted albums. Here are the tags calculated by foobar, downsampling, discarding non audible frquencies With Foobar's calcuation, the replaygain works as intended, every album is the sameish volume-wise (mainting the volume differences between tracks within the album) |
I don't understand why the tags have 2 values. |
From the whole library, i will show 2 tracks, and the different replaygain values. This table shows the replygain values generated by rsgain/picard. These values do not work, they do not normalize the value. With this, Taylor swift is considerably louder, than the flute + piano duo.
This table shows the good values, generated by foobar. These values do actualy normalize the volume
File size is too big, cannot attach directly, so here is a link: https://drive.google.com/file/d/1P0DTsqhDA347Devo5uFgDd_sXAVRKwxC/view?usp=sharing |
The Picard plugin was unable to determine the correct replaygain tags for high Res classical music.
Foobar worked very nicely though. Foobar downsampled the audio, so only it worked with audible frequencies. Is it possible, that it is missing from this and that is the reason, replaygain failed?
The text was updated successfully, but these errors were encountered: