Multiple album artists

Hello,

About this album:

Here is what I got in picard:


I would expect the album artist field to be multi values, to properly associate each AlbumArtistMBID with the correct name.
Is that the expected behavior?

Regards,

That’s intentional. The album artist of that album really is " Burial + Blackdown" (with + being the join phrase in MB). You can find the name of each album artist in the multivalued ~albumartists tag (should have the order as they appear in the artist credit). ~albumartists_sort provides the same as ~albumartists, but sorted by name. You can set the albumartist tag to just the list of artist names with a tagger script: $set(albumartist,$join(%_albumartists%,:,)) (replace : with the separator of your choice).

2 Likes

Thanks for your answer!
It looks like similar to the artist/artists tags, but I can’t see picard filling the albumartists tag? I can only see albumartist?

Does “I can’t see” mean that you’re checking the metadata box at the bottom (what’s shown in your screenshot?). If so, then that’s - again - intentional :slight_smile: All tags whose name begin with _ (~ in plugins) are not shown in that box and are not saved to files (more details in the docs).

You can view them if you install the “View script variables” plugin, then right-click on a track, Plugins → View Script Variables.

1 Like

Ah, that explains why I can’t see these tags using taglib or ffprobe.
Well, do I really have to parse the : separator of the albumartist tag to extract both names? There is no standard way to expose multiple values for album artists?

Side note, I see this kodi recommendation: https://kodi.wiki/view/Music_tagging#albumartists

You can do what is recommended on that page:

$setmulti(albumartists,%_albumartists%)

That’s exactly how you’ll set a multi value albumartists tag.

2 Likes

Yes indeed, but why is it not done by default by Picard?

Picard already writes quite a lot of tags, I don’t think that adding yet another non-standard tag with very specific need is such a good idea. That’s why Picard is configurable, to allow for such things.

1 Like

You can open a ticket asking for this tag to be populated by default, explaining which apps are using it, and why it should be set by default.
As said, that’s a non-standard tag.

3 Likes

Well I wanted to open a ticket but I found this: https://tickets.metabrainz.org/browse/PICARD-700
and the related review https://github.com/metabrainz/picard/pull/553
Seems to be just closed/rejected.
What is the status on this?

2 Likes

Side question but related: do you know where I can find an official “grammar” used by join phrases?
I see there are a lot of possible join phrases and quirks in https://wiki.musicbrainz.org/Style/Artist_Credits

  • " + "
  • " med "
  • ", "
  • " and "
  • " feat. "
  • " featuring "
  • " featuring XX,YY,ZZ" etc.
  • " / "
  • " with the "

All these join phrases make me think an “albumartists” tag should really be provided by picard by default

2 Likes

+1 for Picard writing ‘albumartists’ by default.
To me it’s an essential and very useful feature.

5 Likes

I guess no acceptable consensus was found by the time. You should ask in ticket.
@outsidecontext : what do you think?

1 Like

No strong opinion really. I guess having albumartists would make it consistent with artists, and if there exists an actual use case with Kodi I guess it is only consequential to add this tag. As far as I remember Kodi was also one of the primary factors for artists.

We should have a migration to update existing scripts.

My only concern is that this could get kind of out of hands. Idon’t think Picard should add every imaginable information to tags by default. Unless there is a clear use case or common standard I’m more in favor to making the data available and let the users decide what to do with it.

But if someone wants to revert the change a script like this would do:

$setmulti(_albumartists,%albumartists%)
$delete(albumartists)

I personally do this for the artists tag.

2 Likes

Well I am about to instruct my own soft (https://github.com/epoupon/lms) to do the same as Kodi.
What annoys me most is that there is no easy fallback on parsing “albumartist” to extract multiple artists since the MB join phrases do not seem to be standardized.
I do agree with you it could get out of control (maybe someone will ask to do the same for composers, remixers, mixers, producers, lyricists, etc.) but albumartists (and even albumartistssort) seems to be a reasonable minimum

That tag is used for display by players. If something is credited to “Neil Young with Crazy Horse” I’d like my player to show this, and not just a bookkeeping list of artist names :smiley: If you prefer plain lists you already can set $set(albumartist,%_albumartists%). You can even set it to a multi-value tag with $setmulti(albumartist,%_albumartists%), if the player supports that.

Yes indeed, but ideally I want to make every artist clickable in this field, as it is displayed on MB :blush:

1 Like

Just curious, who for you is the albumartist for releases such as these?:


I don’t know, I’m not familiar with any of those.