[ID3 Dev] Apple iTunes complicance issues
prabhaka at apple.com
Mon Feb 12 15:41:47 PST 2007
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.
> I think that by definition ID3 developers are a nitpicky lot, so
> I'm not asking about highly esoteric issues in rarely used frames.
> But it seems to me that problems like the ID3v2.4 non-syncsafe size
> issue and iTunes inexplicable preference for a deprecated ID3
> version (ID3 v2.2) would cause interoperability consequences that
> would warrant attention from Apple.
> Again, thanks for your reply. I hope that the list has found
> resource that can help address these problems from within.
> - Mitchell S. Honnert
> ----- Original Message -----
> From: Ernest Prabhakar
> To: id3v2 at id3.org
> Sent: Sunday, February 11, 2007 8:05 PM
> Subject: Re: [ID3 Dev] Apple iTunes complicance issues
> Have you filed a bug?
> If you can file a specific bug explaining the concrete, real-world
> interoperability consequences, I can help escalate it to the iTunes
> -- Ernie P.
> On Feb 9, 2007, at 6:46 PM, Dale Preston wrote:
>> Apple iTunes suffers from the same problem as Windows Media Player
>> 11 when it comes to ID3V2.2 TYE and ID3V2.3 TYER frames. In both
>> tag versions iTunes adds a leading and trailing zero byte to the
>> And, of course, there’s the issue of iTunes defaulting to the
>> obsolete ID3V2.2 tag in the first place.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ID3v2