Picard 2.3.2 released

Picard 2.3.2 has been released and is available for download. This is mainly a bug-fix release with few minor improvements, see below for a full list of changes.

This release contains code changes by zas, rdswift, outsidecontext, RaysDev and new contributors Undearius and Gabrielcarvfer, who also is working on some interesting changes regarding UI responsiveness.
Thanks a lot to everybody who contributed to this release with code, translations, bug reports and general feedback.

Download

Picard 2.3.2 is available for download from the download page.

Changes

Below is a list of all changes since Picard 2.3.1. If you are upgrading from an older version you might want to read previous release post.

Breaking change:

$find script function now returns “” rather than -1 on not found, for the sake of consistency. You may want to review your scripts.

Notable improvements:

Picard was trying to guess the file format based on file content. This was very IO expensive and in many cases not needed. So we decided to change the logic to:

  • Try guessing the format by file extension first
  • If no extension or no matching file extension is available, guess by file content
  • If format was guessed by extension and loading the file with mutagen fails with an exception, retry with guessing by file content. Retry loading if the newly guessed format is different from the format guessed by extension.

Also notable, On Windows 10, support for fractional scaling was implemented.

The complete list of changes is the following:

Bug

  • [PICARD-1775] – $firstwords function doesn’t catch IndexError
  • [PICARD-1776] – $datetime crashes when invalid format specified
  • [PICARD-1781] – Have $find return “” rather than “-1” on not found
  • [PICARD-1783] – Deleting performer, comment or lyrics tag fails for some cases in ID3, Vorbis, MP4 and Apev2 tags
  • [PICARD-1784] – Host not found error when downloading PDF artwork
  • [PICARD-1785] – $delete(_id3:TXXX:foo) does not delete the ID3 frames
  • [PICARD-1786] – Deleting tag stored in ID3 TIPL frame only removes first occurrence
  • [PICARD-1787] – Deleting case-insensitive TXXX frames does not delete anything
  • [PICARD-1788] – Saving ID3 tags marked as case-insensitive causes duplicated TXXX frames
  • [PICARD-1790] – Crash when selecting plugin that can be updated
  • [PICARD-1791] – Network access is disabled error under VPN service
  • [PICARD-1795] – iTunes tags not removable (reappear after being deleted)
  • [PICARD-1801] – List index out of range when saving Vorbis file
  • [PICARD-1803] – Instrument EWI is rewritten “e w i”

Improvement

  • [PICARD-1777] – Support fractional scaling on Windows 10
  • [PICARD-1800] – Simplify Unicode ‘Bullet’ to ASCII ‘Hyphen-minus’
  • [PICARD-1809] – Optimize format detection logic

Reminder: Upgrading to PostgreSQL 12 on May 18, 2020

As we announced in February, in two weeks time (May 18, 2020) we’ll be upgrading our production database server to PostgreSQL v12 (from v9.5). At the same time, v12 will become the minimum supported version for MusicBrainz Server, so we ask that you upgrade afterwards as soon as possible! If you’re still unsure, a Q&A is below.

When do I need to upgrade my postgres by?

As soon as possible after May 18 if you’d like to keep your musicbrainz-server code up to date.

How do I perform the upgrade?

We’ll provide instructions closer to May 18. It’s recommended that you don’t upgrade until then, since we’ll be providing scripts to resolve some issues.

Will the live data feed (replication packets) stop working right away if I don’t upgrade?

No, as long as you keep your musicbrainz-server code checkout on the v-2020-05-11 tag (which will be the final release before May 18) or earlier. Future releases may work for a while too.

This is not a schema change release, so replication will continue to work smoothly until you upgrade. No tables or views will change.

However, to make the upgrade process smoother we’ll be dropping the musicbrainz-collate and musicbrainz-unaccent extensions, instead using PG’s builtin collation support for the former and replacing the latter with the unaccent extension from postgresql-contrib. A few SQL functions are being added to enable this, and some indexes need to be rebuilt. This will all happen as part of upgrade scripts we provide (or you can import from scratch). Some features of musicbrainz-server that use these old extensions may cease to work if you don’t apply them.

The extension changes above don’t actually make use of any new PG 12 features. We’ll avoid using such features for at least 1 month.

If I’m already running PostgreSQL 12, do I need to do anything?

Yes, but things will be easier for you. As mentioned in the previous answer, we’ll be dropping the musicbrainz-collate and musicbrainz-unaccent extensions to make the upgrade process smoother for pre-v12 instances. So you’ll only have to run some upgrade scripts we provide to replace those extensions and rebuild some indexes.

