Picard 1.0 released

Lukáš Lalinský announced the long-awaited release of Picard 1.0 today:

It took us a long time to get here, but I’m very happy to announce the release of Picard 1.0!

This version includes a new UI for viewing tags, some options have been rearranged and a number of bugs fixed. The file naming formats for single and various artist releases have been merged. If you were using a different format for various artist releases, Picard will upgrade the format automatically for you, but you might need to review the result. This version also comes with support for two audio fingerprinting solutions (AcoustID and AmpliFIND), but fingerprint scanning is disabled by default – you have to enable it and choose which one you want to use first.

Many thanks to Robert Kaye (ruaok), Phillipp Wolfer (outsidecontext), Michael Wiencek (bitmap), Chad Wilson (voiceinsideyou) and many many others who helped the project along the way from 2003 when it was started!

You can download the new version at:

If you notice any problems, please report them at:

Complete list of changes since version 0.16:

  • New UI: Extended comparison of existing vs. MB metadata & tags (PICARD-43)
  • Merged the renaming and moving options pages
  • Removed the VA file naming format option (there is now a single format option) (PICARD-159)
  • Add %license% tag
  • Made %writer% available to tagger scripts and plugins with contents of songwriter (PICARD-21)
  • Allow two multi-valued variables to be merged in tagger scripting (PICARD-139)
  • Allow multi-valued variables to be transformed in tagger script and then set back in tags as multi-valued (PICARD-147)
  • Fix $copy not preserving multi-value variables as documented (PICARD-138)
  • Load/save free-text tags for ID3 as TXXX frames (PICARD-148)
  • Fix writing of MusicBrainz Work Id / musicbrainz_workid to tags (PICARD-88)
  • Handle mimetype for embedding cover art from EXIF jpegs (PICARD-27)
  • Change cover art box to open MusicBrainz release rather than Amazon
  • Support manual drag-and-drop of cover art onto a release via cover art box
  • Only open browser on left-click of cover art box (PICARD-190)
  • Fix Lookup in Browser (previously ‘tag lookup’) for clusters (PICARD-186)
  • Lookup in Browser will now not use MBIDs to lookup unmatched files/clusters
  • Add Date/Country to CD Lookup results dialog (PICARD-198)
  • Fix/reset album folksonomy tag counts while refreshing releases (PICARD-4)
  • Plugins actions can now create sub-menus using the MENU class attribute
  • New plugin hook register_clusterlist_action
  • Display the port Picard is listening on at bottom right status bar (PICARD-191)
  • Make album drops from right hand pane to left default to “unmatched files” again (PICARD-33)
  • Remove .DS_Store, desktop.ini, and Thumbs.db from otherwise empty directories (PICARD-75)
  • Update artist translation to use new alias features (primary flag, sort names) (PICARD-200)
  • Deleted tags aren’t indicated as changes (PICARD-165)
  • Picard log entries have inaccurate timestamp (PICARD-45)
  • Interface doesn’t allow keyboard only management (PICARD-103)
  • Added option to preserve timestamps of tagged files (PICARD-31)
  • Added keyboard shortcut to reload release (PICARD-99)
  • Medium formats weren’t listed in order in the “Other versions” menu (PICARD-91)
  • Couldn’t select multiple directories in “Add Folder” window on OS X (PICARD-74)

20 thoughts on “Picard 1.0 released”

  1. In the options menu, the left side with the sub menus is too small and can’t be correctly resized (only 3 unusuable sizes).

  2. Hmm, just installed: Is it by design, that we can’t drag&drop files/directories/trees from Win7-Explorer to Picard (left panel) anymore?

    I registered for JIRA, but need some help HOW I can report a new issue/question like this…

  3. @Invisibleman78 – Sounds like the issue where Picard runs with the elevated privileges needed for the install when it starts up after the install. Windows stops you dragging stuff from a non-elevated application (e.g. explorer) to an application running with elevated privileges. Close Picard and re-open and drag and drop should work again!

  4. There are two major copy+paste errors (cause by me, and fixed by now) in the German translation file. One error is making the selection of preferred release types nearly impossible, the other one is hiding the “Tools” menu from view. We need a speedy update here. Thanks, and sorry for that.

    Anyway, congrats!

  5. Thank you cerdd83 and Michael Wiencek*! Maybe it would be better in this case, if the user can not start Picard directly from the installer?
    In the meantime, drag&drop works fine. Close and restart solved the problem.

    *thanks for the ticket too!

  6. Invisibleman78 – the option has been removed for the next release; not worth the hassle changing the whole installer process to make this work properly. (although it is technically possible to do so)

  7. The new “original/new value” part is too confusing for me with the scrollbar and useless cryptic hash values, I found it much easier to just compare the basic information like in the previous versions.

  8. @Disappointed: The cryptic hash values are MBIDs, and they’ve always been saved by Picard. One thing they’re used for is to automatically load albums when you add files you’ve previously tagged. However, you don’t have to save them if they’re useless to you. One way to get rid of them is to add $unset(musicbrainz_artistid) etc. to your advanced scripting setting.


  9. Great program! Thanks! One problem: When scanning it skips WMA lossless. Is that by design?

  10. I agree with Disappointed, the old user interface was more simple and clean.
    The new is more cluttered and more power-user oriented.

  11. Re: WMA lossless: I’m guessing it’s unsupported by the version of ffmpeg that was used to build chromaprint. You can still report it at http://tickets.musicbrainz.org/browse/PICARD to keep track of the issue.

    @Disappointed and murdos: I think it’s reasonable to keep both “simple” and “advanced” views as a user-configurable setting and default to the former.

  12. V1.0 looks great so far. I have never used any tagging programs before, so I am still becoming acquainted with the entire process. I have tried installing the LastFMPlus plugin but I am afraid it is not compatible, is this true? What is recommended?

  13. IdeasGirl – LastFMPlus should work fine with Picard 1.0. I’ve flicked you an email separately – but we should be able to work out what’s wrong for you on the Forums. 🙂

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.