# \[F\] ID3v2.4 multi-values not always fully read when character size is 16

**URL:** https://community.mp3tag.de/t/f-id3v2-4-multi-values-not-always-fully-read-when-character-size-is-16/15081
**Category:** Fixed Bugs
**Tags:** bug-fixed
**Created:** [October 5, 2013, 7:14pm UTC](https://community.mp3tag.de/t/f-id3v2-4-multi-values-not-always-fully-read-when-character-size-is-16/15081 "2013-10-05T19:14:36Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![yindesu](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/y/b77776/32.png) [@yindesu](https://community.mp3tag.de/u/yindesu)
#### Post date: [October 5, 2013, 7:14pm UTC](https://community.mp3tag.de/t/f-id3v2-4-multi-values-not-always-fully-read-when-character-size-is-16/15081/1 "2013-10-05T19:14:36Z")

</div>

While testing TagLib, I produced another file which isn't fully compatible with Mp3tag. (I made sure this one is reproduceable.)

I tried to save 3 values into Artist (TPE1) and Artist Sort (TSOP).

The results are strange:

- Mp3tag only reads 2/3 of TPE1 (Artist)
- Mp3tag reads all 3/3 of TSOP (Artist Sort)
- in comparison, foobar2000 reads all 3/3 of both TPE1 and TSOP

TagLib writes the characters to both tag frames with a size of **16 bits**. When trying the same thing with Mp3tag on the original file, I noticed Mp3tag writes the characters with a size of 8 bits.

I suppose the character encoding is the cause of the incompatibility?

I have just sent a link to the file to the support email.

---

<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 5, 2013, 8:39pm UTC](https://community.mp3tag.de/t/f-id3v2-4-multi-values-not-always-fully-read-when-character-size-is-16/15081/2 "2013-10-05T20:39:31Z")

</div>

Thanks for the example file.

It seems that the last string in the TPE1 frame is not terminated by a null character.

Can you verify?

---

<div class="post-metadata">

### Author: ![yindesu](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/y/b77776/32.png) [@yindesu](https://community.mp3tag.de/u/yindesu)
#### Post date: [October 5, 2013, 11:00pm UTC](https://community.mp3tag.de/t/f-id3v2-4-multi-values-not-always-fully-read-when-character-size-is-16/15081/3 "2013-10-05T23:00:30Z")

</div>

That is probably an intentional decision by the devs then.  
[https://bugs.kde.org/show\_bug.cgi?id=149468](https://bugs.kde.org/show_bug.cgi?id=149468)

I can't verify what the spec is supposed to be.

---

<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 6, 2013, 8:28am UTC](https://community.mp3tag.de/t/f-id3v2-4-multi-values-not-always-fully-read-when-character-size-is-16/15081/4 "2013-10-06T08:28:08Z")

</div>

I had a further look at the file and there was indeed a bug in Mp3tag which is now fixed with Mp3tag v2.58.

Thanks for reporting!

Kind regards  
Florian

---

<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: [December 28, 2018, 2:06pm UTC](https://community.mp3tag.de/t/f-id3v2-4-multi-values-not-always-fully-read-when-character-size-is-16/15081/5 "2018-12-28T14:06:48Z")

</div>

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