# MusicBrainz: Screwed up result

**URL:** https://community.mp3tag.de/t/musicbrainz-screwed-up-result/56991
**Category:** Web Sources Discussion
**Created:** [April 8, 2022, 8:31am UTC](https://community.mp3tag.de/t/musicbrainz-screwed-up-result/56991 "2022-04-08T08:31:57Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![poster](https://community.mp3tag.de/user_avatar/community.mp3tag.de/poster/32/4881_2.png) [@poster](https://community.mp3tag.de/u/poster)
#### Post date: [April 8, 2022, 8:31am UTC](https://community.mp3tag.de/t/musicbrainz-screwed-up-result/56991/1 "2022-04-08T08:31:57Z")

</div>

The result for ALBUMARTIST for these releases is screwed up:

[https://musicbrainz.org/release/f72ffee7-fff1-4d93-acde-1b7bae2322c5](https://musicbrainz.org/release/f72ffee7-fff1-4d93-acde-1b7bae2322c5)  
[https://musicbrainz.org/release/506aeadb-2e51-4ac7-84bf-bf9171298168](https://musicbrainz.org/release/506aeadb-2e51-4ac7-84bf-bf9171298168)

Is it the fault of the script or a faulty source?

---

<div class="post-metadata">

### Author: ![Romano](https://community.mp3tag.de/user_avatar/community.mp3tag.de/romano/32/7465_2.png) [@Romano](https://community.mp3tag.de/u/Romano)
#### Post date: [April 8, 2022, 9:27am UTC](https://community.mp3tag.de/t/musicbrainz-screwed-up-result/56991/2 "2022-04-08T09:27:28Z")

</div>

This is a question of the script, if you use the expanded version(LyricsLover version) the album artist is correct. maybe they change the html or this is a rare version.

---

<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: [April 8, 2022, 10:30am UTC](https://community.mp3tag.de/t/musicbrainz-screwed-up-result/56991/3 "2022-04-08T10:30:35Z")

</div>

[My expanded script](https://community.mp3tag.de/t/ws-musicbrainz-expanded/55909) version is using the JSON answer format from MusicBrainz. The official MusicBrainz script is using the HTML answer format.

As @Romano already wrote, it could be that something has changed in one of the recent MB server updates displaying the HTML answer.

I'm not sure, but It could also be that this is caused by the displayed release artist name which differs from its current name "Ron Wood" and disambuigation:

 ![image](https://community.mp3tag.de/uploads/default/original/2X/e/ed3c5600669899aa1721106cf2893e33652dbfad.png)

 ![image](https://community.mp3tag.de/uploads/default/original/2X/6/6d82eccfe992297ec2458faa7191baccc4702342.png)

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [April 13, 2022, 9:45am UTC](https://community.mp3tag.de/t/musicbrainz-screwed-up-result/56991/4 "2022-04-13T09:45:05Z")

</div>

It should be fixed with [Mp3tag v3.14b](https://community.mp3tag.de/t/455) and I'm thinking about switching to JSON too. The more optional elements the API gets, the more complex it gets to parse the XML structure.