Calvin Walton [[email protected]] wrote: > While I don't see any technical problems with R128 - it is a good volume > normalization scheme - the issue is that it is a *different* > normalization scheme from the replaygain tags that are supported in
Replay gain does not specify a method for measuring the level. The R128 measurement technique is, in fact, being used in place of te older replay-gain in many places and I wouldn't be surprised if it were actually the most popular of the two then. With that in mind the only difference between the two values is the specified meaning and a constant scaling factor for the different reference levels. So it's trivial to make software that that can play a mixture of OggOpus and replaygain vorbis with the expected constant levels. > other audio formats - it gives different results, and isn't directly > interoperable, and isn't supported by many existing players. Replaygain itself has very spotty support. This means that if you create a file with replaygain tags it will have _wildly_ different playback levels depending on which player you use. So any content distributor can simply not use it if they care about things working consistently at all. The only place it works reliably is on your own files... and well, if thats all you care about interoperability isn't much of an issue. One of the major motivations behind how this this is address in OggOpus is that we have the gain header field that gives a default playback gain. This works in all existent players... and it allows consistent behavior. And it is supported by every single existing decoder that I'm aware of. > I've done a survey of existing player applications with Ogg Opus > support. All of these players: > * Rockbox (development version with Opus support) > * GStreamer-based (e.g. Rhythmbox) > will use the REPLAYGAIN_TRACK_GAIN and REPLAYGAIN_ALBUM_GAIN tags (as > specified in Vorbis) to apply replaygain to Opus tracks. Both Rockbox Can you give me a link to a test file— I tried and it isn't for me. > and Gstreamer-based players will first apply the stream header's output > gain field prior to applying the replaygain correction; I haven't > checked foobar2000 on that point. Well thats good. > Of the players in that list, only foobar2000 supports the R128 gain tag. > I am not sure what happens if both tags are present. Thats not correct. The way the spec is constructed and apps are implemented gain works fine _without_ supporting the tag. It basically make it work by default. And I think this is a massive improvement which would be broken by reintroducing the widespread inconsistency of replaygain. Make sense? _______________________________________________ codec mailing list [email protected] https://www.ietf.org/mailman/listinfo/codec
