Picard 2.7.3 fixes a packaging regression for macOS, which caused the app to be reported as damaged when trying to launch it. This affected especially users of macOS 10.13, see PICARD-2395 for details.
There are no other changes in this release. If you are running Picard on a different operating system or if you are using macOS but could start Picard without an error message than you don’t need to upgrade.
The Picard team is happy to announce that the final version 2.7 of MusicBrainz Picard is now available for download. MusicBrainz Picard is the official tag editor for the MusicBrainz database and helps you get your music collection sorted and cleaned up with the latest data from MusicBrainz.
This release brings many changes, including a completely new naming script editor, scripting improvements and AcousticBrainz submission. See below for the highlights.
The Picard team is happy to announce that Picard 2.7 Beta 1 is now available. This is a pre-release we put out for wider testing and to gather feedback on the changes before the final 2.7 release. There are many new features in this release, which might or might not work for you as expected. If you prefer stability we recommend you use the stable version Picard 2.6.4 which we released yesterday.
Thanks a lot to everybody who contributed to this release with code, translations, bug reports and general feedback. This release contains code contributions by Bob Swift, Gabriel Ferreira, Laurent Monin, Philipp Wolfer and Louis Sautier.
Picard 2.7 Beta 1 can be downloaded from Picard website Downloads section.
Linux users might want to install the beta version using Snap. If your Linux distribution supports Snap you can install Picard from the beta channel using:
snap install --beta picard
This release brings a lot of new features, enhancements and bugfixes. Some of the highlights in this beta include:
It is now possible to have more than one naming script and to switch between them as needed. A new script editor dialog allows you to edit the different scripts while tagging.
Scripts can be exported to and imported from YAML files.
The “Submit cluster as release” functionality, which was previously available as a plugin, is now directly available in Picard. This also fixes some issues the plugin had. While the plugin is still available for now and can be used independently it will be considered deprecated once Picard 2.7 stable version has been released.
Picard now supports analyzing your music files and submitting the audio characteristics to AcousticBrainz. Previously this was only possible with separate tools provided by the AcousticBrainz project. This functionality requires a separate Essentia music extractor tool. The macOS and Windows packages come with this tool bundled. For Linux this tool is available from the AcousticBrainz download page. For details on this feature see the documentation.
The scripting now allows explicitly entering any Unicode character with the escape sequence \uFFFF, where FFFF is the Unicode code point. E.g. \uff0f would enter a full-width slash. This makes it easier to handle characters that are either not easily accessible on common keyboards or are invisible control characters. If you hover your mouse over such a sequence a tooltip will show details about the corresponding character.
[PICARD-2248] – Lazily initialize the file browser on first display
[PICARD-2251] – Add ability to import/export tagging scripts
[PICARD-2263] – Performers without role do not get saved to TMCL (TIPL respectively) frames
[PICARD-2266] – Add already mapped tags gapless, podcast, podcasturl, show and showsort to list of known tags
[PICARD-2271] – Allow removing obsolete option settings from configuration INI file
[PICARD-2273] – Set acoustid_id tag also if AcoustIDs were found, but no recordings are attached
[PICARD-2278] – Show the path and name of the configuration currently used
[PICARD-2288] – Add variable %_workcomment% for the work disambiguation comment
On macOS if you have the script editor dialog open and then open the preferences the script editor dialog will be behind the preference dialog and will not be accessible until the preferences get closed again.
On macOS setting the user interface color theme to “Default” does not automatically use the dark mode if dark mode is enabled in the system. See the ticket PICARD-2290. As a workaround you can force the dark mode in Picard’s preferences.
The Linux Snap package does not yet contain the Essentia music extractor binary, which is required for the AcousticBrainz submission. We plan to add this to the package in a future update.
The easiest way to help us getting a great Picard 2.7 release is using and testing this beta release. Please report bugs on the Picard issue tracker and provide feedback in the community forums.
Please also help translate Picard. There have been many changes to the user interface existing translations need to be updated for the final 2.7 release. Translating is easy and can be done online: Head over to MusicBrainz’s translation page on Transifex and click on “Help Translate MusicBrainz”. Once you have registered an account on Transifex you can start translating. For Picard the primary resource to translate is “picard“, but there is also the “picard_appstream” resource, which is used for providing descriptions for various Linux software-center applications, and “picard_installer”, which contains the translations for Picard’s Windows installer.
If you are a software developer you are very welcomed to provide fixes and features. Picard is free software and the source code is available on GitHub. See Developing on the Picard website to get started.
Thanks a lot to everyone who gave feedback and reported issues.
[PICARD-2199] – Saving ID3 ratings fails, if rating e-mail contains non latin-1 characters
[PICARD-2200] – Copy and pasting function names from inline scripting docs can copy Unicode left-to-right mark
[PICARD-2230] – Picard fails to start on Windows if the hostname contains non-ASCII characters and browser integration is enabled
[PICARD-2269] – “TypeError: arguments did not match any overloaded call” with Python 3.10
[PICARD-2274] – Picard 2.6.3 crashes when track is removed or moved during lookup
On Windows if the computer name contains non-ASCII characters the browser integration will not work. The only known workaround is to rename the computer so the name consists only of ASCII characters. While Picard 2.6.3 would crash in such a situation when starting, we fixed this crash in Picard 2.6.4. But the root cause is actually a bug in Python 3, which we will solve by an upgrade to Python 3.8.10 with the upcoming release of Picard 2.7. See PICARD-2230 for details.
Copy and pasting code from the built-in script documentation Window when using Picard with Arabic or Hebrew language can cause invisible Unicode left-to-right mark control characters to be copied. This can have unintended side effects in your script. This will be properly handled with Picard 2.7, where control characters will be made visible in the script editor. For details see PICARD-2200 and PICARD-2204.
A beta release for the upcoming Picard 2.7 will be available soon.
Picard 2.6.3 is the third maintenance release for the recently release Picard 2.6. It contains a couple of bug fixes, most notably it fixes a bug where changes to some options did not get applied until a restart of Picard. Users of Picard 2.6 are highly recommended to update.
Picard 2.6.2 is a maintenance release for the recently release Picard 2.6. It fixes a bug where a plugin update could fail because Picard would use the old version from the network cache.
We also reverted a change from Picard 2.6.1, where if a file had no title or track number in metadata and Picard guesses this information from the file name, the title and track number would show up only as new metadata. This turned out to break people’s workflow who relied on this data for comparison with the actual new metadata loaded from MusicBrainz. For those of you who do not want Picard to automatically guess these tags from file names we will add an option in Picard 2.7 to completely disable this behavior.
The Picard team is happy to announce that Picard 2.6 is now available. This release fixes issues where the user interface could freeze and contains many new features, bugfixes and improvements.
Thanks a lot to everybody who contributed to this release with code, translations, bug reports and general feedback.
Picard 2.6 can be downloaded from the Downloads section on the Picard website.
For macOS users there are now two separate builds available. If you are using macOS Mojave 10.14 or later, including macOS 11.0 Big Sure, please use the download for macOS 10.14+. If you are still on macOS Sierra 10.12 or macOS High Sierra 10.13 you should use the download for 10.12+ instead.
Only the 10.14+ builds support the macOS dark mode. This build also uses newer versions of Qt5 and Python and is hence recommended, but won’t run on macOS before 10.14.
Users who have installed Picard on Windows 10 from the Windows Store will receive the update automatically once it has been approved by Microsoft.
Since the release of Picard 2 we had some reports of some users experiencing Picard’s UI completely locking up. This mostly happened when adding or removing tags or toggling the “Show changes first” in the metadata view. As this was a timing issue not all users on all systems were affected by this issue the same.
The root cause for this has been now identified and Picard 2.6 comes with a fix to prevent those freezes.
Dark mode switching on Windows and macOS
On both macOS and Windows it is now possible to switch to dark or light UI independent of the system setting. By default Picard will follow your system settings.
This is also the first stable release which supports the dark mode on macOS Mojave 10.14 and later in the official app packages. Previously this was only available when running Picard from source or installing via PyPi. Please note that you need to use the Picard app build for macOS 10.14 or later for this feature to work (see above).
Reworked cover art options
The cover art options have been rearranged to be easier to understand their meaning. Some options that previously had been shown in the Cover Art Archive options but actually affected all cover art sources have been moved to the general cover art options.
Please note that there was no change in functionality, all the options are still available and behave as before.
Support for track-level original release date
The MusicBrainz server since recently supports returning a first release date per recording. This information is based on the earliest release on which this recording appears on according to the MusicBrainz database.
Picard makes this date available in the variable %_recording_firstreleasedate%. If you want to have this date set in your files for the original release date you can use the following script:
Please note that this means that each track on a release can have a separate date. In this case you should not use %originaldate% as part of a folder name in your file naming script.
By default %originaldate% will still be filled with the first release date of the release group. To be more flexible this date is also now available in a variables %_releasegroup_firstreleasedate%.
Improved script editor
The auto completion in the script editor has been improved to not popup unnecessarily and to provide better suggestions. It also is now possible to trigger the autocompletion anytime by pressing Ctrl+Space.
Support WebP images for cover art
Picard now supports cover art in WebP format. Please note that support for this depends on your playback software. Also WebP images will not be embedded into MP4 files as those do not support this format.
There are many more bugfixes and improvements since the last stable release 2.5.6, such as support for a director tag (for videos), the release annotation being available as a variable %_releaseannotation% and fixes for cover art drag and drop from browsers
For a complete list of changes since the last stable release please see the full changelog below.
Notes for package maintainers
If you are maintaining packages of Picard for a Linux distribution or another OS please note the following changes:
The minimum supported Python version is now Python 3.6
Qt 5.10 or later and PyQt5 5.10 or later are now required
The newer Qt5 versions are necessary in order to work around the dead lock issues (see above). If possible it is recommended that you use PyQt5 5.15.3 or later, as those versions actually fix the root cause for the deadlock. But Picard applies a workaround that should also prevent this in earlier versions. Please see the discussion on PICARD-2088 for details.
This release contains code contributions by Philipp Wolfer, Laurent Monin, Gabriel Ferreira, Sophist, Bob Swift, RomFouq and petitminion.
Many thanks also to all the translators and everyone who tested the beta releases and provided feedback on the community forums, IRC and the issue tracker.
This is the complete list of changes since Picard 2.5.6:
PICARD-1528 – “Search for similar albums” causes crashes if the selection includes clusters and files