[ID3 Dev] Sync-safe sizes?

[Mike van Bokhoven]

I was wondering about that - I was beginning to think about really awful
ways to verify the frame size, such as checking for an apparently valid
frame header following each frame before the last one. Wrong for several
reasons, but when reading a 2.4 frame with obviously invalid sizes, what
else can be done?

For now, my app will continue to write 2.3 by default I think, it seems
safer. Once I get to grips with ID3 better (have been working with it for
the grand total of a day or so) I might look at going to 2.4, if the support
is out there. 2.3's been quite co-operative in general; I'm reading, parsing
and updating the basic standard frames, and writing all frames out again.
Working on APIC support now, hence the size problem!

Thanks again for the info,

Mike.



----- Original Message ----- 
From: "Ben Allison" <benski at winamp.com>
To: <id3v2 at id3.org>
Sent: Thursday, May 17, 2007 4:32 PM
Subject: Re: [ID3 Dev] Sync-safe sizes?


> Applications not writing syncsafe frame sizes in ID3v2.4 has been a major
> issue for widespread adoption of 2.4.  I'm sure the mailing list archives
> have more to say - unfortunately there's not an easy answer.
>
> -Ben Allison
>
> > Hi Jim,
> >
> > Thanks for the quick response! OK, that's good - that's exactly what my
> > code
> > does now. I thought I must be missing something obvious; I thought I'd
> > checked the frame size specs too, but obviously not! I'll have a read,
and
> > update as required.
> >
> > Mike.
>
>
> ---------------------------------------------------------------------
> 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