MusicBrainz Server update, 2021-06-28

This time we have a release with a fair amount of small bug fixes and improvements, but the main improvement you might notice is that release pages are now a lot more efficient for releases with a lot of tracks. Any release with more than 100 tracks will be loaded only partially, and more tracks can be loaded if useful. This avoids loading hundreds of tracks (and all relevant relationships) in cases where the user doesn’t actually need them, and it will make it possible to load some releases with over a thousand tracks which would consistently time out before.

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 yyoung for improving errors in URL editor. Thanks to chaban, Cyberskull, jaw111, Jeluang, jesus2099, nikki, salo.rock, Yurim for having reported bugs and suggested improvements. Thanks to Besnik, kellnerd, mfmeulenbelt and salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2021-06-28.

Fixed Bug

  • [MBS-6811] – Edit note permalinks are not always canonical
  • [MBS-8678] – Split Artist not blocked by all relationships
  • [MBS-8844] – “Display Credits at Bottom” doesn’t work for releases with collapsed mediums
  • [MBS-11522] – Regression: Link to release group missing in “Set cover art” edit
  • [MBS-11697] – Old release group type (now secondary) not displayed on edits
  • [MBS-11703] – Release index pages with a lot of tracks and relationships often time out
  • [MBS-11724] – Typo in Disc IDs attached but not applied report
  • [MBS-11734] – ISE when filtering duplicate artists report
  • [MBS-11737] – The cover art upload form claims “we don’t own the associated item” even though we do

Improvement

  • [MBS-5632] – Make it clear in Set Cover Art edits that the old cover art is not displayed because it was automatically picked
  • [MBS-5680] – Allow inc=artist-credits when combined with release-group-rels, release-rels or recording-rels
  • [MBS-8700] – Include genres in JSON-LD (RDF) representation of resources
  • [MBS-9695] – Allow editing link_creditable_attribute_type / link_text_attribute_type from the UI
  • [MBS-9826] – Make edit expiration time show days + hours when it will take more than a day
  • [MBS-10307] – Cover art types selector are inconsistent between add and edit actions
  • [MBS-11342] – Clarify that recording duration will change if track duration is changed
  • [MBS-11421] – Give useful message when trying to split empty artist
  • [MBS-11644] – Allow specifying target release MBID when moving disc ID
  • [MBS-11698] – More specific target of external link error messages

New Feature

  • [MBS-8070] – Show Events in contained Places in Area Events tab
  • [MBS-8866] – Show Artist relations on Split Artist page

React Conversion Task

  • [MBS-9921] – Convert the release index page to React
  • [MBS-11520] – Convert Remove Relationship Type edit to React
  • [MBS-11523] – Convert Set Cover Art edit to React

Other Task

  • [MBS-10463] – Remove the iframe-based cover art image uploader
  • [MBS-10711] – Convert standard report lists to react-table
  • [MBS-11677] – Add Selenium tests for the CAA

ListenBrainz will soon require a valid email to submit listens

Starting with today’s update of the ListenBrainz server, we now require new account sign-ups to provide a valid and verified email in order to submit your listens. Existing accounts have until 1 November 2021 to meet this requirement, with users being reminded to add their email addresses when they log in. To avoid losing listens come November, we urge you to add an email address to your account now.

We dislike taking this step, but sadly we’ve seen an uptick of spam listens (why???) being submitted to ListenBrainz. Having a verified email address will deter some people from submitting spam listens, but most importantly it allows us to contact users about their listen histories. Sometimes it can be hard to judge if someone’s listening history is not particularly diverse or if they are a spammer.

Having an email allows us to contact users whom we suspect of spamming, ensuring that we don’t delete valid user profiles.

Thanks!

Kendraio Bounty: MusicBrainz integration

Our friends over at Kendraio want to integrate the MusicBrainz API into their app and are offering a bounty to a developer to help them do it. Kendraio App is a low-code bi-directional dashboard data browser. The aim is to enable Kendraio App users (including music artists) to search and browse, and also upload information to MusicBrainz. Here’s a ready-made example of how easy it is to create Kendraio Flows that connect to our API.

