[ID3 Dev] iTunes id3 tag v2.4

[Ben Bennett]

> What is going on here? I'm getting the urge to just jump in and code  
> my own id3 tag library, but with so many out there, there's no reason  
> why it should be breaking so badly. Is there something seriously  
> wrong with the iTunes id3 v2.4 implementation? Shouldn't there be a  
> work-around still?

The problem probably is that Apple screwed up their 2.4 implementation
and _did not_ use syncsafe integers for the lengths.  So if the frame
is > 127 bytes then the size will be misread.

Prior to 2.4 the length was not syncsafe, and this changed with v
2.4.  But Apple seemed not to have noticed.  They also didn't change
the flag field to the 2.4 form when I converted a 2.3 tag in
iTunes...

I have come to the conclusion that 2.4 is implemented differently by
every package that writes it and there is no way to write a portable
2.4 tag.  I recommend not writing 2.4.

Which is too bad, becuase I wanted to use UTF-8.

		      -ben

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