Album gain use the loudest track gain in the album
Request an option for rsgain to apply loudest track gain for album gain.
The reason I want this; if there is an album with many soft songs and just 1 or 2 loud song, that loud song will louder compare to other songs from different album because I always use album gain when listening even in shuffle mode. Another reason this is recommend by AES:
https://www.aes.org/technical/documentDownloads.cfm?docID=731
This suggestion is great, and the functionality is worth looking forward to. In 2017, audio professionals mentioned this.
Album normalization comes in two types: normalize according to the average loudness of the whole album or according to the loudest track of the album. The ‘average album loudness’ variant is currently implemented in Apple iTunes and in ReplayGain. It unfortunately has a few drawbacks. Someone could master an album with many soft songs and just one loud song, which will then play louder than the loud songs from other albums. The loudness war would therefore continue. Another disadvantage is that the playback loudness of a certain track would only be known when the full album is finished and measured as a whole. This is unacceptable for a mastering engineer. All in all, we recommend to never use the ‘average album loudness’ version but always the ‘loudest track’ version.
https://web.archive.org/web/20231003160753/https://music-loudness.com/
https://octo.hku.nl/octo/repository/getfile?id=qLlZPGSVXFM
Now AES has also made this recommendation.
For this scenario, I’ve created a temporary workaround and would like to share it with everyone. https://github.com/DrZAjV/apply-loudest-track-gain-for-album-gain
Usage:
Step 1:
rsgain easy -mMax -O -p <your_profile> <your_music_library>
Step 2:
apply_loudest_track_gain.py <your_music_library>
Thank you for workaround @DrZAjV. I hope you consider add execute mode to the script git add --chmod=+x apply_loudest_track_gain.py and also add shebang in the first line of the script #!/usr/bin/env python or #!/usr/bin/python.
Just noticed this in the issues, after I made a pull request implementing this feature :) see #168