# MP3TAG messing up with MP3 comments tag when editing

**URL:** https://community.mp3tag.de/t/mp3tag-messing-up-with-mp3-comments-tag-when-editing/57125
**Category:** Support
**Created:** [April 24, 2022, 10:08pm UTC](https://community.mp3tag.de/t/mp3tag-messing-up-with-mp3-comments-tag-when-editing/57125 "2022-04-24T22:08:19Z")
**Posts on this page:** 1
**Showing post:** 34

<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: [April 26, 2022, 5:29am UTC](https://community.mp3tag.de/t/mp3tag-messing-up-with-mp3-comments-tag-when-editing/57125/34 "2022-04-26T05:29:22Z")

</div>

> [@Loud3r](#):
>
> Is there really two comments on both files or MP3TAG thinks there's two comments in each file?

There are 2 comment fields - even MP3diags shows 2 fields COMM, each with the size 6 for the file exported by Audacity.  
Yet, for the files exported by Audacity, the first COMM field has no language token, whereas the second field has the languge token XXX.  
Editing the file with MP3tag changes both to ENG.  
 ![grafik](https://community.mp3tag.de/uploads/default/original/2X/4/45843038d1e1224911458852715520d1ef85076a.png)

So, my

> [@Loud3r](#):
>
> Conclusion: editing comment value using

Audacity causes problems.  
If your windows does not display the comments at all, check if ENG is the best setting or whether XXX would be better.

---

_[View the full topic](https://community.mp3tag.de/t/mp3tag-messing-up-with-mp3-comments-tag-when-editing/57125)._