Freedb.org Ending
haroldag writes "Freedb, the free music database used by tons of CD ripping software, has been shut down due to a disagreement among its developers. One of its developers used a data dump from the original freedb.org and is providing the service at freedb2.org, though, and will be adding features and posting them at his site as they become available. Unfortunately, a database dump or source code for freedb2.org is yet nowhere to be found."
"Unfortunately, a database dump or source code for freedb2.org is yet nowhere to be found."
So _that_ is why I got the "Nothing to see here" message.
Way too many dupes. I searched for "Post" and this is what I get:
1
misc/2c03fb04
Post Andra rum
2>
rock/7d0ad70b
Björk Post
3>
misc/7d0ad70b
Björk Post
4>
rock/3b04e804
Post Post
5>
rock/9c0beb0c
Bjork Post
6>
misc/800ac80b
Björk Post
7>
newage/800ad70b
Bjork Post
8>
rock/7b0a720b
Björk Post
9>
newage/7b0ad70b
Björk Post
10>
newage/7e0ad70b
Björk Post
So which one am I supposed to choose? Too many dupes. (Your comment has too few characters per line (currently 7.5). Your comment has too few characters per line (currently 8.5). Your comment has too few characters per line (currently 9.4).)
The quality of submissions were total, utter shit. You'd be better off typing in the info yourself.
That sucks. I hope that freedb2 will be compatable with the old freedb protocol. Pretty much every open source tagger/ripper/whatever I know of uses freedb.
:)
Then again, maybe it's time for MusicBrainz to take over.
...that folks just can't seem to get along.
So for programs that use Freedb, e.g. I use dBpowerAMP, does this just mean that they won't be able to grab track listings anymore?
Sigh, FreeBSD, we hardly knew ye.
I'm sorry the staff fell out, costing us access to a useful resource. freedb was a useful tool but it was always in need of improvement.
It really should have had facilities for submitting an md5 hash of the CD so end-users could avoid collisions, perhaps an easy way to edit or rate database entries, so that submissions where the track titles were wrong could be corrected by the community, etc...
Hopefully whatever replaces it will be better and more robust..
--
I have no CDs on hand here at work to see what happens when I try a db lookup, but does it mean that there is no info anymore on freedb on the lookup? Or is it just that any new entries have no-where to go?
What about the mirrors?
alag alaagagagaga
lag alglagl alglaglag lalglagagl
aglagla jsglalg jalgjalgl agalglalglag
a
ga
g
agalgl aglagl aglalgalg laglaglalgagl
That is all.
""Freedb, the free music database used by tons of CD ripping software, has been shut down due to a disagreement among its developers."
And in other news. Slashdot has been shut down due to a disagreement between Taco and CowboyNeal. The former likes the new layout, while the latter hates it. Apparently one of the readers has mirrored a copy of the "/. database to slashdot2, which will be undergoing a year long "burning server" effect.
Oh well - I'm probably going to get flamed for this....
but there's no honor among theives.
Just stop being a bunch of cheap a-holes and BUY music that you like.
[Connection closed by foreign host]
"Another One Bites The Dust" ?
spoonerize "magic trackpad"
I am the author of freedb2.org. It currently supports a subset of the old freedb protocol, enough to rip your CD's. Just point your software at http://freedb2.org/~cddb/cddb.cgi. There are also some new features which I will be documenting shortly. For some source code and a development history, please see http://asmith.id.au/freedb.html and also http://asmith.id.au/mod_libpq.html.
I hate to see things like this its sad when projects fail just because people can't seem to work together.
TheADDkid.com
"Freedb, the free music database used by tons of CD ripping software, has been shut down due to a disagreement among its developers." ...What a db.
I just now remembered what I did once, quite a while ago:
.wav, burned them to CD using gcdmaster, and ripped them to OGG, only to find that the ripping program actually guessed *correctly* the album and the titles of all the included songs.
I recorded some of my (difficult-to-find) LPs to
Note that even though I marked the beginning and end of each song manually, it still found the right titles. freedb really rocks!
On one hand, I guess I can't criticize them too harshly, because it's not as though many of us (myself included) who are using the service were paying the developers any for their time, on the other hand, it seems a little unfortunate that the one developer decided to just abruptly pull the plug on the service when it was in use by so many people, without trying to see if there were others in the community of users willing to take over the project, if he no longer wanted to manage it.
It seems like there were three people on the project, and two of them wanted to take it non-free, one didn't; although I'm glad the remaining developer didn't go along with the other guys if they really wanted to make it non-free, I can't really understand why he would choose to just kill it outright rather than find people who were willing to maintain it, if nothing else.
I'm not sure whether this shows a shortcoming of the collaborative development model or not. It seems like it might be -- although I suppose projects managed by a "benevolent dictator" are also prone to shutting down if the person moves on / dies / whatever; however it seems like the a not insignificant number of projects that are run by teams without a clear leader close due to 'personality conflicts' over time.
On the other hand -- what is it with CD meta-databases and going non-free? Is it just that they seem like tempting revenue sources or what?
"Ladies and gentlemen, my killbot features Lotus Notes and a machine gun. It is the finest available."
on behalf of all of us geeks,
Thanks!
Add to your hostfile:Ugly, but it might work.
Don't fight for your country, if your country does not fight for you.
At the end of proprietary software development, the project ends and the free software community has to either do without or start anew from whatever they've got (which is not the proprietary program's source code and a license to run, inspect, share, and modify at any time for any reason). At the end of a free software project, others can pick up where the former free software hackers left off and continue improving the free software. If the license for the program is a copylefted free software license, the improved software continues to be free.
Let's hope source code for freedb2.org and database dumps from freedb2.org are shared under a free software license so that if freedb2.org dies we're not left with nothing but an increasingly out-of-date freedb.org database and freedb.org software.
Thanks so much for all the work, freedb.org hackers. Your efforts are greatly appreciated.
Digital Citizen
While I believe that free, open source software is very good and should be used more widely, this is an example of where corporate solutions can prevail.
I've used FreeDB for a while now with the CD ripping program I use (Goldwave, highly recommended), and it had its pros and cons.
On the plus side, I could find listings for more foreign/anime CDs than I could using CDDB (a corporate company, used by the likes of WinAmp and WMP, I believe).
On the minus side, there were a few moderately popular to very popular CDs that had no listing. Also, more than a few CDs (including the foreign CDs mentioned) had more than one listing, each with small differences (some with large differences, such as translated song titles, or even just misspelled words), so you had to go through each one to find one that suited you. (One might argue that the choice was good, but in this case it was just annoying.)
The reason that FreeDB stopped is because those in the lead couldn't come to a decision. This would almost never happen in a corporate environment. Any dispute would go up the chain until it hit the CEO or board of directors, where a firm decision one way or another would be made. In the mean time, the product would merely remain unchanged (unless company policy specifies otherwise), so there would be no interruption in service.
Had FreeDB used a similar hierarchy (which they may have had, but it just fell apart), this might have been avoided. The programmers/engineers would dispute something, and the project lead/lead engineer would hear both sides and say "This is this, and that's that."
Certainly, this will be an inconvenience to those who use programs that use FreeDB, but have no idea that the program does.
It gets in the way of good ideas.
Damn... burningserver.com is taken! That'd be a pretty sweet domain name...
By the Power of BitTorrent, the freedb.org database is made available to all.
.torrent file on http://tracker.freedb.org/ - but if it ever becomes unavailable there, you can use a DHT-aware Bittorrent client such as Azureus and get it by using this info hash: 21AF020252FD2E556B683CEB123689733E0BC063
Today, you can get the
I, for one, have allocated a total of 16mbps of bandwith on four hosts to help seed this database. I'm seeing a total swarm performance of around 25mbps, so this should be a fast download for anybody who wants it.
Go ahead: feel the Power of BitTorrent and share this free database!
Share, my friends, share!
What?!? How could this happen? GAY! VERY, VERY GAY!
I hold very few opinions. I hold information based on observation and fact. If you wish to disagree, please use facts.
Joerg on freedb:
For almost two years now Ari and I have supported a developer from Australia, who was working on the next generation of the freedb server, which would have overcome most of our current technological problems and offered text searching. This was the biggest chance for freedb in years. Unfortunately there have been rising tensions in our team about the question, how long we should support a development project, which has not yet been made open source by the developer and which is not yet running on freedb servers. Last weekend the line was crossed by the founder of freedb, who owns the domain, when he took action against that developer without talking to the rest of the team first, while we were still trying to find a solution in everyone's interest.
Well, if I'm reading between the lines correctly:
1) Ari and Joerg support some australian guy developing the "next-gen" freedb for two years
2) Australian guy doesn't want to release it as open/free for freedb (or all three?)
3) Ari and Joerg have either been suckers or part of an attempt at pulling another Gracenote
4) Kaiser won't play ball, it's freedb or no db at all. He finally tires and goes to the source.
5) The play is called, Ari and Joerg leave because the gig is up.
To put it this way, I would not be surprised to see another CD database show up soon, lead by an australian and maybe with a few more anonymous employees. Either that, or they're been really gullible. Never ever trust someone who says they'll open source it "soon". If that is their true intention, they would have no problem being open about it all the way. The only reason not to is when you're pulling a bait-n-switch like here. It seems clear to me that they expected it to be open source ("not yet open source", Joerg), it wasn't ("did not seem to be kept free", Kaiser) and that tore them apart.
Live today, because you never know what tomorrow brings
You jackasses are the core of all music database systems. Just because you don't like each others hair, doesn't mean you put that before the project. Grow up you adolescents.
Wikipedia is busily replicating GraceNote and IMDB, by hand, and not too well. They're using a wiki to do the job of a database. Some music types from Wikipedia should take this database and the data in Wikipedia and make something useful out of it.
Personally, I think that Wikipedia needs something like "Wikipedia Music and Movies", to which all content associated with music, movies, TV, and the people involved in the industry would be moved. More structured than Wikipedia Encyclopedia, Music and Movies would have standard database formats and slots for music and movies, indexed so that you could see all movies by some director or all songs by some musician. Wikipedia can't do that, but IMDB can.
Then Wikipedia needs "Wikipedia Atlas", a map-based system, for all those "State Route 93" entries. Wikipedia isn't spatial, and space is what keeps everything from being in the same place. An atlas system would be able to handle an endless number of "my favorite restaurant" articles. Wikipedia Travel already has something like this.
With that out of the way, Wikipedia would become more like an encyclopedia. Right now, it's drowning under the incoming cruft.
IBM's gonna be pissed.
That is all.
Time for a new business (sic) model. If you want to survive, eat (or die). If you want to be eaten, open source ! Viva la revolution !
serves to reinforce it atempts to
That's the one which was destroyed by Michael Sims and his rampant, uncontrollable ego. You remember Michael? He used to be an 'Editor' here at Slashdot for a while. Before they finally figured out what a tossbag he was and fired him...although they should never have hired him in the first place, and probably did more damage to Slashdot by doing so than anything else.
Also, more than a few CDs (including the foreign CDs mentioned) had more than one listing, each with small differences (some with large differences, such as translated song titles, or even just misspelled words), so you had to go through each one to find one that suited you.(One might argue that the choice was good, but in this case it was just annoying.)
Is offering a choice of original and translated titles more or less annoying than if they had standardised on the language you like less? Do multiple language and subtitle tracks on DVDs annoy you too?
This sounds like the *BSD or XFree86 faggotry.
I want to delete my account but Slashdot doesn't allow it.
Why is this a problem? The freedb server is open source and the database is also available for download from freedb.org.
..The lag it took them to make this post? Last NIGHT I was reading about this. Pfft.
A blob field for album covers would be great too, so programs like Amarok don't have to point to Amazon.com's limited collection.
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
freedb has sucked almost since it's inception. Multiple entries for the same album, hard to do Various Artist albums, lots of misspellings and mistakes, and no way to ""fix" the problems.
I really hope people take this opportunity to check out Musicbrainz, a MUCH nicer alternative. It's (mostly) open source, runs on Linux, Mac and Windows.
Also, it's community moderated like Wikipedia, and it has loads of information about releases, something which was nonexistent on freedb.
I'll check into that real soon now.
And who deals with the copyright issues for the artwork?
would a massively-replicated and -distributed p2p database of song information be a better answer to this need? why put all the eggs in one cranky-developer basket, especially when such a large number of individuals have contributed their typing to building it?
pr0n - keeping monitor glass spotless since 1981.
Reminds me of NSurvey, a FOSS survey program that went commercial. I make it a point now to always download the source code for *ANY* binary download I make - as is yours and my right.
That's also why I am a little surprised that Ubuntu's source code isn't up on their download page, there isn't even a link to it.
I think the point being made was that in a world where someone can be sued and forced to remove software from distribution - either from legal rulings or the threat of litigation forcing a chioce of financial priorities - saying that the source will be released "real soon now" may mean it's never released at all. Obviously, releasing well-formated source code with documentation is better than releasing poorly formated code with no documentation, but both are better than releasing nothing at all.
I mention DVD Decrypter in the subject of the post because it's a well-known (if you're into that kind of thing) DVD ripping software that was taken down from a number of (US-hosted) sites after threat of litigation and, since it was closed-source, no further developement was made. Now, I'm not trying to compare FreeDB to DVD Decrypter, either in terms of legality or morality. Just using DVD Decrypter as an example of software which, had it been open source, could still be under developement but because the source code wasn't being released is now "lost forver." (Of course, in actually, it's not that hard to find a download of the final released version of DVD Decrypter, but it would have been nice if the code was out there for other people to continue improving.)
Again, I'm not trying to compare FreeDB to DVD Decrypter. Just providing an example for the parent's point that you never know how some court ruling or sue-happy lawfirm is going to affect what's out there. I'm not even trying to say FreeDB *should* post every line of code currently written - I can understand why the author wouldn't want that. At the same time, I can understand why the GP has an attitude of "all-or-nothing" in terms of calling something 'open source.'
-Trillian
Quote from one of the freedb authors:
As far as I can see, freedb2 is not distributing the database dump, which was licensed under the GPL. I do not like to see comments on Slashdot promoting a project that violates the GPL. freedb2 has used the data provided under the GPL by freedb and is not giving anything back (yet?).
To be clear about why freedb2 violates the GPL, I will point out that the GPL requires every distributor to make the source code (plain text database dump) available "from the same place" as the binaries (the database used by freedb2). So simply adding references to the original freedb mirros would not be sufficient in this case, especially because these CD databases evolve over time so it is likely that freedb and freedb2 could contain different data. For reference, see this section of the GPL FAQ.
I have contributed a large number of CDs to the freedb database (including corrections to existing entries). I have done it because I knew that the database was licensed under the GPL and could not be taken away from the users (note that I am talking about the database, not the programs used for accessing it). I was using the old XMCD before the database was taken over by what became Gracenote. I was very happy to see freedb emerging, promoting freedom as one of its core values. That's why I contributed my CDs to this free database.
Unless the freedb2 developer (who seems to be responsible for the problems with freedb) complies with the GPL and offers a complete dump of the database, I will discourage anybody from using freedb2.
I understand that whenever a free resource dies, it is a time of lamentation. However, what I do not understand is why this is such a big deal. Are people really that lazy that they cannot be bothered to type in song titles when ripping CDs? I've ripped hundreds and have found most of freedb's responses to be wrong (using CDex). Granted, I own a lot of non-English CDs, but even when I rip English CDs, I prefer to input my own metainformation in. It's just one more minute of time, guys!
would you mind sending SPAM to this email address: runbeth@yahoo.com
I forgot to mention it in the OP, but I believe a sufficiently small copy (say 200x200) would constitute fair use while still being recognizable.
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
Maybe, with this change, and other changes such as individual track downloads and other media mp3 players, DVD-Audio, etc., it's time for something better than a CD-Audio database? Aren't all the tools available now to recognise the actual songs' "fingerprints"? Couldn't a more flexible database, with lyrics etc. be built with that technology?
Who says some developers can't get together and just start "www.reallyfreedb.org?" We can download July version of the dataase, host the software, and continue on as if nothing happened. Anyone interested?
The essential part about all this is the collaboratively filtered and collected data, right? And that is out in the wild and still available as a package, correct? ...Mmmmh... Coming to think of it ... does anyone know the mean load of late freedb?
Copy, Fork, Install, Build a cool website, have yourself a fresh OSS project. No big deal.
Ideal for anyone who needs to make themselves a name as DB admin / web services expert.
Anyway, a handfull of weeks and we'll have an alternative and freedb will be history (no pun intened).
My 2 cents.
We suffer more in our imagination than in reality. - Seneca
Hmm I looked at the URLs you provided but all I could find were some CREATE TABLE statements and some scripts to do conversion between different character encodings.
As far as I understand we're talking about a full FreeDB server here, something that is able to answer requests and accept new submissions. I haven't seen any such code!
There is no need to comment your source code in fancy HTML pages. We can read pure source. Just put up a tarball with the source online and we'll see what you did in the last two years.
Need a Wiki? Check out DokuWiki
I don't understand. You claim that you'll release the source code to the public, yet when the issue came to a head and the two main freedb devs essentially walked away from years of (free) work, you just sat by and watched? We could have avoided all of this mess if you'd even just given them the code and said, "Here, this is the source, this is the license, could you please hold off on distributing it until after I've documented it?" Then they'd at least be able to open it up to the public if you were to get hit by a bus or something in the interim.
/. with promises you should have kept a year ago. Why should any of us trust you, when you could have prevented all of this?
But you didn't do that. And now you're shilling your code on
I found it's pretty common for CD drives to not return bit-identical results when ripping the exact same CD. I've got several drives, and they will not all result in matching MD5 sum output. I forget the details, but one drive for example would add a few extra 0 bytes onto the front of the CD. And that's without taking into account the possibility of scratches or differences between different copies of the same album. It's a nice idea, keeping the MD5 sum, but would probably just result in huge numbers of duplicate entries.
That very page you linked from GNU also says this:
The CD info is factual public-domain data, and anyone's added comments/notes are copyrighted to their authors. The freedb software has translated it into another form, which doesn't give them any ownership rights, and ergo they can't impose GPL on it.
Database dumps are NOT "source code" no matter what the freedb guys say. Calling a tail a leg doesn't make it one.
As stated by the subject, the bosses are just as human as the other team members. So, while it can be hoped that being capable of diplomacy, tact and some ego control helps one to become a boss, it does not guarantee that they can't get stubborn and irrational as well every now and then.
Regarding the closed-source projects, I'd assume that most of the ones that were damaged sufficiently by personnel conflicts would do so inside the walls of a company, without much publicity. After all, not all projects get hyped much until they have progressed moderately far, whether they are open or closed source.
Everyone who makes generalizations should be shot.
Care to tell how I'm supposed to be a thief, while I'm listening for a CD chosen from my collection of a couple of hundred or so audio CDs I've bought since 1991 and player application uses the database to display track/artist information?
(Sure, I could just look at the track number and compare it to the listing contained at the back of the CD. But why not use the technology, when it's available.)
Everyone who makes generalizations should be shot.
well, it's just blue-sky thinking - an example of one possible feature that could have been useful. perhaps a straightforward checksum of tracks, with fuzzy best-matching searches would do the trick. maybe not. Trogre suggests in this thread that a very small cover graphic would be good.
Of course, I've not really looked into it - there may be technical limitations to the CDDb format the freedb has to adhere to...
--
Having looked at what constitutes freedb I can honestly say there is plenty of opportunity for improvement.
Staying compatible with the current protocol isn't difficult, and moving it forward to something more recent would not be difficult. It is an exceptionally easy and straightforward process.
The issue I would have with the cover-art is copyright issues. To resolve that would require licensing arrangements with the music publishers. Not fun, and not going to happen for a free database.
I seriously considered what it would take to run a freedb server in the last few days.
freedb consists of hundreds of thousands of files, it isn't a database per say. (the rock folder contains 574,664 files each only a couple K in size. )
In the end an uncompressed archive is 3,513,815,040 bytes. 3.5Gigs. I don't have easy access to that kind of space on a server on the internet. (ok, I might, but that would require negotiating with my boss. Don't think they are up for it. No clue what the actual bandwidth hit is for freedb)