Track and album names displayed with replacement character. How to resolve?

[paultaylor]

(24-01-2024 17:49)simbun Wrote:  (although whilst I did realise 2.4 is NUL separated I didn't realise they were NUL teriminated)

Hi, you are correct they are not null-terminated just null separated (although there are some taggers that incorrectly null-terminate all strings)

e.g from spec for text information frames and the variant of TXXX frames

Quote:4.2. Text information frames

The text information frames are often the most important frames,
containing information like artist, album and more. There may only be
one text information frame of its kind in an tag. All text
information frames supports multiple strings, stored as a null
separated list, where null is reperesented by the termination code
for the charater encoding. All text frame identifiers begin with "T".
Only text frame identifiers begin with "T", with the exception of the
"TXXX" frame. All the text information frames have the following
format:

<Header for 'Text information frame', ID: "T000" - "TZZZ",
excluding "TXXX" described in 4.2.6.>
Text encoding $xx
Information <text string(s) according to encoding>



4.2.6. User defined text information frame

This frame is intended for one-string text information concerning the
audio file in a similar way to the other "T"-frames. The frame body
consists of a description of the string, represented as a terminated
string, followed by the actual string. There may be more than one
"TXXX" frame in each tag, but only one with the same description.

<Header for 'User defined text information frame', ID: "TXXX">
Text encoding $xx
Description <text string according to encoding> $00 (00)
Value <text string according to encoding>

Look at the definition of the Description field, if <text string according to encoding> was meant to include terminating byte(s) you would have it twice because it has been explicity defined in the definition.