Development – Page 2 – MetaBrainz Blog

MusicBrainz Server update, 2025-02-24

This release includes several mid-sized improvements requested by multiple editors, in addition to the usual URL cleanup changes, bug fixes, and smaller improvements.

We have extended the filtering tools already available on artist pages so that they will also work on label pages, allowing users to filter the releases from that label according to several different conditions.

We have separated artist-work relationships not related with authorship so that they will no longer appear under the “writers” section of works lists (now renamed to “authors”). This allows to distinguish a lot more easily whether a an artist is related to a work as an author or in another, generally more minor way.

Finally, a newly added set of last-year editor stats aim to give editors who are motivated by leaderboards but have not already been active for an eternity (and as such would be hard-pressed to ever get into the “top editors/voters of all time” leaderboards) an achievable goal which rewards consistency more than the current weekly stats do.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to derat, ernst-roux-dice and Maxr1998 for having contributed to the code. Thanks to Gary Young, KenParker_CN, Maxr1998, mr_maxis, salo.rock, UltimateRiff, yindesu and yomo12 for having reported bugs and suggested improvements. Thanks to delamons, EmO686, KenParker_CN, percylee, PS123 and salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2025-02-24.0.

Picard 2.13.3 released

Picard 2.13.3 is a maintenance release for the recently released Picard 2.13. This primarily fixes a regression with the Windows package, where a system wide installed libssl would cause SSL failures in Picard’s network requests. This release also includes a workaround for libopus not loading embedded cover art files.

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.12 please see our detailed release announcement for Picard 2.13.1.

MusicBrainz Server update, 2025-02-10

This is a small release that mostly includes URL display improvements. Additionally, it further improves RTL display and adds a new report for lonely pseudo-releases (poor them, please go help them).

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to dvirtz and Maxr1998 for having contributed to the code. Thanks to dvirtz, HibiscusKazeneko, Maxr1998, raelthelamb, UltimateRiff and yindesu for having reported bugs and suggested improvements. Thanks to KenParker_CN, Peter69, Ral Hole and wileyfoxyx for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2025-02-10.0.

Picard 2.13.2 released

Picard 2.13.2 is a maintenance release for the recently released Picard 2.13 which fixes a crash when opening the context menu for multiple selected changed tags.

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.12 please see our detailed release announcement for Picard 2.13.1.

MusicBrainz mirror security advisory, 2025-01-29

After the recent disclosure of CVE-2025-24814 which is affecting those of MusicBrainz mirrors that publish the port for the search service, we remind mirror owners to follow upstream security recommendations when publishing ports. See the release notes for details.

MusicBrainz Server update, 2025-01-27

This release includes, among the usual small bug fixes and improvements, two small changes worth mentioning specifically.

The first is an improvement that has been requested often: it is now possible to filter all versions of an artist’s index page. That means non-official and various artists release groups can be filtered using the same tools previously available for the standard official groups view. Enjoy, live bootleg lovers!

The second is that account administrators can now immediately accept or reject any edit (even ones that cannot normally be approved). This is an anti-vandalism measure, and the plan is to use it only in cases where spam and vandalism should be removed as soon as possible, rather than waiting for a specific number of days and/or votes. When used, a new type of vote “Admin approval” / “Admin rejection” will be indicated on the edit votes list.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to Aszazin, chaban, Griomo, MonkeyPython, otringal, phantomenlister, UltimateRiff and wileyfoxyx for having reported bugs and suggested improvements. Thanks to Besnik, guardiansock, KenParker_CN, Peter69, poromies00, salo.rock and Vaclovas Intas for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2025-01-27.0.

MusicBrainz Server update, 2025-01-13

Welcome to the first release of 2025! This includes a lot of small improvements and fixes, and one larger change: using primary aliases for more entities and in more places.

Primary aliases for all entities except instruments (which can be translated directly) will be displayed after the entity name when they exist, just like a disambiguation comment. This extends the existing feature for artists written by derat a few months ago (thanks derat!). If you find some places where the aliases should be displayed, but aren’t, please let us know with a ticket!.

Keep in mind aliases will only be shown if they are marked as primary for the language you are browsing MusicBrainz in (you won’t see English aliases if browsing in French, for example). If you see an entity is missing an alias in your language that would help people more easily understand what it is, add it!

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to derat and dvirtz for having contributed to the code. Thanks to Aszazin, chaban, derat, dvirtz, Freso, HibiscusKazeneko, Lotheric, Raman Sinclair, sammyrayy, ThunderMite42, Vac31. and vaibhav for having reported bugs and suggested improvements. Thanks to Besnik, chaban, Crowbardoctor, dirt3009, guardiansock, imgradeone, liilliil, Peter69, poromies00, salo.rock and wileyfoxyx for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2025-01-13.0.