And within Kendraio App they’ve built Kendraio Player, a proof-of-concept for a multi-service music streaming player using web monetisation technology, funded by Grant for the Web.

The timeframe is about 2 weeks — start any time from now. The bounty is $500 USD (paid out via https://opencollective.com/kendraio – so you need to have an account there to be paid – but that’s easy). Please answer their bounty by replying to their GitHub issue.

See how their first bounty went at Kendraio Player Audiotarky integration. And see Radhy’s writeup of his experience at Afterthought on integrating Audiotarky API into Kendraio App.

MusicBrainz Server update, 2021-06-14

This week we spent some time looking through code that had been sitting for a long time waiting for a review while we worked on all sorts of other things. Most of the changes are small – one that might be more noticeable is that on recording lists you can now see the release groups the recording appears on. This should make it easier to figure out what is going on when a list has many recordings with the same name.

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 yyoung for fixing a display bug with external links. Thanks to chaban, HibiscusKazeneko, Ian Tresman, Jeluang, otringal and salo.rock for having reported bugs and suggested improvements. Thanks to ffff23 and salo.rock for updating the translations. And thanks to all others who tested the beta version!

The git tag is v-2021-06-14.

Fixed Bug

  • [MBS-11371] – JSON-LD “member” returns “1991-1992” only for “1991-1992, 2000-present”
  • [MBS-11440] – Subscribers page for private collection is not private
  • [MBS-11638] – Work form allows adding duplicate work attributes
  • [MBS-11639] – Changing work attribute type always keeps the old value
  • [MBS-11640] – Errors never shown for work attribute fields with fixed values
  • [MBS-11682] – Deadlock when entering edits
  • [MBS-11688] – The external link section will disappear once any link starts with //
  • [MBS-11700] – ISE when viewing “Remove disc ID” edit
  • [MBS-11702] – Disc ID: Same release displayed twice when moving disc-id

Improvement

  • [MBS-4826] – Display source release next to recordings
  • [MBS-10205] – Readd a link to the Data Removal Policy under the “About us” drop-down menu
  • [MBS-11293] – Report: streaming relationships in non-digital releases
  • [MBS-11337] – Always link to URL entity page and link on URL reports
  • [MBS-11609] – Show genre disambiguation on autocomplete dropdown
  • [MBS-11627] – Don’t show “delete” link for deleted editors
  • [MBS-11696] – Disallow Twitter documentation links

New Feature

  • [MBS-9098] – Add JSON-LD “memberOf” relationship to artists who are members of groups
  • [MBS-10107] – Add overview pages for relationship attributes
  • [MBS-11290] – Report of works with a type which are part of a work with the same type
  • [MBS-11305] – Report for erroneous looking trailing join phrases

React Conversion Task

  • [MBS-10997] – Convert /search/error files to React
  • [MBS-11326] – Convert edit/notes.tt to React
  • [MBS-11430] – Convert format_setlist to Javascript

Other Task

  • [MBS-11330] – Split root/types.js into smaller files
  • [MBS-11553] – Move from passing $c to using React.useContext in layout pages

Picard 2.6.3 released

Picard 2.6.3 is the third maintenance release for the recently release Picard 2.6. It contains a couple of bug fixes, most notably it fixes a bug where changes to some options did not get applied until a restart of Picard. Users of Picard 2.6 are highly recommended to update.

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

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

What’s new?

Bugfixes

  • [PICARD-2205] – Syntax highlighting ignores functions starting with underscore or numbers
  • [PICARD-2206] – Fix tab order in option pages
  • [PICARD-2209] – Minimizing / maximizing Picard window registers desktop status indicator multiple times
  • [PICARD-2214] – Backslash at end of script raises TypeError
  • [PICARD-2219] – Empty file naming script causes files to be renamed to _ext
  • [PICARD-2226] – Some config changes are not applied until restart