[ID3 Dev] id2v2.4???

[Michael Makuch]

> (foobar2000) only supports writing 2.4 tags 

I discovered this recently. In looking for ReplayGain solutions
I tested out fubar. It silently converted my 2.3 tags to 2.4 
(test data of course). Very poor behavior IMHO. 

I've been relying upon id3lib for 6 years and I'd hate to see
it die a slow death. I have no idea how big an effort it would be 
but I'm one ole code slinger who'd give some time towards
adding 2.4 to it. Clearly it is needed. 

Mike


> Perhaps if 2.4 is adopted by more software then Apple will 
> finally fix the
> problem in iTunes?  (I know I'm probably deluding myself with 
> such wishful
> thinking but I can hope.)  Or perhaps some other work-around 
> can be devised.
> But I still think letting Apple ruin the future of 2.4 just 
> because they
> can't get it right in iTunes would be a tragedy.


> 
> -Jim
> ----- Original Message ----- 
> From: "Ben Bennett" <fiji at ayup.limey.net>
> To: <id3v2 at id3.org>
> Sent: Wednesday, January 03, 2007 10:40 PM
> Subject: Re: [ID3 Dev] id2v2.4???
> 
> 
> > On Wed, Jan 03, 2007 at 05:14:15PM -0800, Robert Manson wrote:
> > > I think we should discourage any tags being written in 2.4 due to
> > > the iTunes bug.
> >
> > Ugh.  That is a shame.
> >
> > I like 2.4's changes to list handling in some of the text frames
> > (making them consistently null separated vs. frame specific rules).
> >
> > I like the improved time handling stuff... making a timestamp format
> > and consolidating the split time fields is nice.
> >
> > I like the sort order frames (but I am not sure if anything uses
> > them)
> >
> > And I love the addition of UTF-8.
> >
> > Unfortunately you are probably correct though :-(
> >
> > As a note, you can work around the problem if you only have 
> one large
> > frame and you put it at the end of the file.  That way 
> iTunes wants to
> > read the longer frame length, but there isn't enough left in the tag
> > to read (or it reads the padding), but then renders the image
> > correctly (since the jpeg/gif/png has its own size info and the
> > trailing junk is ignored).
> >
> > The nasty case occurs if you have multiple frames > 128 bytes, or if
> > the frame contents are not images (or another 
> self-identifying type).
> > Or if you are trying to read a tag iTunes wrote.
> >
> > -ben
> >
> > 
> ---------------------------------------------------------------------
> > 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