Store analysis info in mp3 (so you only ever have to analyze an mp3 once)
But than I've noticed one thing... Why the "REPLAYGAIN_TRACK_GAIN" and "REPLAYGAIN_ALBUM_GAIN" are with only 0.5dB adequacy?? I use foobar2000 and it's more adequate... I know MP3Gain has to use 0.5dB steps when replaygaining but does it have tu use them here?I don't know much about mp3 and maybe it doesn't matter but if it does could you pretty please do something with it?
One other thing though... I might make myself look stupid again but I've found something that could possibly be a source of trouble. Foobar2000 uses a dot to separate the integer part of a number from the fractional (I'm not sure if I used the right words - I don't know English very well) while MP3Gain uses a comma. Well, probably the dot/comma is only a graphical symbol and it won't cause any problems...
As for the 4 vs. 6 decimal places, the version of foobar2k I've been using only writes 4 decimal places...?It's simple enough to make the switch in mp3gain, if needed.
I actually would suggest turning that Tag feature off by default! I played a little around with it and mp3test or mp3trim always said that the last frame is corrupted and that the mp3 has some errors!
It thinks the ape2-tag is corrupted frames.
After adjusting the gain and checking the files out with encspot, there are sync errors in all of them. Is this going to be a problem? What problems will this cause if any? Is there another way to tag the files without causing sync errors? Should I remove the tag? The sync errors just sort of worry me a little bit.
It shouldn't be a "real" problem, but I'm already thinking that I'll have to provide ID3v2 tag support (as an option to APEv2 tags) just so everyone doesn't keep asking me about this
yes I believe ID3v2 support would be the perfect solution!