If there are fewer than 5 tracks, the release will NOT be auto-inserted.
Processing stops at the first rule to "match": The following rules are applied in order. These were the then-current import criteria before the automatic imports were disabled. Additionally, the MusicBrainz search page still retains special support for running queries that include or exclude the FreeDB editor. For example, the concept of adding disc IDs to existing releases was kept, although since the addition of disc IDs to a release happens automatically, without voting, the FreeDB editor is not used for these additions. Nonetheless, even though the automatic addition of releases was disabled, certain elements of the implementation still remain in MusicBrainz. This feature was eventually disabled after some mailing list discussion because the poor quality of raw freeDB data and the frequency of duplicated entries were felt to outweigh the benefits of additional data for MusicBrainz. Prior to the server update, releases that met certain criteria were automatically imported from FreeDB by the MusicBrainz FreeDB bot as a method of growing the database when the MusicBrainz project was just starting out. Read more in this awesome article ( archived) FreeDB MusicBrainz user These Enhanced CD that were added by the FreeDB automoderator, have their last audio track with an exceeding 2:32 length. If the last track of a CD is a data track, the 11400 sector (152 seconds, 2:32) gap between the last audio track and this data track is included in the last audio track length. This affects only the releases imported from FreeDB Enhanced CD entries. Sometimes mistakenly referred to as the FreeDB 2:30 bug. last audio track before data track is 2:32 too long When MusicBrainz used to create disc ID out of FreeDB entries, last track length had only 1 chance out of 75 to be correct (there are 75 frames per second). They only contain the total length of the CD in seconds. This affects only the releases imported from FreeDB, with a computed disc ID.įreeDB entries don't contain the leadout frame. Known issues Disc ID computed last track length is only an approximation Also, it is good practice to provide proof of your release in the edit notes – FreeDB is not considered as a proof, as their submissions process is not monitored. You must carefully examine the FreeDB data since it needs to be corrected in most cases to conform with the MusicBrainz style guidelines. Eventually, it is hoped that MusicBrainz will take over from FreeDB as the preferred open-source free-database way to look up CDs, especially since Gracenote has since developed (and is forcing customers to switch to) CDDB2, a proprietary replacement for the original CDDB protocol. MusicBrainz has many features included to import data from FreeDB. Status: The following details a deprecated feature and is being retained only for historic value. GnuDB, created in 2006 to make sure CDDB remains alive and free, has been the natural successor. One of the advantages of this protocol is that it is practically the same as the original CDDB protocol, and could thus be used as a drop-in replacement for CDDB when Gracenote took it over.Īs a result, FreeDB has taken over as the de-facto standard CD recognition database for open source music software. There is a web interface to FreeDB but most access (lookups, submissions) takes place via the FreeDB protocol (which may be embedded in HTTP, but is not really accessible via a browser).
The quality of the data is not always the best, and there is a lot of duplication in the FreeDB database. Technologically, it has remained fairly static since then, but it has amassed a very large number of releases. It was formed in response to the actions of Escient, which through its subsidiary, Gracenote, bought the rights to CDDB and restricted access to the data.įreeDB took the last available snapshot of data, and created their own server and database.
3.1.1 Disc ID computed last track length is only an approximation.