Picard 2.9.1 released

Picard 2.9.1 is a maintenance release for the recently released Picard 2.9 with fixes for reported issues and updated translations.
This release contains important fixes for a potential data loss on Windows and several crashes. Windows users are highly recommended to upgrade.
Please see below for details.

The latest release is available for download on the Picard download page.

The detailed changes for this maintenance release are below. For an overview of the new features since Picard 2.8 please see our detailed release announcement for Picard 2.9.

Thanks a lot to everyone who gave feedback and reported issues.

Important fixes

Windows: Unexpected file deletion on drag-and-drop

Due to a bug in Picard’s handling of drag-and-drop operations files being dropped into the Picard window while holding the Shift key would be considered “moved” by Windows and deleted from disk.

This issue was introduced in Picard 0.13 released in 2011 and is present in all subsequent releases up to 2.9.0. To our knowledge this issue affects only the Windows operating system. See PICARD-2696 for details.

Windows: Permanent high CPU usage

The Windows implementation for handling the single instance mode caused constant CPU usage. With the revised implementation the CPU usage should be near zero again if Picard is idling. See PICARD-2698 for details.

Windows: Crash on startup after upgrade

Several Windows users reported Picard crashing at start after they upgraded their Picard 2.8 installation to Picard 2.9 using the Windows installer.

In general it is required to uninstall the previous Picard version completely and not have Picard running in the background while installing or uninstalling. The installer was supposed to perform the uninstall and also check for already running Picard instances. Unfortunately both of those checks had issues and could fail. The installer has now been fixed. For details see PICARD-2692 and the related tickets PICARD-2693 and PICARD-2186.

All platforms: Files are not getting loaded on systems with 2 or less CPUs

The new single instance mode requires additional threads for the communication between separate started Picard instances. On systems with only one or two CPU cores this resulted in no threads being available to process file loading or saving. Picard doesn’t ensure there’s at least one thread available for processing those tasks. See PICARD-2710 for details.

Changelog

Bugfixes

• [PICARD-2186] – Windows installer fails to detect already running instance
• [PICARD-2688] – Windows: Portable version crashes when launched with “-h”
• [PICARD-2692] – Windows: Crash on startup after upgrade from 2.8 to 2.9
• [PICARD-2693] – Windows installer allows canceling the uninstaller
• [PICARD-2694] – Crash when re-opening options after closing without the closing scripting documentation dialog
• [PICARD-2695] – Crash in script editor when showing tooltips for some Unicode character codes
• [PICARD-2696] – Windows: Shift dragging files into Picard deletes the files on the filesystem
• [PICARD-2697] – Options “Restore Defaults” does not restore all defaults
• [PICARD-2698] – Windows: Permanent high CPU usage
• [PICARD-2710] – Files are not getting loaded on systems with 2 or less CPUs
• [PICARD-2713] – Stand alone instance mode does not work
• [PICARD-2714] – Windows: Portable installs should run as separate instances
• [PICARD-2718] – File selector for ripping log files does not show *.log files with the “All supported log files” filter

New Features

• [PICARD-1815] – Notification on plugin updates available
• [PICARD-2705] – Provide the new audio director relationship as tag

Improvements

• [PICARD-2691] – Provide code signed source archives

Get in touch

Please use the MetaBrainz community forums and the ticket system to give feedback, suggest new features or report bugs.