Sorry for the delayed response— been tied up on other tasks. Calvin Walton [[email protected]] wrote: > Hmm? Replaygain does specify a method. They go into a lot of details on > http://www.replaygain.org/ to describe the loudness filter used, the > method for calculating RMS power levels afterwards, the histogram-based > statistical processing, and how to calibrate the gain level to the -83dB > reference with a pink noise signal.
It offers one, yes— but it's not a specification. I was stridently corrected by the author of replaygain when I made the same claim that you are. I'm also advised that most tools are now using the EBU R128 method now in any case. And in practice the point is fairly moot as the values are effectively compatible on actual audio once the reference level. > Yes, having the standard gain header that is supported by all decoders > is nice - except for the case of playback of mixed file formats, > particularly by an application that doesn't understand the gain tags in > other formats. In those cases, the Opus files will be significantly > quieter (assuming modern pop mastering...) than the other files, making > them sound "worse" than files without gain applied. I don't see how you can usefully make an argument here. If you don't have gain adjustment (on the files or in the application) and you have files from various sources you will have various levels. If you listen exclusively to commercially mastered loudness-war recordings then having gain adjustment on some files and not others would increase the level of the already existing inconsistency somewhat. But I don't see what more there is to do about that. I can't abide by an argument that because Vorbis was previously broken all things forever must be broken. Applying gain on OggOpus files has functionally identical behavior to aacgain/mp3gain with respect to this. > I can do that; here's the CC attribution, non-commercial, share-alike > track "Discipline" by Nine Inch Nails, with vorbis-style replaygain tags I still can't reproduce on my system, but I've asked people to fix it and the next version of these tools shouldn't have the weird behavior any longer. > The issue I see here is that the normalization method used for the value > in the opus header output gain field is *not specified* currently. An There is a recommendation, but it's not— and shouldn't be— a requirement. > If a player blindly applies only the header output gain value, it has no > knowledge of whether the output is loudness normalized or not. I'd like to say that there should be an informative tag there to indicate whats being done. However: I'm absolutely sure it will be reliably set wrong, double so because other than displaying it as metadata there is simply nothing most software can do with the information. There would be little way for careless implementers to discover that they've gotten it wrong... and so the information would likely be worse than useless as it would just add complexity without concrete value. _______________________________________________ codec mailing list [email protected] https://www.ietf.org/mailman/listinfo/codec
