[ID3 Dev] Info Sought

[Andy Kernahan]

Opps, sorry. The maximum safe-sync value is 0xFFFFFFF.

    Andy.

----- Original Message ----- 
From: "Andy Kernahan" <andrew.kernahan at btinternet.com>
To: <id3v2 at id3.org>
Sent: Thursday, October 27, 2005 7:22 PM
Subject: Re: [ID3 Dev] Info Sought


> Kirk,
>
>    the answer to your other question is 7F 7F 7F 7F for a maximum value 
> sync-safe integer. As the for the comment frame it has the following 
> structure:
>
> text encoding ID (1byte),
> language ID (3bytes (3 ASCII chars)),
> description (null terminated (\0)),
> body of text.
>
> Below is an example of the structure:
>
> \0engThis is the null terminated description\0This is the rest of the body 
> of the frame
>
> There are a few other frames that use null terminated strings - APIC, POPM 
> and the GEOB frames spring to mind.
> Tom is right thought, if you are only going to be using Winamp to play 
> your music then you need only code around the v2.3.0 std as later versions 
> of ID3 are not supported by Winamp.
>
> Hope this helps,
>
> Andy.
>
> ----- Original Message ----- 
> From: "Tom Sorensen" <tsorensen at gmail.com>
> To: <id3v2 at id3.org>
> Sent: Thursday, October 27, 2005 2:16 PM
> Subject: Re: [ID3 Dev] Info Sought
>
>
> Again, do not use ID3v2.4 if you want Winamp to read the results.
> Winamp will not read any v2.4 tags. You need to use
> http://www.id3.org/id3v2.3.0.html as your reference instead.
>
> As for VB libraries, I do not know VB, but if you Google for "vb id3"
> there seems to be a good number of hits, including this:
> http://www.pstruh.cz/tips/detpg_change-id3-tags-script/
>
> I can answer at least one of your questions...
>
>> The next byte is (always?) a zero and the actual information starts
>> after that.
>
> No, that byte is part of the frame data (you must include it in frame
> length!), is only present for text field data, and indicates if the
> data is Unicode or not. The reference to it in the ID3v2.3 docs is
> rather buried though, so here it is:
>
> "Frames that allow different types of text encoding have a text
> encoding description byte directly after the frame size. If ISO-8859-1
> is used this byte should be $00, if Unicode is used it should be $01."
>
> Note that for ID3v2.3 "Unicode" means UTF-16. v2.4 is more flexible,
> but, again, I recommend against using it if you want to use Winamp.
>
> ---------------------------------------------------------------------
> 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