<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content=text/html;charset=iso-8859-1>
<META content="MSHTML 6.00.6000.16587" name=GENERATOR></HEAD>
<BODY id=MailContainerBody
style="PADDING-RIGHT: 10px; PADDING-LEFT: 10px; PADDING-TOP: 15px"
bgColor=#ffffff leftMargin=0 topMargin=0 CanvasTabStop="true"
name="Compose message area">
<DIV><FONT face=Arial size=2>I recently started hearing from users of my
applications about new issues related to Apple iTunes implementation of COMM
frames. While this may or may not be a new issue, it is a new issue to me
and my applications.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>In samples I have received from users, there are
COMM frames with null bytes included in the actual text field for the COMM
frame. The text of the COMM frame is:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV> <FONT face=Arial
size=2>"engiTunes_CDDB_TrackNumber<NULL BYTE HERE>1"</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>where the null byte replaces the brackets and text
indicating its location above. The "eng" in the text above is not the
language attribute of the COMM frame but is included in the actual
text.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>The result of having a null byte in the middle of a
string is that it appears to be an array of strings. This is sure another
unexpected issue to have to deal with because of Apple's inability or refusal to
follow the standard.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Dale</FONT></DIV>
<DIV> </DIV></BODY></HTML>