Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[shAf]

I stumbled upon this original (but locked for some reason) thread while looking to find why I'm also seeing the same problem.  YADB's hit rate for re-RIP'ing many of my library is about 4/5.  A previous post stated:

I use EAC to rip (I understand that MC performs secure rips, but I like EAC) and it uses Gracenote CDDB.  I rarely stump it.  Then I have MC's auot-import keep an eye on my rip folder.  

I rip to FLAC and mp3 with EAC.

I've resorted to something similar ... i.e., to use EAC for accessing freeDB, then using EAC to export the data to 'CDplayer.ini', ... and then to use MC14 to import from the same.

Regarding YADB being MC user supported, I have to wonder why JRiver tried to re-invent the wheel, when freeDB is supported by a larger user base and its hit rate is near 100%(??)  Is there a technical reason?

My $0.02  

[John Gateley]

Basically, the quality of FreeDB's data. FreeDB has a lot of data, but a lot of it is incorrect, garbled, etc.
A 100% hit rate isn't impressive, if the results returned are wrong. YADB has mechanisms that constantly improve the data based on user submissions.

j

[raym]

FreeDB has a lot of data, but a lot of it is incorrect, garbled, etc.

That's never been my experience but regardless, surely it's resonable to suggest that MC could resort to an alternate online db when jadb comes back with nothing?

[bunglemebaby]

That's never been my experience but regardless, surely it's resonable to suggest that MC could resort to an alternate online db when jadb comes back with nothing?

That's an interesting thought, but I wonder if there would be legal issues with extracting the data from one database (free.db) and then importing it into another (YADB), since I believe MC uses user data in this way to fill YADB with data. I'm certainly not the expert, but I'd guess it's something along those lines.

-JB