# 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:** 3
**Page:** 1

<div class="post-metadata">

### Author: ![mr\_bug](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/3bc359/32.png) [@mr\_bug](https://community.mp3tag.de/u/mr_bug)
#### Post date: [January 18, 2019, 5:17pm UTC](https://community.mp3tag.de/t/musicbrainz-recording-ids-erroneously-written-to-musicbrainz-track-ids/44233/1 "2019-01-18T17:17:13Z")

</div>

Likely not a bug, see edit below.

Hello,

When using the MusicBrainz Tag Sources option, after selecting a result and clicking Next, the list of IDs shown on the left panel are all Recording IDs _not_ Track IDs as the column header states (bug1). I'm not sure which ID type is meant to be displayed next to each song on the left, but for certain, those IDs aren't Track IDs.

When saving these suggested tags, these Recording IDs are mistakenly being written to MUSICBRAINZ\_TRACKID instead of MUSICBRAINZ\_RECORDINGID (bug2).

When viewing a release on MusicBrainz (e.g. [this](https://musicbrainz.org/release/55ab4d65-6cac-499f-927a-21e088c98e5f)), the Track ID can be found by clicking the track number, and the Recording ID can be found by clicking on the song title.

Hopefully I'm not misunderstanding things here,  
Thanks.

Source: [https://picard.musicbrainz.org/docs/tags/](https://picard.musicbrainz.org/docs/tags/)  
Version: 2.91 stable (current dev build doesn't list any relevant changes)

* * *

So after some more investigation, bug1 is not a bug. Most of the confusion I'm having here is is that Mp3Tag and Picard call these fields different things on the surface but it looks like they're handled correctly under the hood. The lesson here seems to be to not enter MusicBrainz ID manually and trust the software is doing it correctly because the fields are being displayed as one thing and being written as another. Examples (assuming all mentioned tags are prefixed with MUSICBRAINZ\_):

On the MusicBrainz site, recordings (i.e. the hyperlinked titles on a release), are referred to as TRACKIDs in Mp3Tag but as RECORDINGIDs in Picard, but both actually write to TRACKID. Again on the site, tracks (i.e. the hyperlinked track numbers on a release), are referred to as RELEASETRACKIDs in Mp3Tag but as TRACKID in Picard, but both actually write to RELEASETRACKID.

I wish tagging was more standardised and transparent.to avoid such confusions.

---

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

---

<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: [July 28, 2020, 12:15pm UTC](https://community.mp3tag.de/t/musicbrainz-recording-ids-erroneously-written-to-musicbrainz-track-ids/44233/3 "2020-07-28T12:15:43Z")

</div>

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