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

[Dale Preston]

Whoops.  My mistake here.  I apologize.

Four characters is not the same as four bytes.

Back to the drawing board.  Thanks for clearing it up.

Dale

-----Original Message-----
From: Dale Preston [mailto:dalepres at msn.com] 
Sent: Friday, February 09, 2007 9:51 PM
To: id3v2 at id3.org
Subject: RE: [ID3 Dev] An addition for the Compliance Issues list.

TYER
The 'Year' frame is a numeric string with a year of the recording. This
frames is always four characters long (until the year 10000).


I guess that's the reason there's a list like this.  Reasonable men disagree
on the interpretation of the specification as written. :)

Dale


-----Original Message-----
From: Jud White [mailto:jwhite at cdtag.com] 
Sent: Friday, February 09, 2007 9:45 PM
To: id3v2 at id3.org
Subject: Re: [ID3 Dev] An addition for the Compliance Issues list.

4.2.   Text information frames

   The text information frames are the most important frames, containing
   information like artist, album and more. There may only be one text
   information frame of its kind in an tag. If the textstring is
   followed by a termination ($00 (00)) all the following information
   should be ignored and not be displayed. All text frame identifiers
   begin with "T". Only text frame identifiers begin with "T", with the
   exception of the "TXXX" frame. All the text information frames have
   the following format:

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

Hope this helps.

Dale Preston wrote:
> If I understand the published specification, the TYER frame is not a
> terminated string which would start with an encoding byte but is, instead,
a
> numeric string.  The spec states specifically "always four characters
long".
> Is this not correct?
>
>
> Dale
>
>
>
> -----Original Message-----
> From: Jud White [mailto:jwhite at cdtag.com] 
> Sent: Friday, February 09, 2007 8:45 PM
> To: id3v2 at id3.org
> Subject: Re: [ID3 Dev] An addition for the Compliance Issues list.
>
> Dale,
>
> It's the text encoding byte, and the terminator is optional, at least to 
> the point where the spec says ignore anything that comes after a 
> terminator in a text field.
>
> Brian Mearns wrote:
>   
>> They must be preparing for the Y10K bug.
>>
>> -Brian
>>
>> 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
>
>
>
> ---------------------------------------------------------------------
> 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



---------------------------------------------------------------------
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