We have released Picard 2.2.1, which is a small bugfix release for the recently released Picard 2.2. Thanks to everybody who gave feedback and reported issues.
Picard 2.2.1 is available for download on the Picard website.
The changes in detail:
Bug
[PICARD-1603] – Translations from picard/ui/colors.py don’t show up in Picard
[PICARD-1604] – Windows install is not using Qt default translations
[PICARD-1607] – Upgrading a plugin displays the dialog box multiple times
[PICARD-1608] – “[non-album tracks]” can not directly be removed
[PICARD-1609] – Picard About shows Qt version PyQt was build against, not actually used Qt
Improvement
[PICARD-1602] – Tests should not be included in the sdist package
The Picard Team is proud to announce the release of MusicBrainz Picard 2.2. This version provides a number of new features and bug fixes. Some of the highlights are:
Files can be moved to sub folders without renaming the actual file (see below for details).
Colors used for highlighting changes in files and metadata can now be configured in options.
A new integrated media player toolbar. This feature is considered beta and is disabled by default, but you can enable the toolbar in the menu with View > Player. Please note that the file formats supported by the player depend on your operating system.
New plugin hooks which trigger when a file was added to a release, a file was removed from a release, a file was saved and a file was loaded.
Improved support for dropping cover art images directly from Google and Bing image search results.
Support for ReplayGain 2.0 tags.
There are a few potentially backward incompatible changes.
Amazon cover art moved to plugin: If you have been using the Amazon cover art you will need to install the Amazon Cover Art plugin in Options > Plugins. The functionality remains the same, we just moved it to a plugin.
Moving files without renaming creates folder structure: Previously Picard would just drop all files into the selected target folder if “Move files” was enabled but “Rename files” was disabled. This was not very useful. Now Picard will generate the folder hierarchy according to your script.
If you want to retain the old functionality use a renaming script that does not generate any folder hierarchy (no slash or backslash characters in the script).
The minimum supported macOS version is now macOS Sierra (10.12) or higher. If you are using macOS 10.10 or 10.11 you can continue using Picard 2.1.3.
Picard 2.2 is available for download on the Picard website.
Thanks to everybody who contributed to this release with code, translations, testing, bug reports and general feedback. This is much appreciated and we are always happy to see new contributors.
Here is the full changelog:
Bug
[PICARD-456] – “Delete empty directories” should not delete special folders such as the desktop
[PICARD-571] – Scripting and renaming font on macOS and Windows not monospace
[PICARD-622] – File Browser resets horizontal scrolling on selection change
[PICARD-765] – Refreshing a release reloads the CAA index.json file from cache, even if it changed online
[PICARD-1025] – An empty destination directory prevents the options from being saved, but doesn’t show an error
[PICARD-1090] – Match quality indicators are blurry
[PICARD-1282] – ⌘W does not close Preferences window
We’re happy to announce the release of our May 2019 schema change today! Thanks to all who were patient during today’s downtime as we released everything to our production servers.
This is a fairly minor release as far as schema changes go, but please do report any issues that you come across, especially any related to genres and collections.
Visible changes with this release are limited to an indication if a specific artist credit is being edited (MBS-5387). Work on some of the changes to collections and genres is quite advanced, and we’re hoping to release some of the new features onto beta already in a week or so from now, while others might take a while longer.
Now, on to the instructions.
Schema Change Upgrade Instructions
Note: Importing the latest data dump is always a valid alternative to running ./upgrade.sh on an existing database, if you’d prefer to also get new data in one go. Just follow the relevant instructions in INSTALL.md. The git tag is v-2019-05-13-schema-change. The rest of the instructions here assume an in-place upgrade.
Make sure DB_SCHEMA_SEQUENCE is set to 24 in lib/DBDefs.pm.
If you’re using the live data feed (your REPLICATION_TYPE is set to RT_SLAVE), ensure you’ve replicated up to the most recent replication packet available with the old schema. If you’re not sure, run ./admin/replication/LoadReplicationChanges and see what it tells you; if you’re ready to upgrade, it should say “This replication packet matches schema sequence #25, but the database is currently at #24.”
Take down the web server running MusicBrainz, if you’re running a web server.
Turn off cron jobs if you’re automatically updating the database via cron jobs.
Switch to the new code with git fetch origin followed by git checkout v-2019-05-13-schema-change.
Install newer dependencies Yarn and NodeJS 8 or later according to install prerequisites.
Run cpanm --installdeps --notest . (note the dot at the end) to ensure your perl-based dependencies are up to date.
Run ./upgrade.sh (it may take a while to vacuum at the end).
Set DB_SCHEMA_SEQUENCE to 25 in lib/DBDefs.pm as instructed by the output of ./upgrade.sh.
Turn cron jobs back on, if applicable.
Restart the MusicBrainz web server, if applicable. It’s also recommended you restart redis. If you’re accessing your MusicBrainz server in a web browser, run ./script/compile_resources.sh.
Here’s the list of resolved tickets:
Bug
[MBS-5387] – ACs being edited aren’t marked as having pending edits on the aliases tab
[MBS-9365] – event_meta_fk_id was never created as part of any upgrade script
[MBS-9462] – Standalone databases created before schema 21 are missing some l_event_url triggers
[MBS-10146] – Regression: ISE on Remove DiscID page
[MBS-10149] – Swap track titles with artist credits fails to update both fields properly
[MBS-10150] – Regression: The link to the release group reviews in the release page is broken
Improvement
[MBS-9664] – Add database constraints to disallow loop relationship
We finally have a new release! Some large conversions of the MusicBrainz website templates to React happened during the past three months, leading to a long delay between releases – sorry about that! This release also fixes several bugs and adds some small improvements.
Thanks to Cyna, Ge0rg3, and spellew for their contributed code, mostly written during GCI. Also, thanks to alpinetux, amCap1712, chirlu, culinko, cyberskull, derobert, Griomo, hibiscuskazeneko, Jeluang, jessew, kepstin, Kid Devine, ListMyCDs.com, Lotheric, mfmeulenbelt, rafwuk, RavenWorks, samj1912, yindesu, yurim, and everyone who tested beta version, reported issues, or updated website translations.
Much of the initial part of this mini-version was done during let’s get serious. However, after coming back to it later, it became apparent that a more overarching edit and reorganization of idiophones was needed, so the second phase of this work involved linking existing and creating new idiophone instruments and organizing them.
Many of the tickets in this version were created or improved by students during GCI ’18. Many thanks to our students George Omnet and Jayant Dharwadkar, especially!
MiniVersion Clapper tree
[INST-630] – Rearrange idiophone tree (was: Create clapper tree)
Thanks in great part to the new How to Add Instruments guide, we now had a framework to better objectively review inclusions of instruments. Following that, these instruments were found to be either not applicable (noisemakers not intended for music as such, rather than musical instruments) or to be too much of a novelty instrument:
Closed as not applicable / Reopen if/when musical use is demonstrated
The improvement of the idiophone section isn’t completely done however! Some more work is needed: moving and/or renaming the “tuned percussion” instrument (which is basically equivalent to the “percussion struck idiophones” in Hornbostel-Sachs already anyway) and (possibly) getting rid of “metallophone” (which is almost a duplicate of tuned percussion in function today, and that in meaning is basically just “idiophones made of metal”), which doesn’t seem necessary anymore.
We expect to release a new stable Picard version in few days.
Very few translatable strings changed since last version, so it would be great if active translators could translate those before the release.
Thanks !
Hi everyone! As you might remember, our last post was the end of a series of entries meant to summarize everything that had happened in instrument-land so far. So now that catching up is done, here’s what has happened lately!
MusicBrainz Picard 2.1 is finally here. This version includes a lot of fixes and improvements over previous stable version (2.0.4). It is recommended to upgrade of course.
new convenient script functions: $title and $delete
new command line option (-P, --no-plugins) allowing to skip plugin loading, which may help when a plugin is crashing Picard at start and to identify if an issue is due to a plugin or the main program
improve tags support, better compatibility with other applications, wider range of audio files supported
better stability and performance
I’d like to thank all developers, translators, testers and users who contributed to this version, kudos to Philip Wolfer (phw).