[ID3 Dev] Apple iTunes complicance issues

[Jud White]

Apple replied to one of the bugs I opened last night.  I reported the 
syncsafe problem and the non-Latin1 APIC problem; they replied to the 
text encoding problem, just asking for a sample file but it's a start.

I think it's in the wording
1. ID3v2.4 frame sizes written incorrectly (should be syncsafe)
2. ID3v2: "APIC" frame with non-Latin1 encoding is not read by iTunes

If I don't get a reply to #1 in a couple days I'll open a new one that 
says iTunes can't read multiple pictures in ID3v2.4. :)

Ernest Prabhakar wrote:
> Hi Mitchell,
>
> On Feb 12, 2007, at 12:08 PM, Mitchell S. Honnert wrote:
>> Hello Ernie.  I'm sure most of the members of this list would greatly 
>> appreciate any help you could give with resolving the iTunes ID3 
>> compliance issues.  As you can see from the other responses, there 
>> are some fairly big problems with the way iTunes implements the ID3 
>> standards.
>>  
>> I have a quick follow-up question.  What is your criteria 
>> for "real-world interoperability consequences"?
>
> Thanks for your query, and I can appreciate your concern.  The sort of 
> data I'm looking for is "When I obtain an MP3 track from this legal 
> download site, it contains this information which is *not* usable from 
> iTunes."
>
> That is, while I realize you live in a world where spec conformance is 
> its own reward, I need to be able to provide concrete customer usage 
> problems to motivate change.
>
> Does that make sense?
>
> -- Ernie P.
>
>
>



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