352013-12-05 21:50:04DanONeillRemoved an entry that is not a compliance issue.342013-12-02 21:02:21DanONeillRemoved wikilink syntax around Windows Media Player and Windows 7 entries.332012-11-01 19:28:53drjackool322012-11-01 19:26:48drjackool312012-10-30 13:17:20drjackool302012-10-30 13:15:13drjackool292012-10-30 13:12:18drjackool282012-10-08 22:15:40localhostconverted to 1.6 markup272011-03-31 09:05:26217-155-98-246.dsl.in-addr.zen.co.uk262010-06-21 09:29:16217-155-98-246.dsl.in-addr.zen.co.uk252010-06-21 09:28:11217-155-98-246.dsl.in-addr.zen.co.uk242010-06-21 09:27:09217-155-98-246.dsl.in-addr.zen.co.uk232010-05-15 21:17:32188-192-236-215-dynip.superkabel.deremoved "Cannot read V24 frames" as a compliance issue in Windows Explorer. Explorer is not advertised as being able to interpret id3v2.4, and a missing feature is NOT a compliance issue.222010-05-15 21:14:14188-192-236-215-dynip.superkabel.deremoved "Doesn't use TPE2 for Album Artist" as a compliance issue for f2k. TPE2 is misused by both iTunes and WMP as ALBUM ARTIST, TPE2 is NOT defined that way in the specs.212010-04-24 05:56:29217-155-98-246.dsl.in-addr.zen.co.ukFixed errors202010-04-15 19:09:32217-155-98-246.dsl.in-addr.zen.co.ukFoobar v23 multriple string fields192010-04-15 13:03:21217-155-98-246.dsl.in-addr.zen.co.ukFoobar page182010-04-15 13:01:57217-155-98-246.dsl.in-addr.zen.co.ukFoobar 2000 doesnt use Album Artist172010-04-15 12:50:52217-155-98-246.dsl.in-addr.zen.co.ukWindows Explorer only understands ID3v23162010-04-15 12:24:57217-155-98-246.dsl.in-addr.zen.co.ukWindows Media Player doesn't like TMOO frame152009-08-26 13:24:56webgw2.mh.bbc.co.uk142008-09-11 14:07:13cpc2-leed4-0-0-cust808.leed.cable.ntl.com132008-09-11 14:06:37cpc2-leed4-0-0-cust808.leed.cable.ntl.com122008-09-11 14:05:22cpc2-leed4-0-0-cust808.leed.cable.ntl.com112008-09-11 14:03:48cpc2-leed4-0-0-cust808.leed.cable.ntl.com102008-04-01 15:29:25brixeng.brixnet.comClarified NCON92008-02-25 11:32:40cpc1-leed4-0-0-cust535.leed.cable.ntl.com82008-02-24 21:26:40DanONeill72007-11-21 05:55:51DanONeill62007-09-19 23:34:26ayup.limey.netAdded bad 2.4 frame length support info for itunes52007-01-11 15:08:34BenAllisonforgot one42007-01-11 15:01:01BenAllisonNoted fixes for Winamp bugs. *** WinAmp -> Winamp32006-12-17 00:26:12DanONeill22006-12-17 00:20:00DanONeill12006-12-17 00:19:36DanONeill