My host/distribution doesn’t have PostgreSQL 12 yet!

If you’re running Debian or Ubuntu, the PGDG maintains an APT repository with the latest versions. These are the same packages MetaBrainz uses in production.

Amazon RDS supports PostgreSQL 12 since March 31.

I absolutely cannot upgrade yet! What should I do?

You can stay on the v-2020-05-11 release of musicbrainz-server or earlier until then. Replication packets (i.e. the live data feed) will continue to work until the next schema change on that tag, but you’ll have upgraded to v12 by then, right?

Instead of performing a pg_upgrade and running these upgrade scripts you mentioned, can I just import fresh data dumps into a new v12 cluster?

Of course. Just make sure your musicbrainz-server git checkout is on the v-2020-05-18 tag (once that’s released) or later before performing the import. And keep in mind it may be slower than a direct upgrade.

MusicBrainz Server update, 2020-04-27

A large variety of issue types have been addressed in today’s release!

As a new feature, search indexes are now dumped and made available along with database dumps under the FTP directory search-indexes. They are mainly intended to be loaded on a MusicBrainz slave server to start a mirror with search.

Among improvements, a noticeable one is to lighten the area’s overview page that was heavily crowded with all sorts of relationships that have been scattered over more specific tabs.

As for bugfixes, the major one secures user/admin forms against CSRF attacks.

Thanks to atj for contributing code to support Traxsource URLs. Thanks to alex_s7, chaban, danbloo, Lotheric, murdos, Skeebadoo for reporting issues. Thanks to kellnerd, Jormangeud, mfmeulenbelt, salorock for updating the translations in German, Finnish, Dutch, Italian, respectively. And thanks to all others who tested the beta version!

The git tag is v-2020-04-27.

Bug

  • [MBS-10359] – Guess feat. artists from track titles do not give expected result
  • [MBS-10677] – Place type shown as null on WS event place rels
  • [MBS-10717] – Cookie attributes must be adjusted to work with with new behavior in browsers
  • [MBS-10719] – “remove PUID” edit doesn’t load
  • [MBS-10742] – “Show more” country miscount
  • [MBS-10756] – Inconsistent default sort order for recordings on Works page
  • [MBS-10778] – User/admin forms are prone to CSRF attacks

New Feature

  • [MBS-10546] – Dump MB Solr data along with MB DB full export

Improvement

  • [MBS-1921] – Display edit link under annotations
  • [MBS-9086] – Move most relationships away from area overview
  • [MBS-10666] – Collapse work artists when there are too many on merge pages
  • [MBS-10741] – Make “relationship [attribute] in use” pages consistent
  • [MBS-10755] – Add entity type restrictions for musik-sammler.de URLs
  • [MBS-10781] – Add support for Traxsource URLs

React Conversion Task

  • [MBS-10740] – Convert /relationship static pages to React
  • [MBS-10751] – Convert Remove PUID edits to React

MusicBrainz Server update, 2020-04-13

No Easter egg in today’s update but rather a dozen or so of small bugfixes and convenient improvements.

Thanks Rotab for the pair of bugfixes he submitted, to CatQuest, chaban, chirlu, FSpy, HibiscusKazeneko, JesseW, KRSCuan, MichelV, wcw1966 for issues they reported, to salorock for the Italian translation he updated, and to all others who tested the beta version!

The git tag is v-2020-04-13.

Bug

  • [MBS-7465] – Tag cloud isn’t updated
  • [MBS-9169] – Inconsistent locale identifiers
  • [MBS-9728] – Recently-added Unicode emojis can’t be used in titles
  • [MBS-9894] – Timeline shows future date
  • [MBS-10360] – Whitelist User-Agent header in CORS Preflight requests
  • [MBS-10640] – Incorrect donation status in “Donation Check” tab
  • [MBS-10688] – Attaching a CDTOC that already exists on the medium gives a cryptic error
  • [MBS-10718] – Duplicate series “part of” relationships which got grouped are harder to detect
  • [MBS-10730] – Recording is displayed twice in artist overview when credited multiple times

Task

  • [MBS-10735] – Remove (discontinued) CD Baby links from the sidebar

