Odd APIC frame

[Norman Palardy]

On Jul 13, 2006, at 2:51 PM, Scott Wheeler wrote:

>
> On Jul 13, 2006, at 10:19 PM, Norman Palardy wrote:
>
>> I'm working with a few mp3 files from various sources.
>>
>> There seems to be a couple that have very odd attached pictures that
>> taglib gets just slightly wrong.
>> Apple's iTunes and MS' Windows Media seem to handle these though.
>
> Just a guess, but this may be the fact that iTunes has a bug in its
> synch safe integer implementation (it doesn't use them, basically),
> so it ends up writing invalid lengths for images which messes things
> up in some cases.  WMP may have a work around for the iTunes bug.
> What are the sizes of the images that aren't being read properly?

Manually I copied the data based on the values in the frame (what  
appears to me to be a a PIC frame) into a new file, saved it and then  
opened it in a image editor. So the value seems to be correct. It was  
only 49974 bytes.

The first 512 bytes of the file are (a snapshot from the hex editor I  
use)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture 1.png
Type: application/applefile
Size: 73 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/taglib-devel/attachments/20060713/6c562cb4/attachment-0001.bin 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Picture 1.png
Type: image/png
Size: 36818 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/taglib-devel/attachments/20060713/6c562cb4/attachment-0001.png 
-------------- next part --------------

When I retrieve the apic frame and iterate over the bytes I see that  
the first 11 bytes of the picture data are not part of the returned data
very odd