# Show raw tag data in Extended Fields \[Request\]

**URL:** https://community.mp3tag.de/t/show-raw-tag-data-in-extended-fields-request/60942
**Category:** Mac
**Created:** [May 11, 2023, 11:39pm UTC](https://community.mp3tag.de/t/show-raw-tag-data-in-extended-fields-request/60942 "2023-05-11T23:39:20Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [May 12, 2023, 5:39am UTC](https://community.mp3tag.de/t/show-raw-tag-data-in-extended-fields-request/60942/2 "2023-05-12T05:39:25Z")

</div>

I think that the basic design of MP3tag will not be the best to implement this.  
As you can treat more or less any tag version (wav, flac, V1, V2.3, V2.4 mp4 etc.) and any file type (ogg, flac, wav, mp3, mp4 etc.) the read data has always to be mapped to an internal representation.

> [@knowle](#):
>
> The only way I have found to fix this metadata issue is to use the "Remove Tag" feature in Mp3tag 2–3 times to remove all fields and then add everything back manually.

If this is the case: which of your other program stacked tags on top of each other? Such a treatment of files is definitely the wrong way.

> [@knowle](#):
>
> Mp3tag selects the first, `music-metadata` selects the last).

Where do you see this display?  
Have you checked the extended tags dialogue to see how many fields there are?

> [@knowle](#):
>
> That is, I don't know if this MP3 file can be considered corrupt or not.

Here are links to some utilities to check files for corruption:

> [@How to check files for errors?](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633):
>
> It’s required and often helps to reduce support cycles to check files for errors before filing a bug report. Symptoms of erroneous files are often missing or wrong bitrate or length audible blips or skips tags seem to be sticky and cannot be removed There are some really good tools to check the files for errors, namely MP3 Diags — identifies many different issues in MP3 files Website: [http://mp3diags.sourceforge.net](http://mp3diags.sourceforge.net) Download: [MP3 Diags - Getting MP3 Diags](http://mp3diags.sourceforge.net/010_getting_the_program.html#binWindows) If the font size in MP3 Diags is …

AFAIK the case of a tag field name should not matter.

> [@knowle](#):
>
> For what it's worth, the "Extended Tags" window currently gives a false impression of being a list of every metadata field in the file, but this isn't the case.

In a way you are right that subordinate tag data is not shown. Priority of tags when read is:  
APE\>V2\>V1.  
But you see which tag version is now the one with priority in the dialogue title of the extended tags dialogue of a single file or the corresponding column of the default shipment.  
If would be intersting to see such problematic file and then find a way to deal with it with the current functions.

---

_[View the full topic](https://community.mp3tag.de/t/show-raw-tag-data-in-extended-fields-request/60942)._