# 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:** 1
**Showing post:** 4

<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.

---

_[View the full topic](https://community.mp3tag.de/t/musicbrainz-screwed-up-result/56991)._