Conrad J. Sabatier | 21 Apr 2012 11:55
Picon
Gravatar

id3v2 (the app): a question re: tag data formatting

I've recently begun experimenting with doing a little coding in C to
manipulate ID3 tags, and have come across something that surprised me.

Briefly, the code I've written so far just parses the ID3 tag and spits
out the raw data from each frame.  What's surprising to me is that the
actual data in many frames contains leading zeroes.  I'm just wondering
why this is.  I've used the id3v2 program to tag most of my files.

Can anyone offer any insight into this?  Is this an expected/required
behavior, or possibly a bug in the id3v2 implementation?

Thanks!

--

-- 
Conrad J. Sabatier
conrads <at> cox.net
Josh Twigg | 21 Apr 2012 12:36
Picon

Re: id3v2 (the app): a question re: tag data formatting

It is my understanding that if the frame has $00 before it then it implies ascii, $01 then it is unicode. I suggest you give the specification a good read.

Good luck with your program



On 21 April 2012 10:55, Conrad J. Sabatier <conrads <at> cox.net> wrote:
I've recently begun experimenting with doing a little coding in C to
manipulate ID3 tags, and have come across something that surprised me.

Briefly, the code I've written so far just parses the ID3 tag and spits
out the raw data from each frame.  What's surprising to me is that the
actual data in many frames contains leading zeroes.  I'm just wondering
why this is.  I've used the id3v2 program to tag most of my files.

Can anyone offer any insight into this?  Is this an expected/required
behavior, or possibly a bug in the id3v2 implementation?

Thanks!

--
Conrad J. Sabatier
conrads <at> cox.net

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


Conrad J. Sabatier | 21 Apr 2012 13:51
Picon
Gravatar

Re: id3v2 (the app): a question re: tag data formatting

On Sat, 21 Apr 2012 11:36:39 +0100
Josh Twigg <twigg321 <at> gmail.com> wrote:

> It is my understanding that if the frame has $00 before it then it
> implies ascii, $01 then it is unicode. I suggest you give the
> specification a good read.

Ah, yes, of course!  Somehow I forgot about that.

I really do need to read the spec again more carefully.  :-)

> Good luck with your program

Thanks!

> On 21 April 2012 10:55, Conrad J. Sabatier <conrads <at> cox.net> wrote:
> 
> > I've recently begun experimenting with doing a little coding in C to
> > manipulate ID3 tags, and have come across something that surprised
> > me.
> >
> > Briefly, the code I've written so far just parses the ID3 tag and
> > spits out the raw data from each frame.  What's surprising to me is
> > that the actual data in many frames contains leading zeroes.  I'm
> > just wondering why this is.  I've used the id3v2 program to tag
> > most of my files.
> >
> > Can anyone offer any insight into this?  Is this an
> > expected/required behavior, or possibly a bug in the id3v2
> > implementation?
> >
> > Thanks!

--

-- 
Conrad J. Sabatier
conrads <at> cox.net

Gmane