On 12/7/07, cliveb <[EMAIL PROTECTED]> wrote: > > snarlydwarf;247447 Wrote: > > CD's can vary and even a single release in various countries can have > > different TOC's, which leads to different disc ID's. If the -exact- > > disc ID is not in the database, it won't be found. > This wasn't the case in the past. Has the matching strategy changed > recently? The matching used to use "fuzzy" techniques based on the > number and length of tracks on the disc, with some leeway included. > This is why sometimes you could load in a CD and have freedb find > completely the wrong disc. I've even seen a few cases where a CDR > transfer from an LP was loaded, and freedb successfully found the > equivalent commercial CD release - and since I made those CDRs I know > for a fact that they have no disc IDs.
This is a consequence of using that specific MusicBrainz-to-freedb gateway ( http://freedb.musicbrainz.org/~cddb/cddb.cgi ) that was being discussed in that post. Since it's pulling the data not from the standard freedb but from the MusicBrainz db, it requires that a Disc ID that matches the one you're trying to rip be present in the MB database. If an exact match for your CD isn't there, this gateway won't return the track info. I should mention, though, that MusicBrainz's guidelines prohibit adding DiscIDs for home-burned CDs, so in the case of a CD transfer from LP, you probably wouldn't want to use the MusicBrainz-to-freedb gateway for those discs. -Steve _______________________________________________ ripping mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/ripping
