Posted by: Anonymous Coward
on February 28, 2007 11:07 PM
In your article you state:
[...]Then, after analyzing the file, it can save information to the MP3's metadata in the APEv2 format[...]
But this is patently false, because mp3 metadata is not in the APEv2 format. To many mp3 compliant programs, the APEv2 data is garbage noise in the mp3 stream, and adding a foreign tag to mp3 files is ungainly and awful.
To split hairs of course id3 and id3v2 tags are also not compliant mpeg audio layer 3 data, but nearly every mp3 decoding program has been improved to handle them. When you start adding random other "tags" (ie. blobs of data) to the end of the file, however, all bets are off.
id3v2 is extensible, so mp3gain should use custom fields in id3v2.
Since it does not, I simply have mp3gain adjust the mp3 headers to tweak the replay decode levels. I lose the undo, but it will work with every decoder everywhere, and it's still a lossless transformation.
Learn about Linux
Download Linux
Get Linux help
mp3 gain is very messy
Posted by: Anonymous Coward on February 28, 2007 11:07 PM[...]Then, after analyzing the file, it can save information to the MP3's metadata in the APEv2 format[...]
But this is patently false, because mp3 metadata is not in the APEv2 format. To many mp3 compliant programs, the APEv2 data is garbage noise in the mp3 stream, and adding a foreign tag to mp3 files is ungainly and awful.
To split hairs of course id3 and id3v2 tags are also not compliant mpeg audio layer 3 data, but nearly every mp3 decoding program has been improved to handle them. When you start adding random other "tags" (ie. blobs of data) to the end of the file, however, all bets are off.
id3v2 is extensible, so mp3gain should use custom fields in id3v2.
Since it does not, I simply have mp3gain adjust the mp3 headers to tweak the replay decode levels. I lose the undo, but it will work with every decoder everywhere, and it's still a lossless transformation.
#