Improvement

  • [MBS-5641] – Show release language/script in reports ReleasesWithUnlikelyLanguageScript, NoLanguage and NoScript
  • [MBS-10679] – Link to the JSON WS from the Details tab
  • [MBS-10680] – Link to WS docs from the Details tab
  • [MBS-10724] – Make sorting options (area, date, artist) consistent
  • [MBS-10747] – Change wording/phrasing of status description for open edits
  • [MBS-10753] – Use artist sort names for artist collection ordering

MusicBrainz Server update, 2020-03-31

This time we have a couple bugfixes, a couple of small improvements, and continued changes to simplify the React table code.

Thanks to chaban, kellnerd, Kid Devine, and all others who submitted patches, reported issues, tested beta version, or contributed to translations!

The git tag is v-2020-03-31.

Bug

  • [MBS-10704] – Relationships header shown for works with no rels to be displayed
  • [MBS-10707] – Open Add DiscID edit already adds discID, cancelling does not remove it
  • [MBS-10712] – ISE when trying to load “merge release” edit

Improvement

  • [MBS-10669] – Restrict “Metal Archives” album links to release
  • [MBS-10699] – Remove “medley” from Guess Case when at the end of a title

Task

  • [MBS-10365] – Refactor display of entity list/table
  • [MBS-0401] – Replace handshaking protocol with bit mask

MusicBrainz Server update, 2020-03-16

Mostly bugfixes today, along with a new data report, plus usual small improvements, React conversion and refactoring. We also blocked ratings for unverified users, since a specific artist was getting hundreds of ratings by people creating many accounts per person just for that (people, please be nice!).

Thanks to andrybo6, chaban, cyna, dimpole, dseomn, gioele, hibiscuskazeneko, jesus2099, kellnerd, mfmeulenbelt, nikki, outsidecontext, panos, sophist, sothotalker, yindesu, and all others who submitted patches, reported issues, tested beta version, or contributed to translations!

The git tag is v-2020-03-16.

Bug

  • [MBS-7835] – [No lyrics] works showing up as “No linguistic content” in old edit summaries
  • [MBS-9359] – Web service shows “mul” languages, but all single languages are duplicates
  • [MBS-9651] – Top voters overall includes more edits than editor profile’s yes+no+approve
  • [MBS-10628] – [no label] should not be editable
  • [MBS-10633] – Can’t change capitalization on username
  • [MBS-10661] – Recording-work rel not showing pending edits on release page
  • [MBS-10683] – Map doesn’t focus on new marker when creating a new Place
  • [MBS-10684] – Message over Place’s map is misleading
  • [MBS-10685] – Place maps: Zooming by clicking doesn’t follow the cursor
  • [MBS-10693] – Artist merge submission page doesn’t show any error message if you attempt to merge a special purpose artist

Improvement

  • [MBS-4090] – Report for recordings with a single track but with different spellings
  • [MBS-10607] – Give context to translations of “unknown” / “(unknown)”
  • [MBS-10676] – Add MD5/SHA256 checksum files for JSON data dumps
  • [MBS-10695] – Show full language names on work lists

React Conversion Task

  • [MBS-10618] – Convert Edit work edit to React

Other Task

  • [MBS-10671] – Block ratings for unverified users
  • [MBS-10689] – Update MapBox API calls
  • [MBS-10692] – Change React imports to “import * as React”

MusicBrainz Server update, 2020-03-02

It’s now possible to find genres through the web service with a new /ws/2/genre lookup endpoint. Additionally, this update fixes some bugs and refactors a lot of stuff behind the curtains, including the continued conversion to React of edit display pages.

Thanks to chaban, cyna, jesus2099, kellnerd, and speardog who contributed through issue reporting, code changes, translation updates, and beta testing.

The git tag is v-2020-03-02.

Bug

  • [MBS-10515] – Weird display of recording info on release merge pages
  • [MBS-10593] – “Edit release label” edit fails to load if country name is undef
  • [MBS-10594] – “Add annotation” edits are stuck
  • [MBS-10649] – Release label edit shows [removed] if label is deselected
  • [MBS-10659] – “Edit relationship” edit not showing credits if they don’t change

New Feature

  • [MBS-10166] – Add genre lookup to the web service

Improvement

  • [MBS-9654] – Show expanded artist credits in “Merge recordings” edits
  • [MBS-10643] – Autoselect relationship type for CPDL artist URLs

React Conversion Task

  • [MBS-10058] – Convert entity merge edits to React
  • [MBS-10617] – Convert “Add work” edit to React

Picard 2.3.1 released

