# Mismatch on flac - MediaMonkey vs MP3TAG
**URL:** https://community.mp3tag.de/t/mismatch-on-flac-mediamonkey-vs-mp3tag/11497
**Category:** No Bugs
**Created:** [January 24, 2011, 7:21pm UTC](https://community.mp3tag.de/t/mismatch-on-flac-mediamonkey-vs-mp3tag/11497 "2011-01-24T19:21:57Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@markeh](https://community.mp3tag.de/u/markeh)
#### Post date: [January 24, 2011, 7:21pm UTC](https://community.mp3tag.de/t/mismatch-on-flac-mediamonkey-vs-mp3tag/11497/1 "2011-01-24T19:21:57Z")
There appears to be a mismatch between how MediaMonkey and MP3TAG handle custom fields on flac and mp3 files. Maybe others also, but I have only tested flac and mp3.
I don't know if this is actually a bug, or if it is, who owns it, so I'm posting this in both MediaMonkey and MP3TAG forums.
In MediaMonkey, the "real name" of the first custom field (for all files, apparently - both mp3 and flac) is **_SONGS-DB\_CUSTOM1_**. This appears in MP3TAG as an extended field - **_COMMENT SONGS-DB\_CUSTOM1_**.
In MP3TAG, the same field for a flac file appears as an extended filed with just _ **CUSTOM1** _.
I have no idea which is "correct," if either. I just want the applications to work together - which means that when I set the field in MP3TAG I would like the same value to appear in MediaMonkey. Of course, I can put _both_ values in the MP3TAG panel, and remember to set both, or set the correct one depending on which type of file I'm looking at. But I use several custom fields to help organize my music, and doing this all of the time would be a hassle.
thnx,
.
---
### Author:  [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [January 24, 2011, 7:58pm UTC](https://community.mp3tag.de/t/mismatch-on-flac-mediamonkey-vs-mp3tag/11497/2 "2011-01-24T19:58:22Z")
MM does not use the same kind of custom fields for these file formats so this is not a bug.
But you can configure Mp3tag to show both fields with the same name in the program.
At **File \> Options \> Tags \> Mapping** add
_ID3v2 | COMMENT SONGS-DB\_CUSTOM1 | Custom1_
Now for both mp3 and flac you can use the name _Custom1_ in Mp3tag.
---
### Author:  [@markeh](https://community.mp3tag.de/u/markeh)
#### Post date: [January 24, 2011, 11:02pm UTC](https://community.mp3tag.de/t/mismatch-on-flac-mediamonkey-vs-mp3tag/11497/3 "2011-01-24T23:02:14Z")
There apparently really are two different fields - in two different locations.
Does this mapping mean that a single update in mp3tab updates both fields??
A single update in MediaMonkey shows in both places??
thnx,
.
---
### Author:  [@dano](https://community.mp3tag.de/u/dano)
#### Post date: [January 25, 2011, 9:59am UTC](https://community.mp3tag.de/t/mismatch-on-flac-mediamonkey-vs-mp3tag/11497/4 "2011-01-25T09:59:31Z")
> [@](#):
>
> Does this mapping mean that a single update in mp3tab updates both fields??
It does not write two fields to one file but the "right" field to each file.
> [@](#):
>
> A single update in MediaMonkey shows in both places??
No, only in Custom1.
You have now one field in Mp3tag that works for both audio formats.
---
### Author:  [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:30pm UTC](https://community.mp3tag.de/t/mismatch-on-flac-mediamonkey-vs-mp3tag/11497/5 "2018-12-28T14:30:14Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.