MusicBrainz – Page 7 – MetaBrainz Blog

MusicBrainz website mirror will require Node.js 20 starting from November 13, 2023

This announcement is uniquely intended for administrators having installed any mirror of MusicBrainz website with manually installed dependencies instead of using the Docker Compose project musicbrainz-docker.

MusicBrainz website is rendered using Node.js whose minimum required version was 16 so far. This version is reaching end-of-life next week according to their Release Working Group. Therefore MusicBrainz Server will switch to the active LTS Node.js 18 for a transitioning period of two months. It will still support Node.js 16 for previous installations during this period. After that, Node.js 20 will enter its active LTS phase and be required by MusicBrainz website. It has already been used locally in development for a long time, so we don’t expect any major issue when switching mirrors to it.

MusicBrainz Server update, 2023-08-28

On the menu of the day there are some improvements to the editing interface thanks to derat! It’s accompanied with a mesclun of changes (additions, fixes, improvements and updates) related to external links, especially some other databases and new relationship types for art gallery and ticketing. It’s spiced with a pinch of new icons (for collections, genres, and tags) and condiments.

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

Thanks also to HibiscusKazeneko, Lotheric, Trevor, wonder_al, Xythium, yindesu, and yyoung for having reported bugs and suggested improvements. Thanks to chaban, outsidecontext, RandomMushroom128, and salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-08-28.

MusicBrainz Server update, 2023-08-07

This is another summer release with no new features, but it contains a fair amount of small bug fixes and improvements, many related to URL handling. The last user account related pages are also converted to React with this update.

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 atj, chaban, Cyberskull, darkshyne, derat, Freso, scoobert, Van de Bugger and yindesu for having reported bugs and suggested improvements. Thanks to atj and derat for submitting code patches. And thanks to all others who tested the beta version!

The git tag is v-2023-08-07.

Happy 23rd Birthday, MusicBrainz!

23 years is a quite a long time and I had never thought that this little project I was starting in 2000, would grow into what it is today — it has been an amazing journey with many ups and downs. Despite many early hardships, I’m extremely happy that I stuck with it and nurtured the project into an important resource for the internet today.

With that in mind, I feel compelled to tell a story of where the name MusicBrainz came from and how July 17, 2000 was the first day that the name has ever been uttered and the domain was registered seconds later.

MusicBrainz Server update, 2023-07-10

This release makes a few small changes, including an updated set of basic edit icons that hopefully will be the start of a consistent icon set for MusicBrainz. Additionally, and sadly, opening voting for new editors has caused the creation of way too many sock-puppet accounts, so we have been forced to restrict voting for beginner editors again. Hopefully the two week wait is not too long; we’ll look into ways to improve beginners’ experience without helping bad actors in the future.

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 all others who tested the beta version!

The git tag is v-2023-07-10.

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.

New dataset: MusicBrainz Canonical Metadata

The MusicBrainz project is proud to announce the release of our latest dataset: MusicBrainz Canonical Metadata. This geeky sounding dataset packs an intense punch! It solves a number of problems involving how to match a piece of music metadata to the correct entry in the massive MusicBrainz database.

The MusicBrainz database aims to collect metadata for all releases (albums) that have ever been published. For popular albums, there can be many different releases, which begs the question “which one is the main (canonical) release?”. If you want to identify a piece of metadata, and you only have an artist and recording (track) name, how do you choose the correct database release?

MusicBrainz Server update, 2023-06-07

We have a small release this time, slightly delayed because of maintenance work on our servers for the last couple days. The most noticeable changes are probably 68 new locales available for aliases (for example, we can now specify an alias is in Latin language), and a fix to a bug where a small amount of tracks would not be shown in their release’s relationship editor and as such couldn’t have relationships added from that page.

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 salo.rock, UltimateRiff and yyoung for having reported bugs and suggested improvements. Thanks to salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-06-07.

MusicBrainz Server update, 2023-05-22

As announced for our schema change release, after a week of beta testing, the ability to modify or remove edit notes is fully delivered in today’s release! A few other unrelated but small improvements and fixes are included too.

As an editor, you are now able to modify or remove your own edit notes if they’re not older than 24 hours and nobody else has replied; you can see the full set of conditions in our edit note documentation. Admins are allowed to modify or remove any edit note from anyone at any time, and have already been using this to remove some spam and inappropriate comments during the beta period.

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 ShivamAwasthi for contributing code and to kellnerd for helping with code review. Thanks to chaban, Cyberskull, jesus2099 q_fdb and yurim for having reported bugs and suggested improvements. Thanks to salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2023-05-22.

We are ready for Summer of Code 2023 !

A belated congratulations to the 7 contributors that we selected to work with for this year’s Google Summer of Code program!

The competition was fierce this year. MetaBrainz received a huge amount of high quality applications. Narrowing it down gets harder every year – what these contributors did right is getting in early, engaging with our community, presenting specific and detailed proposals, and proving excellent communication skills and the ability to integrate our feedback back into their proposals.