Install musicbrainz-picard with Homebrew Cask

Project links

• Homepage
• Package manager page

Commands and aliases

No executable aliases were found in the local package database.

Project history

MusicBrainz states that Picard's predecessor dates to 2003 and development of its current form began in 2007. An earlier Picard generation had already become the official MusicBrainz tagger in 2006.

The project developed into a cross-platform Python application backed by the community-maintained MusicBrainz database. Its source is maintained publicly under GPL-2.0-or-later, now in the MetaBrainz GitHub organization.

Adoption history

Picard became the official MusicBrainz tagger in 2006 as MusicBrainz adopted PUID acoustic fingerprints. It remains the project's supported cross-platform desktop tagger for Linux, macOS, and Windows.

Its combination of MusicBrainz metadata, AcoustID fingerprinting, CD lookup, scripting, cover art, and plugins has made it a common tool for cleaning and normalizing large personal music libraries.

How it is used

Users load audio files, cluster them into albums, look up or scan recordings, compare proposed MusicBrainz metadata, and save approved tags back to the files. AcoustID fingerprints can identify files with missing or unreliable metadata.

Advanced users customize filename and tag output with scripts, install plugins, retrieve cover art, look up CDs, and submit disc IDs to MusicBrainz.

Why package nerds care

Picard is a long-lived, GPL-licensed desktop application with releases across major operating systems and packaging ecosystems. Package maintainers must account for its Python and Qt stack, audio-format support, optional fingerprinting tools, plugins, and platform-specific integration.

For metadata enthusiasts, Picard is important because it writes stable MusicBrainz identifiers and applies an album-oriented matching model rather than merely editing individual tag fields.

Timeline

• 2003: Picard's predecessor was in use.
• 2006: Picard became the official MusicBrainz tagger with PUID support.
• 2007: Development of Picard in its current form began.
• 2012: Picard 1.0 was published.
• 2026: The 3.0 documentation generation was published.

Related projects

• MusicBrainz supplies the community-maintained music metadata used by Picard.
• AcoustID provides the acoustic-fingerprint matching used to identify recordings.
• Chromaprint's fpcalc utility is used to calculate compatible fingerprints.
• Official and third-party Picard plugins extend tagging, scripting, and metadata workflows.

Sources

• https://github.com/metabrainz/picard
• https://musicbrainz.org/doc/Development/Introduction
• https://musicbrainz.org/history
• https://picard-docs.musicbrainz.org/en/latest/