Frederic Devernay wrote:

That's the main flaw of id3v2, and yet another reason to switch to APEv2 ;-) I'm just kidding of course, I know id3v2 is more widely supported, but it gives me an occasion to remind you that APEv2 support for mp3 is just a 10-lines patch that doesn't break anything...

For the iRiver, yes...

Btw, just curious, but is the offset parameter only there to support the (IMNSHO brain-dead) case of having an ID3v1 tag after the APE tag?

  Magnus

Reply via email to