# \[WS\] MusicBrainz expanded

**URL:** <https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909>\
**Category:** Web Sources Scripts\
**Created:** [January 15, 2022, 2:31pm UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909 "2022-01-15T14:31:34Z")\
**Posts on this page:** 11\
**Page:** 4

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [October 18, 2025, 11:13am UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/61 "2025-10-18T11:13:22Z")

</div>

Would you like to see all the "Recording Artist(s)" as highlighted in yellow in this screenshot?

 ![image](https://community.mp3tag.de/uploads/default/original/3X/9/a/9a5c66af9de0892402d70b7b05e2109ba69de246.png)  
If not, please tell me exactly what you mean by "Performers" and provide a specific example release MBID.

---

<div class="post-metadata">

**Author:** ![Fishie](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/f/7bcc69/32.png) [@Fishie](https://community.mp3tag.de/u/Fishie)\
**Post date:** [October 19, 2025, 7:04am UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/62 "2025-10-19T07:04:13Z")

</div>

Yes, that’s what I wanted to see.

The composer should go to the “composer” field instead of “artist” field.

---

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [October 19, 2025, 11:41am UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/63 "2025-10-19T11:41:30Z")

</div>

Thanks for your idea.

Unfortunately, this would no longer align with the primary objective outlined in [point #1](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909):

> Best possible compatibility to MusicBrainz official tagger "Picard"

As you can see in the official MusicBrainz Picard "George Bizet" is also identified as the ARTIST for this release.

 ![image](https://community.mp3tag.de/uploads/default/original/3X/7/a/7ab13a2a5a5fd5608d2a7288696a386f60280c8e.png)

Since version v2.00 of this script, I haven't processed the metadata at track-level anymore.  
Detailed information about recording artists can only be found there.

**Just as a technical hint:**  
To get "Patrick Criswell", "John McCarthy" and the 5 other recording artists for track #2, you would have to  
a) Loop through all 56 medias (aka "CDs") for this release  
b) On media #1/56: Loop through all 26 tracks  
c) On track #2/26: Loop through all recordings  
d) On recording #1: Loop through all 7 artist-credit  
e) On artist-credit #1: Read the artist name "Patrick Criswell" and maybe his disambiguation "Chorus master" and his country "GB"

