Odd APIC frame

[Norman Palardy]

On Jul 13, 2006, at 7:55 PM, Brian Kerrick Nickel wrote:

> I ran into this problem recently with some podcasts. The problem is  
> that APIC (2.3+) and PIC (2.2) handle file type differently. APIC  
> uses a Latin-1 string followed by a nul byte to represent file  
> types. Say, "image/png\0". PIC, on the other hand, uses just three  
> bytes, so "PNG" (no termination). As the parser currently searches  
> for the next nul byte, and 2.2 doesn't have one in the traditional  
> place, the parsing goes haywire and the frame corrupts.

Thanks for the lucid explanation

Norman Palardy
OS X 10.4.6 / MacBook Pro 2.16Ghz MHz / 2Gb RAM