[ID3 Dev] How do I deal with this problem COMM frame

[Paul Taylor]

Ben Bennett wrote:
> Note that when reading a 2.4 tag, you need to implement heuristics to
> pick up on iTunes' messed up frames.  You can look at the size and see
> if it could be syncsafe (i.e. if any high bits are set on the 4 bytes
> then you know it is not syncsafe), and if it could be syncsafe then
> you will need to read to the end of the frame then check to see if the
> next data looks like a frame (or if you have hit the end of the
> buffer).  In which case you need to try it as a non-syncsafe length
> and see if you find a valid frame.  This is all assuming the frame
> length is 255 or more, if it's less then you are all set.
>
> 	  -ben
>
>   
Actually I think the safe limit is 127 (01111111), any higher than that 
and sysncsafe/nonsyncsafe vary, although if the value
is between 127 and 255 you can guarantee it is NOT sync safe.

paul


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