# Replaygain doesn't work with ID3v2.3 UTF-16 and VLC

**URL:** https://community.mp3tag.de/t/replaygain-doesnt-work-with-id3v2-3-utf-16-and-vlc/66146
**Category:** Support
**Tags:** player
**Created:** [October 4, 2024, 4:15am UTC](https://community.mp3tag.de/t/replaygain-doesnt-work-with-id3v2-3-utf-16-and-vlc/66146 "2024-10-04T04:15:08Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![bob.knight](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/b/b3f665/32.png) [@bob.knight](https://community.mp3tag.de/u/bob.knight)
#### Post date: [October 4, 2024, 4:15am UTC](https://community.mp3tag.de/t/replaygain-doesnt-work-with-id3v2-3-utf-16-and-vlc/66146/1 "2024-10-04T04:15:08Z")

</div>

Hi,  
I was trying to setup %replaygain\_track\_gain% in mp3 files and I found that it works using APE tags and ID3v2.4 (UTF8) but not when using id3v2.3 (UTF16), at least with VLC player.  
Why is this happening? A problem with mp3tag saving the tag?

Column:  
value: %REPLAYGAIN\_TRACK\_GAIN%  
field: %REPLAYGAIN\_TRACK\_GAIN%

Comment: values are saved numerically, without "db" at the end. As already said, it doesn't work with UTF16.

Thanks

---

<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: [October 4, 2024, 5:54am UTC](https://community.mp3tag.de/t/replaygain-doesnt-work-with-id3v2-3-utf-16-and-vlc/66146/2 "2024-10-04T05:54:10Z")

</div>

see here for the general problem of out-of-sync APE tags and ID3V2.x tags

> [@Tags not shown or updated](https://community.mp3tag.de/t/tags-not-shown-or-updated/49431):
>
> Trying 3.01 and 3.01a (beta). Neither is showing tags or allowing them to be edited. I can send a sample mp3 if needed. I'd send a screenshot, but not sure how to do that in this forum...

---

<div class="post-metadata">

### Author: ![garym](https://community.mp3tag.de/user_avatar/community.mp3tag.de/garym/32/4822_2.png) [@garym](https://community.mp3tag.de/u/garym)
#### Post date: [October 5, 2024, 2:12pm UTC](https://community.mp3tag.de/t/replaygain-doesnt-work-with-id3v2-3-utf-16-and-vlc/66146/3 "2024-10-05T14:12:19Z")

</div>

I don't use APE tags at all. But for all my mp3 files, they are id3v2.3 (UTF16) and the replaygain (album and track) values work properly.

---

<div class="post-metadata">

### Author: ![MotleyG](https://community.mp3tag.de/user_avatar/community.mp3tag.de/motleyg/32/440_2.png) [@MotleyG](https://community.mp3tag.de/u/MotleyG)
#### Post date: [October 5, 2024, 2:41pm UTC](https://community.mp3tag.de/t/replaygain-doesnt-work-with-id3v2-3-utf-16-and-vlc/66146/4 "2024-10-05T14:41:50Z")

</div>

No issues with mp3 files here either. Id3v2.3 and id3v2.4 working done with track and album Replaygain tags.

---

<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: [October 10, 2024, 11:59am UTC](https://community.mp3tag.de/t/replaygain-doesnt-work-with-id3v2-3-utf-16-and-vlc/66146/5 "2024-10-10T11:59:43Z")

</div>

I've moved this to #Support due to lack of feedback from @bob.knight Thanks to everyone else for confirming that everything works as expected.

I've also checked that ReplayGain metadata fields of ID3v2.3 tagged files using UTF-16 are correctly displayed in the **Metadata** tab of VLC's file information sheet.

I don't know if VLC shows somewhere in its UI when ReplayGain is applied, so I wasn't able to verify this.

---

<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: [November 9, 2024, 12:00pm UTC](https://community.mp3tag.de/t/replaygain-doesnt-work-with-id3v2-3-utf-16-and-vlc/66146/6 "2024-11-09T12:00:42Z")

</div>

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