mp3gain uses 1.5 dB steps, whereas the tag-only method isn't.These 1.5 dB steps give a max amplitude error from 0.75 dB from wanted value, acceptible to me.(afaik 1 dB is the smallest volumestep that can be detected by the ear)For mp3gain, you can only reverse it's results when you know how much you altered the volume in the first placeStripping the tag just gives original file having original volume.
0.75dB error, yes, but with two back-to-back tracks you could potentially have 1.5dB of loudness difference which is noticeable.
Another advantage of Replay Gain (on compliant players) over mp3gain is the ability to switch between album gain and track gain without re-processing your files.
For me, the main drawback of MP3Gain is that it doesn't support ID3v2 tags yet.It's really cumbersome to maintain three different tags in every file (id3v1, id3v2 and APEv2).
The GUI works just fine with aacgain.
I know Glen is busy with other things, but I think mp3gain is "finished" rather than "stopped"! Well, as finished as any software ever is.
...Also, Dave and I will hopefully be merging the code in the near future, so AAC support will be completely integrated into MP3Gain. We'll keep you posted.
Quote from: benski on 06 June, 2008, 10:50:26 AM0.75dB error, yes, but with two back-to-back tracks you could potentially have 1.5dB of loudness difference which is noticeable.Depending on which tracks go back to back, you can easily notice a difference with two tracks that have the same RG figure or even have one that sounds louder even though RG suggests it's quieter. I've had to increase the attenuation with my Beatles tracks because of this. Not that I'm complaining, but I've gotten the impression that some people place too much importance on the numbers.
Quote from: greynol on 06 June, 2008, 03:25:37 AMThe GUI works just fine with aacgain.Yes, but you have to rename aacgain.exe to mp3gain.exe and replace the original mp3gain.exe in the MP3Gain folder. Not too flexible if you have both mp3 and aac files.
Here it only writes to APEv2... that leaves ID3v2.x for the original meta data. That it doesn't write to ID3 tags is a feature, because you don't want to mix up the MP3Gain meta data and original meta data! Stupid players might "reinterprete" and rewrite the MP3Gain undo data. So all you'd have to maintain are the "default" MP3 tags, i.e. ID3v2.x (or ID3v1 in case you have ancient playback hardware/software).
2. 1.5 dB steps is not a big deal. See my Beatles example; you need to make sure the perceived loudness is actually consistent before you start worrying about resolution. Maybe after I make adjustments to my Beatles tracks, I'm still off by 1.49 dB from tracks from some other album. I have a hard time believing this will be all that noticeable.
Replaygain by design does not save the target/reference! It is just asumed, that by convention, it is always 89dB (basically, the 89dB reference IS part of the replaygain specification!)
Quote from: Lyx on 09 June, 2008, 12:33:33 PMReplaygain by design does not save the target/reference! It is just asumed, that by convention, it is always 89dB (basically, the 89dB reference IS part of the replaygain specification!)And that's exactly how MP3Gain stores the tag information. No matter what the user has set in the GUI, the actual stored information is based on the 89dB reference. If a user has their "target" set to 95dB and they use Track Gain on a file, then if someone else opens that file in MP3Gain with the default 89dB target, they will see that the file is about 6dB too loud and should be turned down. The user-adjusted "target" is only used inside the currently-running GUI.
mp3gain itself is "counterproductive to ever establish replaygain as a mainstream-standard..... something which is in any kind of hifi-components" because it removes the need to implement any support outside of mp3gain itself.
in fact, if you take the ReplayGain standard as a whole, then "tag implementations" need a pre-amp in the player, so implicitly "no-tag implementations" need some adjustment in the utility itself (because there's nowhere else to put it).