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

[Dale Preston]

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