MusicBrainz Server update, 2024-12-09

This release includes only small changes and features, including a fix for a regression in the new email system (thanks Jade for the continued work on this).

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to Jade Ellis and Suvid Singhal for having contributed to the code. Thanks to chaban, Lotheric, outsidecontext and practik for having reported bugs and suggested improvements. Thanks to KenParker_CN, Peter69, salo.rock, Vaclovas Intas, wileyfoxyx and yyb987 for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2024-12-09.0.

Pissed off by Spotify Enshittifying more API endpoints? We can help!

Today Spotify announced that a number of APIs will no longer be available for new users.

While Spotify won’t immediately take away these endpoints for existing users, it certainly does not inspire confidence for their longevity. Spotify cites “security reasons” as an explanation of why they are closing off these APIs, but we are unclear as to how that will improve security, so we need to assume that Spotify has some other motivations behind this move. More likely than not, they are hatching a strategy to protect their algorithmic assets from data crawlers used by third-party AI companies.

Needless to say, the Spotify services continue to get enshittified, taking away very useful features that developers have come to rely on. ListenBrainz has very different goals, being entirely open-source and part of a non-profit foundation, and we won’t pull the rug out from under our users for monetary or “security” reasons.

On the contrary, our very small team works in direct collaboration with users and developers interested in developing new discovery tools in the music space, and we embrace the variety of ways passionate music lovers want to interact with music collections and recommendations.

Our own frustrations with Spotify’s ever-worsening recommendations was the spark that lit up our interest in recommendations, but again our approach is one of fairness (we don’t tip the scales) focused on the user’s experience rather than the deep pockets of multinational labels.

For developers frustrated that their app stopped working, the good news is that the ListenBrainz team has been working on building some new datasets and API endpoints that offer replacements for what Spotify is taking away. While not everything that Spotify is enshittifying has a direct replacement with ListenBrainz, we can at least offer a path forward for developers.

These features/datasets include:

Artist similarity*: You can use our ListenBrainz Labs API to explore similar artists.The similarity datasets are still somewhat limited, since we’ve not been able to run all available data through that algorithm, but we plan to do that in the very near future.
Recommendations for a user: Recommendations are available for ListenBrainz users who send us listen information.
Custom playlist generation: https://listenbrainz.org/explore/lb-radio/ allows you to customize generated playlists as in-depth as you want (see the documentation for more details)
Popularity data: Find out the popularity of artists on ListenBrainz, as well as popular tracks for an artist
Fresh releases: Keep up with new albums coming out, generally or specifically for your taste (as seen on https://listenbrainz.org/explore/fresh-releases/)

Future new datasets include:

Track similarity
Album similarity
Your dream feature here

All of this data is Creative Commons CC0 licensed (read Public Domain) and available on our API endpoints, for free, forever. MetaBrainz is a California 501(c)3 non-profit organization dedicated to creating, maintaining and ensuring that these datasets are available for public use.

And on top of that, the person who coined the term “Enshittification”, Cory Doctorow, has been on our board of directors for 20 years, further ensuring that we’re enshittification proof.

Come play with our data – we’d love your feedback! We’re working hard to make this data better and if it doesn’t yet meet your needs, we hope to meet them soon!

* for the similar artist search, use this value for “algorithm”: session_based_days_7500_session_300_contribution_5_threshold_10_limit_100_filter_True_skip_30

MusicBrainz Server update, 2024-11-18

Image editing has been re-enabled after being down for the past month, so it’s now time to upload your backlog of scanned artwork if you haven’t already done so on the beta site! The rest of the changelog is short, but we’ll give a special mention to JadedBlueEyes, whose GSoC project is now being used for sending emails between editors. You’ll notice that a newer, fancier email template is now used for such messages. We hope to convert the rest of the emails we send out to use the new service soon, in future server releases.

A new release of MusicBrainz Docker is also available that matches this update of MusicBrainz Server. See the release notes for update instructions.

Thanks to derat and JadedBlueEyes for having contributed to the code. Thanks to Xythium, jlks82, and roman412 for having reported bugs and suggested improvements. Thanks to ApeKattQuest/MonkeyPython, KenParker_CN, and yyb987 for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2024-11-18.0.