[ID3 Dev] ID3v2.5

[Tom Sorensen]

I disagree completely. If this was true, there wouldn't be nearly as
many tag editors, metadata services (with multiple versions of albums
in them), and so forth. Tag editing is certainly frequent enough to be
a concern. Padding is essential.

And, frankly, as far as encoding goes -- why not just mandate UTF-8
and be done with it? There would certainly be some breakage from files
encoded in other codepages, but there's a lot of breakage there
already.

And, finally, getting anything new adopted at this point would be nigh
impossible. ID3v2.4 is still pretty well unsupported. A simpler tag
structure would help, but unless you get industry giants onboard
(Apple, Creative, WinAmp, various chipset manufacturers, etc) then
expect adoption to occur sometime next decade, if ever.

As someone else said, simply adding UTF-8 to ID2v2.3 and marking it as
v2.3.1 ($03 01 in the header) would probably be a far better option.
And clarify multiple genres (space or NULL separated), along with any
other simple issues. ID3v2.3 is far from perfect, but it's at least
widespread and well adopted. And existing libraries (even dead ones,
like id3lib) could be trivially modified to support the changes.

Tom

On 2/27/06, Michal Vician <id3v2 at audiott.com> wrote:
> > Having the tag at the beginning of the file and no padding means that a
> > rewrite of the entire file will often be necessary if the tag is
> > modified.
>
> This is very disputable, because user mostly edits the tag only once and
> then burns it on CD. In this case there is no need to rewrite entire file
> again and again...
>
> Regards
> Miso
>
>
> ---------------------------------------------------------------------
> 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