Picard 2.3.1 has been released and is available for download. This is mainly a bugfix release, but also some smaller improvements and features made it into this version. Notable changes are the addition of the $sortmulti and $reversemulti scripting functions, overall better handling of releases with multiple release countries and some fixes for the AcoustID fingerprinting. See below for a full list of changes.

This release contains code changes by zas, rdswift, outsidecontext and new contributor RaysDev, who also is working on some interesting changes for the next release. Thanks a lot again to everybody who contributed to this in release with code, translations, bug reports and general feedback. The Picard 2.3 release already was well received, but it is thanks to you all that we can provide a sizeable list of improvements just 10 days later.

Download

Picard 2.3.1 is available for download from the download page.

Changes

Below is a list of all changes since Picard 2.3. If you are upgrading from an older version you might want to read what is new in Picard 2.3.

Bug

  • [PICARD-1745] – Packaged libdiscid is not compatible with macOS 10.12
  • [PICARD-1748] – Many release events can cause the versions context menu to overflow
  • [PICARD-1750] – Existing acoustid_fingerprint tags are not considered for AcoustID submission
  • [PICARD-1754] – DEL always removes release or file from main window
  • [PICARD-1756] – Plugin update fails to compare plugin versions with double digit versions
  • [PICARD-1757] – Crash on loading a release if $div(n,0) is used in a script
  • [PICARD-1760] – Prevent duplicates in top tags editor
  • [PICARD-1762] – Dropping a PDF file on cover art image box doesn’t work
  • [PICARD-1765] – Adding uppercase tags to preserved tags list is not handled correctly
  • [PICARD-1772] – Unexpected results with $num function
  • [PICARD-1773] – Untrapped error on $mod with zero input
  • [PICARD-1774] – $lenmulti with missing name returns “1”

New Feature

  • [PICARD-1743] – Add script functions $sortmulti and $reversemulti to sort and reverse multi-value variables
  • [PICARD-1751] – Provide a %_releasecountries% variable

Improvement

  • [PICARD-1746] – Change Generate AcoustID Fingerprints shortcut to Ctrl+Shift+Y / ⌘⇧Y
  • [PICARD-1752] – Use preferred release countries to select a matching release country if there are multiple
  • [PICARD-1755] – “Supported Languages” on Microsoft Store shows only English (United States)
  • [PICARD-1759] – Make editing tags in top tags list more intuitive
  • [PICARD-1771] – Completely ignore release types set to zero in preferred releases

 

MusicBrainz Server update, 2020-02-18

Today’s release brings a fair amount of small bug fixes and improvements to the website. Notably, it changes the way we display relationships to group ones that are similar (such as different instruments by the same performers) and makes editing history (but not editors and edit notes!) available to visitors without needing to log in.

Thanks to chaban, chirlu, cyberskull, cyna, dimpole, hibiscuskazeneko, jeandeaual, kellnerd, lotheric, mfmeulenbelt, murdos, nikki, rdswift, salorock, supersandro2000, v6lur, and all others who submitted patches, reported issues, tested beta version, or contributed to translations!

The git tag is v-2020-02-18.

Bug

  • [MBS-2436] – “Edit medium” edits don’t link to new recordings
  • [MBS-10209] – Error parsing URL when entering Instagram link on artist’s page
  • [MBS-10223] – ArtistRoles lists don’t use relationship credits
  • [MBS-10329] – URL cleanup breaks Amazon Music URLs
  • [MBS-10576] – Medium merge error messages with links are not properly formatted
  • [MBS-10583] – Event dates displayed twice in event lists
  • [MBS-10586] – Release duplicates tab shows [missing media] when medium format is simply unknown
  • [MBS-10587] – Medium counts broken in Release Duplicates list
  • [MBS-10588] – Medium formats untranslated in Release Duplicates list

New Feature

  • [MBS-3873] – New Report: Release groups with name not matching release’s name
  • [MBS-10331] – Add new URL cleanup/autoselect/sidebar for Amazon Music URLs
  • [MBS-10620] – Add the Discography of American Historical Recordings to the otherdbs whitelist

Improvement

  • [MBS-4326] – Add “Add discid” edits in release artist(s) editing history
  • [MBS-7678] – Combine display of multiple relationships to the same entity
  • [MBS-9164] – Show edit history (but not edit notes) when not logged in
  • [MBS-10308] – Cleanup maniadb URLs
  • [MBS-10584] – Collapse work artists when there are too many
  • [MBS-10623] – Automatically add US store country-code to iTunes URLs missing it
  • [MBS-10625] – Block even more smart links

