[ID3 Dev] An addition for the Compliance Issues list.

[Dale Preston]

Yeah, as Jud said, as well.  That was hard to accept; I've been doing it
wrong for 2 years.  

Dale


-----Original Message-----
From: Mark Smith [mailto:masmit at gmail.com] On Behalf Of Mark Smith
Sent: Friday, February 09, 2007 8:54 PM
To: id3v2 at id3.org
Subject: Re: [ID3 Dev] An addition for the Compliance Issues list.

The spec also says, with regard to all the text frames excluding TXXX:

4.2 <Header for 'Text information frame', ID: "T000" - "TZZZ",
      excluding "TXXX" described in 4.2.2.>
      Text encoding                $xx
      Information                  <text string according to encoding>

And it doesn't specifically exclude the TYER frame. Nor does it  
exclude the TYER frame from being a null-terminated string. The data  
itself is still just 4 chars, so it seems kind of open to  
interpretation. iTunes 7 does the same (nulls front and back), for  
what it's worth.

On the other hand, maybe MS and Apple are thinking really, really  
long-term, and are leaving space in there for the year 10000 and beyond.

Mark


On 10 Feb 2007, at 02:05, Dale Preston wrote:

> I have a couple additions for the compliance issues list.
>
>
>
> Windows Media Player 10 creates improper ID3V2.3 TYER frames.  They  
> are 5 bytes long though the standard specifically states they are  
> always 4 bytes long.  The leading byte is a zero value.
>
>
>
> Windows Media Player 11 leads with a zero value byte but also  
> appends a zero value byte, giving a length of 6 bytes for the  
> ID3V2.3 TYER frame.
>
>
>
> I can provide samples if necessary.
>
>
>
>
>
> Dale
>
>
>
>


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



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