# MusicBrainz Recording IDs erroneously written to MusicBrainz Track IDs

**URL:** https://community.mp3tag.de/t/musicbrainz-recording-ids-erroneously-written-to-musicbrainz-track-ids/44233
**Category:** Support
**Created:** [January 18, 2019, 5:17pm UTC](https://community.mp3tag.de/t/musicbrainz-recording-ids-erroneously-written-to-musicbrainz-track-ids/44233 "2019-01-18T17:17:13Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [January 18, 2019, 8:24pm UTC](https://community.mp3tag.de/t/musicbrainz-recording-ids-erroneously-written-to-musicbrainz-track-ids/44233/2 "2019-01-18T20:24:56Z")

</div>

The definitive source for lookup of Picard tag field names is [https://picard.musicbrainz.org/docs/mappings/](https://picard.musicbrainz.org/docs/mappings/)

From there it becomes clear, that what you refer to as _bug2_ above is intended behavior: what's displayed as "MusicBrainz Recording Id" in Picard is in fact written as `UFID://musicbrainz.org` (or `MUSICBRAINZ_TRACKID` for non-ID3v2 tagging formats).

In Mp3tag it's simply `MUSICBRAINZ_TRACKID` as listed in the overview table at [Add mappings for more MusicBrainz tags](https://community.mp3tag.de/t/add-mappings-for-more-musicbrainz-tags/43846/9?u=florian)

Let me know if I'm missing something, so far I don't see an issue.

---

_[View the full topic](https://community.mp3tag.de/t/musicbrainz-recording-ids-erroneously-written-to-musicbrainz-track-ids/44233)._