From conrads at cox.net Sat Apr 21 04:51:59 2012 From: conrads at cox.net (Conrad J. Sabatier) Date: Sat, 21 Apr 2012 06:51:59 -0500 Subject: [ID3 Dev] id3v2 (the app): a question re: tag data formatting In-Reply-To: References: <20120421045530.679bf1fa@cox.net> Message-ID: <20120421065159.71a0150e@cox.net> On Sat, 21 Apr 2012 11:36:39 +0100 Josh Twigg 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 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 From conrads at cox.net Sat Apr 21 02:55:30 2012 From: conrads at cox.net (Conrad J. Sabatier) Date: Sat, 21 Apr 2012 04:55:30 -0500 Subject: [ID3 Dev] id3v2 (the app): a question re: tag data formatting Message-ID: <20120421045530.679bf1fa@cox.net> 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 From twigg321 at gmail.com Sat Apr 21 03:36:39 2012 From: twigg321 at gmail.com (Josh Twigg) Date: Sat, 21 Apr 2012 11:36:39 +0100 Subject: [ID3 Dev] id3v2 (the app): a question re: tag data formatting In-Reply-To: <20120421045530.679bf1fa@cox.net> References: <20120421045530.679bf1fa@cox.net> Message-ID: 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 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 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: