On Sat, Oct 23, 1999 at 08:50:23AM -0500, Scott Thomas Haug wrote:
> I'm assuming there's nothing wrong with the format of the tags themselves,
> since they were made with musicmatch jukebox and are playable within winamp.
The Winamp test doesn't mean much, unless they've added id3v2 support,
recently. Last I checked, they just skipped stuff in the id3v2 frame,
entirely.
> My assumption is that you aren't using the id3lib, available on the id3.com
> website. If this is an incorrect assumption, please let me know. I am
> currently hacking the library so that it works on linux and comes in a nice gnu
> installer tarball, using automake, autoconf, and such. I'm pretty sure the
> current id3lib download has a windows dll already compiled. This library has
> been released to the public domain, so I was wondering if there was any
> discussion/consideration for using it in freeamp. As I understand it,
> Musicmatch has taken up "official" development of the library, but I haven't
> heard of any public announcement from them, either about their assuming
> responsibility for the library or their plans for future development of it.
I assume that you mean the id3.org website. Check this out:
~$ nslookup www.freeamp.org
Name: fatman.freeamp.org
Address: 209.249.146.48
Aliases: www.freeamp.org
~$ nlsookup www.id3.org
Name: fatman.id3.org
Address: 209.249.146.48
Aliases: www.id3.org
We donate the space to host id3.org and id3v2.org (and id3v3.org, if
anything ever happens, there). :)
> I know little about the freeamp codebase, but if using the id3lib for better
> id3v1/2 tag support would interest folk here, I would be happy to try and help
> integrate it into the project.
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
more of an issue for Linux than Windows, obviously). Anyone remember
why we did this? Generally speaking, I'm a big fan of integrating
existing stuff, rather than rewriting it. At the time, there wasn't
much id3v2 support, so we MAY have decided to roll our own so that
there would be two complete implementations, to help hammer out
compatability issues.
Brett
---
Vice President, Technology, EMusic.com, Inc. -- http://www.emusic.com
