I still don't understand why the replaygain-field stores the difference to a reference volume. Wouldn't it be a lot easier if just the volume of a track and the volume of the whole album would be stored?
I haven't discussed replay gain with Xiph, although plenty of others have.
Their position is clear, but not especially well suited to the situation with music players.
This should give you the gist of it. I'm sure you'll be familiar with the arguments from both sides.https://www.ietf.org/mail-archive/web/codec...eads.html#02935
I spotted another problem today. It'll be vanishingly rare, but worth mentioning.If the Output Gain is used to store the ReplayGain Album Gain (calculated to EBU R128 at -23LUFs), and you have a very dynamic album (i.e. one that peaks near digital full scale, but has a measured loudness lower than -23LUFs, hence a positive Output Gain), then you are telling every Opus player to clip it by default.Seems wrong, but that's the way it is.Cheers,David.
Although the spec doesn't like the commonly used REPLAYGAIN* comment tags, they seem very likely to occur in Opus files because of the incomplete support for track and album gain and peak values
If you like your clipping you can keep your clipping.
The design rationale of the Opus design was clearly to make at least album gain just work even if the player developer had never heard of ReplayGain.
This completely dwarfs your (1), (2) and (3)
The point of clipping is true, but that's a problem even IF you know the peak information. If you know that playing at the right loudness will cause clipping, there's no right way to play back the music.
FWIW the current Opus libraries contain helper functions to do soft clipping, because clipping is an issue in DAP even if ReplayGain isn't in the picture at all.
I understand what you want. You want a perfect world.
We can get some of that if we for example use Vorbis in foobar2000 or selected DAP, but go outside that much and it's a wasteland, and your Vorbis files turn into a pain to use. Opus' version of ReplayGain was designed so it would work everywhere, at the cost of dropping a feature whose benefit is very questionable (peak info).
Meanwhile, there is still no opusgain tool
Well, there's foobar2000.
Quote from: skamp on 12 March, 2014, 03:47:09 PMWell, there's foobar2000.If I admit I don't use it, do I get banned?
Quote from: skamp on 12 March, 2014, 02:32:22 PMMeanwhile, there is still no opusgain tool One reason why I feel I have to offer support for REPLAYGAIN* tags in Opus files. Until there is a tool to set real Opus gains, and maybe even after, people are going to slap in whatever gain tags they have whenever they transcode a file.