[ID3 Dev] Worst cases of "ID3 offenders"?

[Andy Kernahan]

XP doesn't actually support V2.4.0 and therefore has no need to support 
UTF16-BE.

----- Original Message ----- 
From: "Robert Manson" <rmanson at gracenote.com>
To: <id3v2 at id3.org>
Sent: Wednesday, November 09, 2005 1:38 AM
Subject: RE: [ID3 Dev] Worst cases of "ID3 offenders"?


Windows XP does not read UTF16-BE encoded text frames

-----Original Message-----
From: Paul Grebenc [mailto:jid3 at blinkenlights.org]
Sent: Tuesday, November 08, 2005 2:51 PM
To: id3v2 at id3.org
Subject: Re: [ID3 Dev] Worst cases of "ID3 offenders"?


The MP3ext Windows explorer extension corrupts all of its ID3 v2 tags by

repeatedly writing an advertisement for itself (ie. "MP3ext
V3.3.18(unicode)") in the tag padding, which violates the spec.

Winamp ignores the last frame in a v2.3.0 tag if there is no padding in
the tag.

Mixmeister BPM analyzer (among others it seems) writes floating point
values to the TBPM frame.

Paul

---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org




---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org




---------------------------------------------------------------------
To unsubscribe, e-mail: id3v2-unsubscribe at id3.org
For additional commands, e-mail: id3v2-help at id3.org