[ID3 Dev] id3v2.4 & frame sizes?

[Mitchell S. Honnert]

Jonathan, while I can't answer your question directly, I can give some
background that might help a little.

>I'm a little surprised that iTunes doesn't fix it.
In my experience iTunes and the other major audio players follow the ID3
standard very well, but there *are* exceptions.  iTunes for example will
insert a completely non-standard TCMP frame if you check "Part of a
compilation" in the ID3 edit form.  So, if the authors of iTunes are willing
to disregard the standard in this way, maybe they disregarded or overlooked
the specification about synch-safe frame sizes.  (BTW, I'm reading the v2.4
spec the same way you are about synch-safe frame sizes.)

It would be a shame if one of the most popular audio players corrupted the
v2.4 standard in the way you describe.  But I wouldn't be surprised if it
did.

Mitchell S. Honnert
www.UltraID3Lib.com


 
-----Original Message-----
From: Jonathan del Strother [mailto:maillist at steelskies.com] 
Sent: Sunday, January 15, 2006 10:54 AM
To: id3v2 at id3.org
Subject: [ID3 Dev] id3v2.4 & frame sizes?

I'm seeing a couple of MP3s that don't have synch-safe frame sizes,  
and wanted to check that I'm reading the specification right.  For  
v2.4, all frame sizes should have a 0 at the start of each byte, right?

I'm pretty sure that's correct, but I tried persuading iTunes to  
convert the tag to 2.3 and then back to 2.4, and the frame size  
remains non-synch-safe - I'm a little surprised that iTunes doesn't  
fix it.


Any idea how common a problem this is?  I'm tempted to read the size  
as a non-synch-safe integer, and see if that offset then lands me on  
what looks like a new frame id.  Or is that a horribly bad idea?

Thanks,
Jon


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