MusicBrainz: An open music encyclopedia

Original Article ↗ Hacker News Discussion ↗

Reposting and HN Meta

  • Some question why this URL is “news”; others note HN explicitly allows reposts after ~a year and welcomes historical material.
  • Flagging suggests fatigue with repeated submissions, even if permitted.

Use Cases and User Experience

  • Many praise MusicBrainz plus Picard as “essential” for organizing large, often eclectic or international libraries; especially strong for classical.
  • Users highlight global coverage vs region-locked databases, though very obscure or Napster-era material can still be missing.
  • Some report catastrophic library damage from early-2000s or overly aggressive bulk tagging; others emphasize this was user error (running mass-retag without review) and advise album-by-album checks and backups/snapshots.
  • One contributor had a negative experience with broken site JavaScript and hostile feedback on edits, leading them to stop participating.

Companion Tools and Ecosystem

  • Picard is widely recommended; also used by third‑party tools (players, rippers).
  • Alternative/adjacent tools mentioned: beets, mp3tag, puddletag, foobar2000, Funkwhale, Navidrome, Soulseek clients, and self‑hosted stacks (Funkwhale + Snapcast/Mopidy/Iris, FLAC + Plex).
  • ListenBrainz is highlighted as an open scrobbling alternative; some Linux users integrate via generic MPRIS scrobblers.

Data Quality, Style, and Localization

  • Strong editing tools and detailed support for multiple pressings/releases are praised, but contributors note:
    • Mis-matches and incomplete coverage, especially for Asia-Pacific pressings.
    • Occasional inconsistent or odd metadata (instrument classification, spelling variants, place names).
  • Debate around style rules:
    • Tension between correcting spelling/typography (“a cappella”, curly apostrophes, “remix”) vs preserving exact artist usage.
    • Japanese entries more often match original printed text.
    • Some want multi-language/alias-aware tags and user-selectable localization.

Licensing, Openness, and Longevity

  • MusicBrainz is contrasted favorably with proprietary databases (CDDB→Gracenote, TMDB/TVDB under Roku, IMDb), where community data became closed or restricted.
  • MetaBrainz Foundation and public data dumps are seen as safeguards; some say this model is key to avoiding “kidnapping” of user-contributed data.
  • Discogs data dumps are also mentioned, with curiosity about differing terms of use.

Technical Integrations and Projects

  • Examples of deeper integrations: AcoustID/Chromaprint for audio fingerprinting, a Zig reimplementation, a GraphQL wrapper (graphbrainz), and a Typesense-based search-as-you-type demo with tens of millions of tracks.
  • MPRIS is cited as a good open desktop integration standard, though broader FOSS desktop fragmentation and awkward “modern” APIs are lamented.

UI, Community, and Contributions

  • Many enjoy contributing releases (including niche genres, doujin, local bands, vaporwave samples) and receiving change notifications years later.
  • The site’s look is described as “2000s internet”; some ask for modernization. A “beta” server exists, but it’s unclear if that includes a new UI.
  • Annual participation in Google Summer of Code is noted as a structured way to contribute code.

Streaming vs Local Libraries

  • Several reminisce about meticulously curated local libraries later disrupted or partially overwritten by services like iTunes Match/Apple Music.
  • Some have since moved fully to streaming (often Spotify), while others use MusicBrainz-powered setups to maintain high-quality, self-hosted collections alongside or instead of streaming.