<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">Hi Mitchell,<DIV><BR class="khtml-block-placeholder"></DIV><DIV><DIV><DIV>On Feb 12, 2007, at 12:08 PM, Mitchell S. Honnert wrote:</DIV><BLOCKQUOTE type="cite"><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV>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.</DIV><DIV> </DIV><DIV>I have a quick follow-up question. What is your criteria for "real-world interoperability consequences"?<BR></DIV></SPAN></BLOCKQUOTE><DIV><BR class="khtml-block-placeholder"></DIV><DIV>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."</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>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.<BR></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Does that make sense?</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>-- Ernie P.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV><BR class="khtml-block-placeholder"></DIV><BR><BLOCKQUOTE type="cite"><SPAN class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: 0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; white-space: normal; widows: 2; word-spacing: 0px; "><DIV> 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.</DIV><DIV> </DIV><DIV>Again, thanks for your reply. I hope that the list has found resource that can help address these problems from within.</DIV><DIV> </DIV><DIV> - Mitchell S. Honnert</DIV><DIV><FONT face="Arial" size="2"></FONT> </DIV><DIV>----- Original Message -----</DIV><BLOCKQUOTE dir="ltr" style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px"><DIV style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black; font-family: arial; font-size: 13.3333px; "><B style="font-family: arial; font-size: 13.3333px; font-weight: bold; "><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; font-weight: bold; ">From:</SPAN></B><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; "> </SPAN><A title="prabhaka@apple.com" href="mailto:prabhaka@apple.com"><SPAN class="Apple-style-span" style="color: rgb(0, 0, 238); font-family: arial; font-size: 13.3333px; -khtml-text-decorations-in-effect: underline; ">Ernest Prabhakar</SPAN></A><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; "></SPAN></DIV><DIV style="FONT: 10pt arial; font-family: arial; font-size: 13.3333px; "><B style="font-family: arial; font-size: 13.3333px; font-weight: bold; "><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; font-weight: bold; ">To:</SPAN></B><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; "> </SPAN><A title="id3v2@id3.org" href="mailto:id3v2@id3.org"><SPAN class="Apple-style-span" style="color: rgb(0, 0, 238); font-family: arial; font-size: 13.3333px; -khtml-text-decorations-in-effect: underline; ">id3v2@id3.org</SPAN></A><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; "></SPAN></DIV><DIV style="FONT: 10pt arial; font-family: arial; font-size: 13.3333px; "><B style="font-family: arial; font-size: 13.3333px; font-weight: bold; "><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; font-weight: bold; ">Sent:</SPAN></B><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; "> Sunday, February 11, 2007 8:05 PM</SPAN></DIV><DIV style="FONT: 10pt arial; font-family: arial; font-size: 13.3333px; "><B style="font-family: arial; font-size: 13.3333px; font-weight: bold; "><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; font-weight: bold; ">Subject:</SPAN></B><SPAN class="Apple-style-span" style="font-family: arial; font-size: 13.3333px; "> Re: [ID3 Dev] Apple iTunes complicance issues</SPAN></DIV><DIV><BR></DIV>Have you filed a bug? <DIV><BR class="khtml-block-placeholder"></DIV><DIV><A href="http://developer.apple.com/bugreporter/bugbestpractices.html"><SPAN class="Apple-style-span" style="color: rgb(0, 0, 238); -khtml-text-decorations-in-effect: underline; ">http://developer.apple.com/bugreporter/bugbestpractices.html</SPAN></A></DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>If you can file a specific bug explaining the concrete, real-world interoperability consequences, I can help escalate it to the iTunes team.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>-- Ernie P.</DIV><DIV><DIV><BR><DIV><DIV>On Feb 9, 2007, at 6:46 PM, Dale Preston wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><SPAN class="Apple-style-span" style="WORD-SPACING: 0px; FONT: 12px Helvetica; TEXT-TRANSFORM: none; COLOR: rgb(0,0,0); TEXT-INDENT: 0px; WHITE-SPACE: normal; LETTER-SPACING: normal; BORDER-COLLAPSE: separate; border-spacing: 0px 0px; -khtml-text-decorations-in-effect: none; -apple-text-size-adjust: auto; orphans: 2; widows: 2"><DIV class="Section1"><P class="MsoNormal"><SPAN class="Apple-style-span" style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"><SPAN class="Apple-style-span" style="font-family: Calibri; font-size: 14px; ">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 frame.</SPAN></SPAN><O:P style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"></O:P></P><P class="MsoNormal"><O:P style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"><SPAN class="Apple-style-span" style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"></SPAN></O:P></P><P class="MsoNormal"><SPAN class="Apple-style-span" style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"><SPAN class="Apple-style-span" style="font-family: Calibri; font-size: 14px; ">And, of course, there’s the issue of iTunes defaulting to the obsolete ID3V2.2 tag in the first place.</SPAN></SPAN><O:P style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"></O:P></P><P class="MsoNormal"><O:P style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"><SPAN class="Apple-style-span" style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"></SPAN></O:P></P><P class="MsoNormal"><SPAN class="Apple-style-span" style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"><SPAN class="Apple-style-span" style="font-family: Calibri; font-size: 14px; ">Dale</SPAN></SPAN><O:P style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"></O:P></P><P class="MsoNormal"><O:P style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"><SPAN class="Apple-style-span" style="FONT-SIZE: 14px; FONT-FAMILY: Calibri"></SPAN></O:P></P></DIV><BR class="Apple-interchange-newline"></SPAN></BLOCKQUOTE></DIV><BR></DIV></DIV></BLOCKQUOTE><BR class="Apple-interchange-newline"></SPAN></BLOCKQUOTE></DIV><BR></DIV></BODY></HTML>