Not all players and tag editors are compliant to the ID3v2 standard. This page contains a list of applications and the symptoms you might experience. If you have corrections, please join the Mailing List and tell us what should be changed. This list was compiled by Mitch Honnert from comments and descriptions on the ID3v2 developers list. ID3 VersionApp/Lib/EncoderSymptomDescriptionSubmitterv2.3WinampRX & CV genres not recognizedWinamp (5.35) doesn't recognise the RX or CV genres.PaulTaylorv2.3WinampBad Language field in COMM frameWinamp will record apparently gibberish bytes in the Language field of the Comments (COMM) frame. I don't see any pattern to the bytes, so I'm guessing that it's just some uninitialized variable that's getting written to the Language bytes. (Fixed as of Winamp 5.2)Mitch H.v2.3WinampDescription field in the COMM frame is ignoredWinamp does not take into account the Description field of the Comments (COMM) frame when reading a tag with more than one COMM frame. Instead of using the COMM frame where the Description field is blank to set the "Comment" field on the "MPEG file info + ID3 tag editor", Winamp displays whichever COMM frame happens to be read *last*. So, if another app writes two COMM frames to a tag, one without a Description value followed by one with a Description, Winamp will ignore the first generic COMM frame and use the second. This was can happen when using MusicMatch Jukebox to edit a tag (which properly uses COMM frames with Description values to store its Preference, Mood, Situation, and Tempo fields) and using Winamp to read tag. (Fixed as of Winamp 5.2)Mitch H.v2.3iTunesGenres greater than 125 ignorediTunes (7.4.3.1) only recognizes genres in ID3v23 in the form (n) if n is 125 (Dance Hall) or less, nor does it understand the (RX) or (CV) genres. PaulTaylorv2.4iTunesNumeric Genres in ID3v24 format not understoodiTunes (7.6.1) does not understand numeric genres at all unless they are in the ID3v23 Format PaulTaylorv2.3iTunesExtra nullchar in COMM frameiTunes adds an extra nullchar to the end of the Comments frame.Mitch H.v2.3iTunesNon-standard TCMP frameWhen you check the "Part of a compilation" checkbox on the Info tab of the tag editor form, iTunes will add a non-standard TCMP frame to the tag.Mitch H.v2.4iTunesBad frame length handlingiTunes does not treat framelength as a sync safe integer... see iTunes for details.BenBennettv2.3MusicMatchNon-standard NCON frameMusicMatch adds stuff in an unknown format in the NCON frame. These can get quite large.Mitch H., BenBennettv2.3MP3ext Windows ExporerCorrupt padding areaThe 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.Paul Grebencv2.3WinampLast frame ignoredWinamp ignores the last frame in a v2.3.0 tag if there is no padding in the tag. (This issue is fixed as of Winamp 5.2)Paul Grebencv2.3Mixmeister BPM analyzerInvalid values in TBPM frameMixmeister BPM analyzer (among others it seems) writes floating point values to the TBPM (Beats Per Minute) frame.Paul Grebencv2.3Windows XP/Windows Media Player Windows Media Player displays "The input media format is invalid." and will not play file Windows XP does not read UTF16-BE encoded text framesRobert Mansonv2.3Windows Media PlayerDoes not seem to support extended headers.Birkir A. Barkarsonv2.3Windows Media PlayerDoes not seem to support unsynchronization.Birkir A. Barkarsonv2.3Quicktime PlayerDoesn't correctly display unicode characters.Birkir A. Barkarsonv2.3VLC Media PlayerCrashes when reading bad tagSensitive to ill formatted tags and will crash with a memory read error.Birkir A. Barkarsonv2.3Winamp 5 LiteWill not display unicode characters in default mode.(This issue is fixed as of Winamp 5.2)Birkir A. Barkarsonv2.3Windows Media PlayerWon't play an MP3 if certain ill formatted frames are detectedBirkir A. Barkarsonv2.3, v2.4Windows Media Playerv2.4 tag overwritten by v2.3 tagI've seen Windows Media Player write a v2.3 tag to a file that already had a v2.4 tag, resulting in two tags in the same file and thus "disappearance" of the 2.4 tag (as the 2.3 tag is written first, and there is no mechanism in 2.3 for chaining tags).Pytv2.3AudiograbberInvalid language codeThe Audiograbber sets the Language Code field ID3v2.3 frames to "XXX", which is not one of the standard values. If a language is unknown or undefined, the Language Code should be left blank.v2.4iTunesIgnore frames after PRIV framesiTunes does not like PRIV frames and will just ignore them and any frames that follow so if they are at the start of the Tag it reads no data, this is unrelated to whether or not the frames are unsynchronised.PaulTaylorv2.4Windows Media PlayerReads/Write MOOD as PRIV frameCreated as PRIV frame with key WM/Mood instead of using the TMOO frame PaulTaylorv2.3Windows 7Doesnt like Unsynchronized UTF16 fields Displays them as if they were encoded as ASCII (ok on WIndows Vista)PaulTaylor