bug in header size fld?
kde-dev at emailgoeshere.com
Fri Oct 19 14:27:43 CEST 2007
> however, i've got another Q; according to the id3v2.4
> spec, section 3, "The bitorder .. is most significant
> bit first", ie BE byte order. i'm running off x86 so
> i've got LE byte order and if we look at the header of
> a sample mp3 tag from a file which has a tag size of
> 1083 bytes (was empty file, with a tag resulting in
> 1093 file size):
> 4449 0433 0000 0000 3b08 5054 3145 0000
> I D 3 004 \0 \0 \0 \0 \b ; T P E 1 \0 \0
> looking at bytes 7-10 (the tag size) '0000 3b08', we
> see this size stored as a LE synchsafe int,
> representing 1083 bytes.
> therefore, is this a bug in the byte ordering code or
> is it something i misunderstanding from the spec?
I suppose that depends...have you checked to see how large your tag actually
is? As a synchsafe big int, that would work out to 7,560, which would be
large but not anywhere out of the range of possibilities.
More information about the taglib-devel