React Conversion Task

  • [MBS-9917] – Convert the instrument public pages to React
  • [MBS-10401] – Convert Edit Series edit to React

Picard 2.3 now available

The Picard team is happy to announce that version 2.3 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 changes across the board, including additions to the user interface, performance improvements, better tag support, improved desktop integration and many more.

Notable changes

User interface

Picard now allows you to customize the columns in the main panel, so you can choose to see additional details about the files you are tagging, such as album artist, composer, catalogue number, genre and more. And while it has always been possible to reorder and resize the displayed columns, Picard will now remember your settings.

Picard's new configurable columns

Editing tags became more comfortable with multi-line editing for comments and lyrics and autocomplete for media, release country, release type and release status and the ability to reorder the values of multi-value tags. For date tags there is an indication of the expected format shown as “YYYY-MM-DD”. You can now also specify which tags you want to have always on top in the tag editor (Options > User Interface > Top Tags).

Easy submission of AcoustID fingerprints

One complaint we often received was about the ability to submit fingerprints to AcoustID. While Picard leverages AcoustID for identifying your files and searching matching recordings, and you can submit the fingerprints for such scanned files if the found match was wrong. But just using Picard to submit fingerprints for your already well tagged files without doing another search and match was not possible. To address this we added a “Generate AcoustID fingerprints” action which allows you to just generate the fingerprints. There is also a new “Fingerprint status” column which will indicate whether a fingerprint was calculated for a file or not. As can be seen above this uses the new configurable column feature. A red fingerprint icon indicates the fingerprint has been calculated. Once you submit the fingerprints the fingerprint icon will turn gray.

Desktop integration

Picard on Windows will now indicate the progress when loading or saving many files in the Windows taskbar.

picard-windows-taskbar

The same is available on Linux if your desktop environment supports it, e.g. if you are using KDE Plasma or the default Ubuntu desktop.

picard-plasma-taskbar

picard-ubuntu-dock

On macOS Picard is now registered for supported file types. That means you can directly open your music files in Picard using Finder. Furthermore you can also drop files or entire folders directly onto the Picard dock icon.

Performance improvements

We addressed some cases where the Picard user interface became totally unresponsive for a while when clustering files or moving and matching files to releases. This was most notable when working with large releases with several hundred tracks.

Tags and file formats

With custom tags support for MP4 files an often requested feature is now finally available.

There is also new support for raw AC3 files and more details are shown for TAK files. For AC3 and AAC files Picard can save APEv2 tags, which is supported by many other tools, but also can cause problems in others. E.g. players not supporting tags in AC3 and AAC files will often show a wrong duration if there are APEv2 tags present in the file. Hence you can now choose whether to save APEv2 tags to files or not, or even remove existing APEv2 tags for those files.

Scripting

Few new script functions were added:

  • for strings: $find, $reverse, $substr
  • for multi-value variables: $getmulti, $slice, $join
  • for loops: $foreach, $while, $map
  • for current date and time: $datetime

Complete documentation can be found on Picard website.

Breaking changes

We fixed some scripting functions that are supposed to be used as conditions but behaved differently. This affects $is_complete(), $startswith() and $endswith(). If you use one of these functions in your script please read this forum post on how to update your scripts.

Packaging

If you are using Windows 10 you can now install Picard from the Windows store and receive future updates automatically.

Picard for Windows is now also available as a portable application, which you can run directly without installation. You can put it in any folder, including putting it on a USB thumb drive, and it will store all its settings and plugins in the folder it is located in.

The Picard installer and portable app are now signed with a certificate issued to the MetaBrainz Foundation. When you run the installer or the portable app for the first time after download Windows will show you a dialog like the following:

windows-smartscreen

Official releases, including beta version and development builds, will show “Metabrainz Foundation Inc.” as the publisher. If it is showing anything else, e.g. “unknown”, this indicates you are not using an official release. Once enough people have trusted the app the above warning will eventually completely go away.

For macOS the Picard app is now also fully compatible with macOS 10.15 Catalina, which means you can run Picard now without security warning.

More changes and bug fixes

Picard 2.3 has many more improvements and fixes. See the full changelog for details on all changes since the last stable Picard 2.2.3.

Download

Picard 2.3 is available for download from the download page as well as from the Windows Store.
English badge

Known issues

On macOS 10.12 Sierra the CD lookup functionality is unavailable. We will address this issue in Picard 2.3.1. See PICARD-1745 for details.