In Next Release
Here we have an example that only has a Wav Info chunk, and the fields are encoded as CPC-932. So if we run a Status Report on the file we end up with this garbled information. So it identifies an Album, Artist, Genre and Title but is misreading the metadata value because being read as if encoded as ISO-8859-1.
If we now run Fix Charset Encoding and specify these fields and the correct encoding as follows
we now get
The field metadata have been read correctly, then we write them to an ID3 chunk encoded as UTF-8 so can be read nomally without problem, we also create a SongKong Id field so we know file has been processed by SongKong.
If we then rerun Status Report it can now read the metadata correctly because the ID3 chunk is preferred over the old List Info Chunk, and the ID3 chunk has been written in the standard way using UTF-8 as required to write the Japanese script.
