Category: MusicBrainz

Posts related to the MusicBrainz encyclopedia in general: community, data, client, server, etc.

Picard 2.9 Beta 3

The MusicBrainz Picard team has just released a third beta for the upcoming Picard 2.9. This addresses issues and feedback we got after the beta 2 release. See the section “What’s new?” for details.

Picard 2.9 Beta 3 is supposed to be the final pre-release we put out for wider testing and to gather feedback on the changes before the final 2.9 release.

Please report any issue through our bug tracker and give us feedback on this beta release on the Community Forums.

Thanks a lot to everybody who contributed to this release with code, translations, bug reports and general feedback.

Continue reading “Picard 2.9 Beta 3”

Picard 2.9 Beta 2

After our first beta release for Picard 2.9 we had some improvements, but also did an unusual amount of additional refactoring for parts of the code. Especially the code webservice requests module and handling of locale settings got some important improvements.

Hence we decided to do a second beta for the upcoming Picard 2.9. This is a pre-release we put out for wider testing and to gather feedback on the changes before the final 2.9 release.

Please report any issue through our bug tracker and give us feedback on this beta release on the Community Forums.

Thanks a lot to everybody who contributed to this release with code, translations, bug reports and general feedback.

Continue reading “Picard 2.9 Beta 2”

How to build your own music tagger, with MusicBrainz Canonical Metadata

In the blog post where we introduced the new Canonical Metadata dataset, we suggested that a user could now build their own custom music tagging application, without a lot of effort! In this blog post we will walk you through the process of doing just that, using Python.

Continue reading “How to build your own music tagger, with MusicBrainz Canonical Metadata”

Picard 2.9 Beta 1

The Picard team is happy to announce the availability of the first beta release for the upcoming Picard 2.9. This is a pre-release we put out for wider testing and to gather feedback on the changes before the final 2.9 release.

Please report any issue through our bug tracker and give us feedback on this beta release on the Community Forums.

Thanks a lot to everybody who contributed to this release with code, translations, bug reports and general feedback. This release contains contributions by Laurent Monin, Philipp Wolfer, Bob Swift, David Kellner, Tushar Rohith, Aerozol and certuna.

Continue reading “Picard 2.9 Beta 1”

Style Guideline Updates

If you’ve been lurking on our forums, you will know that our style guidelines have been receiving lots of attention lately! Both MusicBrainz docs and BookBrainz docs have been getting new additions and updates, and there’s still plenty being discussed. As I type these very words, there are greased-up editors in what’s known to us only as “the pit” – pitting their words, experience, and muscular bodies against each other in a bid for dominance over typographical punctuation.

Okay, okay, so there’s not really a pit, but here’s a rundown of some of the style discussions that are taking place, or have taken place, this year:

Continue reading “Style Guideline Updates”

Schema change release: May 15, 2023

MusicBrainz is announcing a new schema change release for May 15, 2023. The actual schema (database) changes we’ve detailed below shouldn’t have much perceivable impact on mirror servers, especially if you only use the web service; most are to remove unused tables/columns or tweak how certain tables are materialized.

Continue reading “Schema change release: May 15, 2023”

Picard 2.9 alpha 1 available for testing

Today we have released an alpha version for the upcoming Picard 2.9. The main change coming with this release is limiting Picard to a single instance by default and the ability to run commands inside this running Picard instance from the command line. This work was done by skelly37 as part of last year’s Google Summer of Code.

Keep in mind that we consider this an alpha release and it might contain bugs. As the single-instance mode by default is a significant change on how Picard is being run we want to gather some feedback on the new functionality before we do a final 2.9 release.

Continue reading “Picard 2.9 alpha 1 available for testing”

Unexpected Picard Setups

This article is showcasing some of the more unusual ways MusicBrainz Picard can be run. Some are useful, some are more technically interesting solutions.

The description in MusicBrainz Picard’s README file says:

MusicBrainz Picard is a cross-platform (Linux, macOS, Windows) audio tagging application.

So yes, Linux, macOS and Windows are our officially supported platforms and the main targets for running Picard. If you are using Picard you likely do this on a laptop or desktop computer running one of these three operating systems. We already offer plenty of options to install and run Picard, including our official downloads for Windows and macOS, Picard in the Microsoft Store for Windows 10 and 11 and the popular Linux packages Flatpak and Snap.

But as Picard is free software you can get it running essentially anywhere were Python and PyQt5 are available. Let’s start this year with showcasing some of the more unusual ways Picard can be run. Some are useful, some are more technically interesting solutions.

Continue reading “Unexpected Picard Setups”

Picard 2.8.5 released

Picard 2.8.5 is a maintenance release for Picard 2.8, fixing two regressions found in the previous release.

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

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

What’s new?

Bugfixes

  • [PICARD-2590] – Relative paths for cover art file names no longer work
  • [PICARD-2593] – Toolbar icon text disappears when saving options
  • [PICARD-2596] – “Show icons in menus” option is applied without saving options

Get in touch

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