> I'm pretty sure that's all winamp does, too. But it still plays. :)
I've
> posted a slightly more informative report to bugzilla, along with a link
to a
> file that has an offending tag.
Perfect -- I'll get it taken care of before we release 2.0 on November 15th.
> > I don't remember why we made the decision not to use the id3lib stuff,
> > and roll our own. It may have been because we originally had the
> > philosophy that we were trying to avoid users having to get 57
> > not-commonly-installed libraries before they could compile (this is
That was one of the reasons, but more importantly I tried to run the id3v2
code on linux about a year ago with dismal results. Just before I wrote the
cheese-ass-let's-read-only-the-most-crucial-T-tags-id3v2-read-only
implementation I checked the website for an update and was pointed to
MusicMatch, where I could find no mention of an updated library. We would
very much like to have full read/write ID3v2 capabilities in FreeAmp, and if
you can provide us with a comprehensive library that runs under Linux I'd be
more than glad to incorporate it into FreeAmp. Any chances of this happening
in the next week? :-)
> Well, the id3v2 development has been stagnant for almost a year, at least
> according to the id3.org site and the date of the last id3lib update. As
> mentioned previously, it seems that musicmatch has taken over the id3lib
> project, but I haven't been able to find anything on their site that
mentions
> continued development with the library. This itch is a particularly
important
> one to me, as I have quite a few songs with large id3v2 tags and no linux
> player (to my knowledge) that plays them correctly. I'll continue hacking
> id3lib to make it usable in linux, and if anyone decides that using id3lib
in
> freeamp would be a good idea, I'd be glad to help with this effort.
<soapbox><brutalhonesty>
Do you have a vested interest in ID3v2? Personally, I cannot stand ID3v2.
Its obfuscated, too complicated and it tries to save every last possible bit
of space at the expense of ease of implemtation. (I have written a complete
ID3v2 library in Perl, so I *know*)
We could do this much easier with XML. It could be much more powerful and
the only ID3v2 code we would have to write it code to translate the existing
tags to the XML format. I've even got a rough draft of a proposed
replacement for ID3v2 using XML. I really think it would be worth it for us
to consider doing this. We can have all the features of ID3v2 and a ton more
with a lot of flexibility, with much less code to write. A good standards
document (RFC?) and a bare minimum of code and an XML parser. (And half a
tank of gas....)
Anyone interested?
</brutalhonesty></soapbox>
--ruaok Freezerburn! All else is only icing. -- Soul Coughing
Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert
