This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| Compact Disc Database | |
|---|---|
| Name | Compact Disc Database |
| Developer | Various volunteer projects |
| Released | 1990s |
| Latest release version | varies by client and mirror |
| Programming language | C, C++, Perl, Python, Java, PHP |
| Operating system | Cross-platform |
| License | Public domain / various open licenses |
Compact Disc Database The Compact Disc Database (CDDB) originated as a community-maintained catalog for identifying optical audio media by track lengths and disc length. It grew through contributions from volunteer maintainers, independent developers, and mirror sites, intersecting with projects and institutions in the digital music ecosystem.
CDDB emerged in the early 1990s amid developments in consumer electronics such as the Sony CDP-101, the rise of the X Window System on Unix workstations, and the proliferation of audio ripping tools. Developers involved with projects like Freedb and the MusicBrainz initiative influenced its evolution. Legal and commercial attention came from companies including Gracenote, which later acquired database assets and engaged in disputes with open projects and organizations like Electronic Frontier Foundation. Academic and archival communities at institutions such as the Library of Congress monitored metadata practices alongside standards bodies including the Internet Engineering Task Force and cataloging efforts at libraries using systems tied to the Online Computer Library Center. The landscape included interactions with commercial players like RealNetworks, Rhapsody, and hardware makers such as Pioneer Corporation and Panasonic Corporation.
The database’s primary purpose was to map disc signature heuristics to human-readable titles, enabling software to display album and track metadata during playback. Its scope covered released commercial audio discs from labels such as Sony Music Entertainment, Universal Music Group, Warner Music Group, and independent imprints like Sub Pop and Matador Records. It intersected with cataloging projects from archives like the British Library and discographies maintained by publishers including Billboard and Rolling Stone. Use cases included client applications on platforms by Microsoft and Apple Inc., integration with players such as Winamp and iTunes, and metadata workflows employed by broadcasters like the BBC.
Entries relied on algorithmic disc identifiers computed from track durations and counts derived from Red Book (audio CD standard) timings. The schema typically contained fields for album artist, album title, track titles, track counts, total length, and CDDB/gracenote identifiers; implementations mapped to metadata standards like ID3 tags, Dublin Core, and cataloguing rules practiced by the Library of Congress and the Bibliothèque nationale de France. Crosswalks were developed to align with authority control systems used by institutions such as VIAF and the International Standard Recording Code registry managed alongside registrars like IFPI. The model supported multiple release versions, bonus tracks, and compilation attributions linked to labels such as EMI and distributors like Universal Music Distribution.
Clients queried central servers or mirrors using simple TCP-based proprietary protocols, HTTP-based APIs, or legacy protocols adapted by services like Gracenote and community mirrors like freedb.org. Authentication and licensing shifts involved corporations such as Nokia and legal entities like Compact Disc Digital Audio Committee stakeholders. Networked access patterns paralleled developments in web standards from the World Wide Web Consortium and revealed interoperability challenges with formats endorsed by groups like Music Ontology and schema specifications influenced by the Internet Archive.
Various media players and ripping tools integrated CD lookup: clients included Exact Audio Copy, CDex, Winamp, foobar2000, iTunes, Rhythmbox, and Amarok. Desktop environments such as GNOME and KDE incorporated services for automatic metadata retrieval, while server-side systems in broadcast automation from vendors like Dalet leveraged lookups. Integration extended to database-driven music libraries maintained with tools linked to MySQL, PostgreSQL, and scripting ecosystems around Perl and Python.
Governance varied: community-run mirrors and volunteer maintainers organized around open projects including freedb and later collaborative efforts tied to MusicBrainz and archival initiatives at universities such as Stanford University and Harvard University. Commercial stewardship by companies like Gracenote introduced proprietary policies and licensing terms impacting contributors and consumers. Contributions came from individual volunteers, record label staff, metadata vendors, and archivists associated with institutions like the Smithsonian Institution and national libraries. Copyright and licensing debates involved stakeholders such as RIAA and advocacy groups like Electronic Frontier Foundation.
Reception was mixed: consumers and developers praised convenience enabling integration across players like Winamp and iTunes, while librarians and archivists debated reliability compared to authority-controlled catalogues such as those curated by the Library of Congress and the British Library. Commercialization by entities like Gracenote prompted forks and responses from open projects including MusicBrainz and freedb, influencing subsequent metadata ecosystems used by streaming services like Spotify and Apple Music. The project’s legacy persists in how digital audio metadata workflows reference standards and initiatives at organizations such as IFPI, RIAA, and the Internet Archive.
Category:Digital music