I believe that your problem is due to this part of the spec you linked to:
Frames that allow different types of text encoding contains a text encoding description byte. Possible encodings:
- $00
- ISO-8859-1 [ISO-8859-1]. Terminated with $00.
- $01
- UTF-16 [UTF-16] encoded Unicode [UNICODE] with BOM. All strings in the same frame SHALL have the same byteorder. Terminated with $00 00.
- $02
- UTF-16BE [UTF-16] encoded Unicode [UNICODE] without BOM. Terminated with $00 00.
- $03
- UTF-8 [UTF-8] encoded Unicode [UNICODE]. Terminated with $00.
You don't notice that your "read" program is sending the "\0" byte at the front of such values.
- tye
In reply to Re: ID3 tag version 2.4.0 Pack and Unpack (text encoding byte)
by tye
in thread ID3 tag version 2.4.0 Pack and Unpack
by thanos1983
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |