Picard 3.0
MusicBrainz Picard 3.0 is released, featuring a migration to Qt6, a completely overhauled plugin system, native Apple Silicon support, and built-in synchronized lyrics.
summary is enough The release post efficiently outlines major architectural upgrades and features, making a full read unnecessary unless you actively maintain plugins.
summary
MusicBrainz Picard 3.0 arrives after three years of development, modernizing the official music tagger with a migration to Qt6 for improved dark mode and scaling. It introduces a safer, Git-backed plugin architecture, native Apple Silicon builds, and new audio processing options including cover art filters and synchronized lyrics. Breaking changes drop support for older operating systems such as Windows 7/8 and macOS versions prior to Ventura. Users should note that legacy v2 plugins require migration to the new system.
key points
- Migrated to Qt6 and PyQt6, dropping support for Windows versions prior to 10 and macOS versions prior to 13.
- Introduces a revamped plugin system featuring MANIFEST.toml metadata, centralized registry updates, trust levels, and a new command-line tool.
- Adds native support for synchronized lyrics in LRC format and automated cover art processing filters.
- Includes session saving, option profile export/import, and native Apple Silicon builds.
who should read it
Desktop music collectors and archivists managing large local audio libraries.
discussion positive
consensus
Commenters express nostalgia and praise for the long-standing project, though many note that breaking plugin changes leave some legacy extensions temporarily unavailable.
pushback
Some argue that a manual GUI tagger workflow is outdated compared to automated background daemons or alternative tools like beets.
I love MusicBrainz for everything they did but I don't think using a tagger as a separate program you have to open and point to a file is good UX, even if the tag lookup is fully automated.
It should be a daemon that auto tags all new files in the background and only prompts you when there's a problem. And if it finds a new song with metadata that's not in the database you get the option to upload it. Even better if it scrapes CDs and streaming services. Maybe I'll build it one day.
It provides strong critical feedback on tagger UX, arguing for automated background processing over manual file-pointing workflows.
Generated by an LLM from the article and thread. Check the sources before relying on it.