For major releases such as the current 56 CD-Collection [111 Years of Deutsche Grammophon: The Collector's Edition 2](https://musicbrainz.org/release/6aff4c57-bf1a-4a95-90be-27d8428312db), the processing time increases up to one minute (without any cover art!) and the 32-bit version of Mp3tag results in this error:

 ![Not enough memory addressable](https://community.mp3tag.de/uploads/default/original/3X/d/9/d94528129848117e6d647719a1a776a337a8318c.png)

Technically speaking, a script could return a "combined artist credit" for [smaller](https://musicbrainz.org/release/4d285fd1-6985-4c7b-8492-8992ae01ecb1) releases like  
`Danilo Rigosa (Person, operatic bass)/Slovak Philharmonic Chorus (Choir, SK)/Slovak Radio Symphony Orchestra (Orchestra, SK)/Alexander Rahbari (Person, Ali Rahbari, often credited as “Alexander” Rahbari, IR)`

 ![Combined Artist-Credits](https://community.mp3tag.de/uploads/default/original/3X/d/e/ded0321d1340fe8d123840d32d833c88bce7fad5.png)

**In short:**  
Currently, I cannot change the script to meet your needs.

---

<div class="post-metadata">

**Author:** ![simbun](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/s/ee59a6/32.png) [@simbun](https://community.mp3tag.de/u/simbun)\
**Post date:** [March 10, 2026, 3:06pm UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/64 "2026-03-10T15:06:31Z")

</div>

New user with a few questions, so apologies if I’ve missed something obvious.

Is it possible to write multivalued tags instead of using / as a delmiter? I know I can split them using Actions but that feels a little clumsy?

Would it be posssible to pull %\_albumartists%, %\_albumartists\_sort% and %\_artists\_sort%?

---

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [March 10, 2026, 3:26pm UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/65 "2026-03-10T15:26:17Z")

</div>

Can you please provide an existing real example from MusicBrainz and show me, what field(s) exactly do you like to save as multivalue field?

And where do you see %\_albumartists%, %\_albumartists\_sort% and %\_artists\_sort% in the given MusicBrainz online example?

What exactly would the difference be compared to the existing `ALBUMARTIST`, `ALBUMARTISTSORT`, `ARTISTSORT`?

---

<div class="post-metadata">

**Author:** ![simbun](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/s/ee59a6/32.png) [@simbun](https://community.mp3tag.de/u/simbun)\
**Post date:** [March 10, 2026, 4:13pm UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/66 "2026-03-10T16:13:17Z")

</div>

> [@LyricsLover](#):
>
> Can you please provide an existing real example from MusicBrainz and show me, what field(s) exactly do you like to save as multivalue field?

Any tag that is multivalued really e.g. artists, musicbrainz\_albumartistid, musicbrainz\_artistid, musicbrainz\_albumtype.

> **[Who Believes in Angels?](https://musicbrainz.org/release/4c230d78-ace7-459c-8455-0fd04b3cb83c)**
>
> Official release by Elton John & Brandi Carlile, 2025-04-04
>   
> 10 total tracks (CD)

> [@LyricsLover](#):
>
> And where do you see %\_albumartists%, %\_albumartists\_sort% and %\_artists\_sort% in the given MusicBrainz online example?
> 
> What exactly would the difference be compared to the existing `ALBUMARTIST`, `ALBUMARTISTSORT`, `ARTISTSORT`?

The fields are available in Picard so I guess may not be available through the API; they’re the multivalued equivalents e.g.

ALBUMARTIST: Elton John & Brandi Carlile

\_ALBUMARTISTS: Elton John; Brandi Carlile

ALBUMARTISTSORT: John, Elton & Carlile, Brandi

\_ALBUMARTISTS\_SORT: John, Elton; Carlile, Brandi

NOTE: Using semicolon to denote a multivalued tag

---

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [March 10, 2026, 6:26pm UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/67 "2026-03-10T18:26:42Z")

</div>

Thank you for providing this additional information.  
Unfortunately, neither the `_fields` nor the saving of multivalue fields are planned for the near future.  
The effort required to add and maintain these rather specialized and user-defined fields is currently too high.

Of course you can copy my websource script code and adapt it to your needs.

Or you can use "MusicBrainz Picard" for these specific sort fields.  
AFAIK, MB Picard also supports multivalue fields, so you could implement both suggestions.

---

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [March 12, 2026, 2:32pm UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/68 "2026-03-12T14:32:49Z")

</div>

9 posts were split to a new topic: [Ways to fill sort fields for uPNP server](https://community.mp3tag.de/t/ways-to-fill-sort-fields-for-upnp-server/70862)

---

<div class="post-metadata">

**Author:** ![Casual\_Tea](https://community.mp3tag.de/user_avatar/community.mp3tag.de/casual_tea/32/18886_2.png) [@Casual\_Tea](https://community.mp3tag.de/u/Casual_Tea)\
**Post date:** [October 20, 2026, 10:19am UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/69 "2026-10-20T10:19:33Z")

</div>

Do web source scripts work differently via Wine on Linux? Ever since switching over I noticed that the `ARTIST` delimiters get repeated and even appended after the final artist. Also, for releases with more than one disc, the total part of the `DISCNUMBER` tag gains an appended `0` per disc. `1/3`, `2/30`, `3/300` and so on.

 ![testrelease](https://community.mp3tag.de/uploads/default/original/3X/7/7/77d472ed67c85be11cae212fe3214e51f3a76a93.png)

 ![settings](https://community.mp3tag.de/uploads/default/original/3X/0/e/0e46830bca47547ed1dab5378051fe9416996d36.png)

CachyOS  
wine-11.20  
Mp3tag v3.37-beta3  
MusicBrainz expanded v2.31  
[Testrelease](https://musicbrainz.org/release/143f1d30-0da7-4000-8dd6-3089dc1a29f0)

---

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [October 20, 2026, 11:04am UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/70 "2026-10-20T11:04:47Z")

</div>

> [@Casual\_Tea](#):
>
> Do web source scripts work differently via Wine on Linux?

AFAIK, they should work in the same way. But, to be honest, I only test my script on Windows.

As you can see, the problem also occurs on Windows:

 ![image](https://community.mp3tag.de/uploads/default/original/3X/d/4/d496cfdfe4e452ab83f14d1d157a9f7b11a11e4a.png)  
_(The yellow highlighted lines show the formatting that is almost correct...)_

The multiple ARTISTS (plural) seems to be filled correctly (separated with a slash `/`).

A quick check reveals that other multi-artist albums seem to be affected too:

 ![image](https://community.mp3tag.de/uploads/default/original/3X/7/5/75e8b46f593e64477001716c26912a35eb1ecd8f.png)

I'm not sure whether this is a long-standing undetected bug in the script, or if MusicBrainz has recently made a slight change to the format of the JSON result.

I'll check it and let you know. Just give me some time. 😉

---

<div class="post-metadata">

**Author:** ![LyricsLover](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/l/c6cbf5/32.png) [@LyricsLover](https://community.mp3tag.de/u/LyricsLover)\
**Post date:** [October 21, 2026, 6:44am UTC](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909/71 "2026-10-21T06:44:23Z")

</div>

2026-10-21 - Update v2.32 (Bugfix release)

- FIX: Multiple `ARTIST` entries now appear with the correct joinphrase (such as `,` or `&`) in the correct position (thanks to @Casual_Tea)
- FIX: The discnumber will no longer have an unwanted 0 appended to it for releases with more than one disc (thanks to @Casual_Tea)
- ADD: New variable `TOTALTRACKS_PER_MEDIUM` in the top right section. This variable contains the total number of tracks per medium, for example 14;21 (for a two-media release with 14 and 21 tracks). This feature can be enabled in the MusicBrainz expanded settings (as requested by @shyfx)

 ![image](https://community.mp3tag.de/uploads/default/original/3X/8/6/86934d57ceac9b6d7e1b49ac4909d72d3c868b86.png)

[Previous page](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909.md?page=3)
