Hello!

I was wondering what you are thinking about Enhanced TAG. The idea is not really bad, but there aren't any players capabile of reading or writing the format yet.

Regards,
Sebastian Mares

Meh ?
This "standard" is inferior to apev2, while apev2 is already supported in several different programs.
"TAG+" seems to only attempt to address one of id3v1 issues (field length), while it still doesn't support international characters, or custom fields, and it appears that field lengths are still limited, just the number is greater (bah).
Why even bother ?

À propos APEv2 tags... People here seem to forget one thing: ID3v2 tags were designed to be the first thing that is streamed when the MP3 file is on a streaming server. APEv2 tags, however, are at the end of the file, so they will be the last thing to be received.

BTW, this has nothing to do with TAG+, so it is some kind of off-topic. Sorry.

Does any software in the world actually use id3v2 for streaming ?

I thought Winamp and Windows Media Player do. Correct me if I am wrong.

At least Winamp gathers the meta information from shoutcast and not from any tags. Using id3v2 tags, except for pure HTTP streaming, is pointless.

<edit>

This made me laugh... Are you sure the author of this page is serious about his proposal?
</edit>

Not sure. I found that page while looking for a Genre ID list.

<edit>Argh... it is supposed to be an addition to id3v1... still stupid</edit>

Even Lyrics3 2.00 is better than TAG+, and is even is supported by many players.

It seems that it's only the authors own program "SpeedTag" who support TAG+

Well, I find it hard to understand. ID3v1 had a problem with length limit. So why "fix" it by setting new one if you can store variable-length strings instead (just like all APEv2, ID3v2, vorbiscomment, etc do) ? Even ID3v2 is more useful than this (though it has different kind of bad design issues).

winamp doesn't show id3v2 tags for any streamed mp3

I don't even stream mp3s, so I don't need tags in front of my audio files.