# Add mappings for more MusicBrainz tags

**URL:** https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846
**Category:** Support
**Created:** [December 11, 2018, 11:55am UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846 "2018-12-11T11:55:57Z")
**Posts on this page:** 14
**Page:** 1

<div class="post-metadata">

### Author: ![culinko](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/dc4da7/32.png) [@culinko](https://community.mp3tag.de/u/culinko)
#### Post date: [December 11, 2018, 11:55am UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/1 "2018-12-11T11:55:57Z")

</div>

In v2.89 you did the following change:

> [2018-06-04] CHG: added mappings for special fields with MusicBrainz IDs for ID3v2 and MP4. (#18405)

Can I ask if you could add more mappings of MusicBrainz fields? The following fields would need to be changed from

TXXX:ACOUSTID ID  
TXXX:MUSICBRAINZ ALBUM RELEASE COUNTRY  
TXXX:MUSICBRAINZ ALBUM STATUS  
TXXX:MUSICBRAINZ ALBUM TYPE

into

TXXX:Acoustid Id  
TXXX:MusicBrainz Album Release Country  
TXXX:MusicBrainz Album Status  
TXXX:MusicBrainz Album Type

and also changed in the extended tags **display** into

ACOUSTID\_ID  
MUSICBRAINZ\_ALBUMRELEASECOUNTRY  
MUSICBRAINZ\_ALBUMSTATUS  
MUSICBRAINZ\_ALBUMTYPE

I'm using ID3v2.4 UTF-8 setting. Thanks so much for implementing this, greatly appreciated!

---

<div class="post-metadata">

### Author: ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)
#### Post date: [December 11, 2018, 12:54pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/2 "2018-12-11T12:54:27Z")

</div>

As far as I understand the user-defined fields (that start with TXXX) the name of that field is set during creation.  
So

> [@culinko](#):
>
> TXXX:ACOUSTID ID

and

> [@culinko](#):
>
> ACOUSTID\_ID

would actually be 2 different fields.  
If you want to map these, see File\>Options\>Tags\>Mapping

---

<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: [December 11, 2018, 1:00pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/3 "2018-12-11T13:00:54Z")

</div>

@culinko

Are you sure about this?  
In [your other thread](https://community.mp3tag.de/t/some-txxx-tags-are-written-in-lowercase/43847) you ask to write tags in all uppercase, but here, you ask for some kind of "title case"?

What's the difference between this MusicBrainz tags and TXXX tags in general?

---

<div class="post-metadata">

### Author: ![culinko](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/dc4da7/32.png) [@culinko](https://community.mp3tag.de/u/culinko)
#### Post date: [December 11, 2018, 1:08pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/4 "2018-12-11T13:08:16Z")

</div>

I probably confused you with the Extended tags bit, I just mean for display purposes. I added the "display" word into my initial post.

What I mean is that after MusicBrainz tags got their special mixed case mappings in Mp3Tag v2.89, they are displayed in all caps and with underscores in Extended Tags, so I just wanted the 4 tags that I mentioned to be displayed the same way so it would be consistent for all MusicBrainz tags (yes, AcoustID is also a MusicBrainz tag, I asked a current Picard dev about that).

What I mean is this: [https://i.imgur.com/KZ7LZkf.png](https://i.imgur.com/KZ7LZkf.png), you can see the missing underscores not being displayed for the tags there. Also I'm not sure about whether they should be displayed as MUSICBRAINZ\_ALBUM\_RELEASE\_COUNTRY or MUSICBRAINZ\_ALBUMRELEASECOUNTRY, but I think Florian named the current tags so he can decide how they should be named. Anyway the Extended Tags display is not that big of a deal, I just like things to be consistent and couldn't not notice this 🙂

---

<div class="post-metadata">

### Author: ![phw](https://community.mp3tag.de/user_avatar/community.mp3tag.de/phw/32/11831_2.png) [@phw](https://community.mp3tag.de/u/phw)
#### Post date: [December 11, 2018, 1:33pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/5 "2018-12-11T13:33:56Z")

</div>

> [@LyricsLover](#):
>
> What's the difference between this MusicBrainz tags and TXXX tags in general?

I think this is similar to what was already changed for other MusicBrainz defined tags like `MusicBrainz Artist Id`. These are specifically defined tags with a specific meaning, and their casing should be preserved. MP3Tag already contains a fixed mapping of most of those tags, but not for the ones @culinko mentioned above. See also this older discussion:

> [@Problem when entering MusicBrainz IDs (e.g., MusicBrainz Artist ID)](https://community.mp3tag.de/t/problem-when-entering-musicbrainz-ids-e-g-musicbrainz-artist-id/43258/2):
>
> This is due to a change in v2.89 for the internal mapping of MusicBrainz IDs [2018-06-04] CHG: added mappings for special fields with MusicBrainz IDs for ID3v2 and MP4. ([#18405](https://community.mp3tag.de/t/18405)) With this change, I've added an mapping from internal (written to the tag) to external (displayed in Mp3tag) representation of the MusicBrainz ID fields. This was necessary, because other applications (e.g., MusicBrainz Picard) or libraries (e.g., TagLib) are using different names for those identifiers depending on t…

---

<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: [December 11, 2018, 2:52pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/6 "2018-12-11T14:52:07Z")

</div>

Yes, I'll add them to the next release. Thanks for pointing.

---

<div class="post-metadata">

### Author: ![culinko](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/dc4da7/32.png) [@culinko](https://community.mp3tag.de/u/culinko)
#### Post date: [December 11, 2018, 3:09pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/7 "2018-12-11T15:09:31Z")

</div>

Thank you for addressing this, much appreciated!

---

<div class="post-metadata">

### Author: ![paultaylor](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/p/5fc32e/32.png) [@paultaylor](https://community.mp3tag.de/u/paultaylor)
#### Post date: [December 11, 2018, 5:51pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/8 "2018-12-11T17:51:29Z")

</div>

Hi Florian,

Jaikoz/SongKong developer here. We have a nice spreadsheet that we share with phw that keeps mappings for different formats for Picard/Jaikoz/SongKong. We really like to try and keep compatible with other tagger applications like Mp3tag so I share with you hoping it will be useful to you [https://docs.google.com/spreadsheets/d/1afugW3R1FRDN-mwt5SQLY4R7aLAu3RqzjN3pR1497Ok/edit?usp=sharing](https://docs.google.com/spreadsheets/d/1afugW3R1FRDN-mwt5SQLY4R7aLAu3RqzjN3pR1497Ok/edit?usp=sharing) and will help to improve compatability between applications.

---

<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: [December 16, 2018, 12:51pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/9 "2018-12-16T12:51:23Z")

</div>

As of [Mp3tag v2.91a](https://community.mp3tag.de/t/455), Mp3tag maps the following fields specific to MusicBrainz:

| MusicBrainz | Mp3tag |
| --- | --- |
| Acoustid Id | ACOUSTID\_ID |
| Acoustid Fingerprint | ACOUSTID\_FINGERPRINT |
| MusicBrainz Album Id | MUSICBRAINZ\_ALBUMID |
| MusicBrainz Album Release Country | MUSICBRAINZ\_ALBUMRELEASECOUNTRY |
| MusicBrainz Album Status | MUSICBRAINZ\_ALBUMSTATUS |
| MusicBrainz Album Type | MUSICBRAINZ\_ALBUMTYPE |
| MusicBrainz Artist Id | MUSICBRAINZ\_ARTISTID |
| MusicBrainz Album Artist Id | MUSICBRAINZ\_ALBUMARTISTID |
| MusicBrainz Original Album Id | MUSICBRAINZ\_ORIGINALALBUMID |
| MusicBrainz Original Artist Id | MUSICBRAINZ\_ORIGINALARTISTID |
| MusicBrainz Release Group Id | MUSICBRAINZ\_RELEASEGROUPID |
| MusicBrainz Release Track Id | MUSICBRAINZ\_RELEASETRACKID |
| MusicBrainz Work Id | MUSICBRAINZ\_WORKID |
| MusicBrainz TRM Id | MUSICBRAINZ\_TRMID |
| `UFID://musicbrainz.org` | MUSICBRAINZ\_TRACKID |
| MusicBrainz Disc Id | MUSICBRAINZ\_DISCID |

---

<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: [December 17, 2018, 8:54am UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/10 "2018-12-17T08:54:43Z")

</div>

> [@Florian](#):
>
> ACOUSTID\_ID  
> ACOUSTID\_FINGERPRINT

Thanks for this change @Florian.  
Can it be, that the first two fields are not yet listed in "Erweiterte Felder"?

---

<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: [December 17, 2018, 9:22am UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/11 "2018-12-17T09:22:42Z")

</div>

> [@LyricsLover](#):
>
> Can it be, that the first two fields are not yet listed in "Erweiterte Felder"?

Yes, thanks for pointing. I'll add them to the next release.

---

<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: [December 22, 2018, 12:37pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/12 "2018-12-22T12:37:57Z")

</div>

I've added the fields to the extended fields list with [Mp3tag v2.91b](https://community.mp3tag.de/t/455).

---

<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: [December 31, 2018, 12:04pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/13 "2018-12-31T12:04:54Z")

</div>

A post was split to a new topic: [Add field mapping for MusicBrainz Picard](https://community.mp3tag.de/t/add-field-mapping-for-musicbrainz-picard/44062)

---

<div class="post-metadata">

### Author: ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)
#### Post date: [January 30, 2019, 12:04pm UTC](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/14 "2019-01-30T12:04:55Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
