Importing .cue sheet with Japanese characters (UTF-8)

Hello everyone! I have a problem with showing normal characters in Mp3tag if I am choosing to open .cue sheet that has UTF-8 coding.

I ripped CD disc with cue, log and single wav file.
Then I tried to split wav files with Medieval CUE Splitter, and it doesn't write any tags, just Track01.wav, Track02... etc. I renamed manually each file (it's annoying).
Then I need to apply track tags to all .wav files.

Instead of manually copying them each time in mp3tag, comparing to .cue sheet, I decided to open .cue sheet throught mp3tag and just copy tags and paste them into .wav files. But the problem that Japanese characters became terrible when mp3tag opened it, and .cue sheet is still UTF-8 file. What's wrong?

Is there way to make my life easier with applying tags in .wav files from CD?
Because manually pasting names, artists etc for each file is really exhausting. Thank you!

I attached screenshots of problem.

Which MP3tag version are you using?
Please note that V3.25

has some fixes in respect to UTF8:
[2024-02-03] FIX: writing UTF-8 encoded export files produced wrong 4-byte character encoding for some Unicode characters. (#63556)
[2024-02-02] FIX: writing UTF-8 encoded *.m3u8 playlists produced wrong 4-byte character encoding for some Unicode characters. (#63556)
[2024-02-02] FIX: error when reading UTF-8 encoded *.m3u8 playlists with Unicode characters encoded using 4-bytes.
I don't know, though, if these also apply to cue files.

If you still have the single .wav and .cue file, you might want to give CueTools a shot. That can often times fetch Metadata from MusicBrainz before splitting a single .wav/.flac + .cue file.
Also if you want a broader tag compatibility, split and encode to flac in the same step. Flac is also lossless but quite a bit smaller and more versatile than .wav.

Unfortunately, MusicBrainz don't have metadata for many CD I purchased (I often purchasing really rare Japanese music CD that doesn't included in any database etc).

Also, as I can see, WAV has problem with tags showing Japanese characters, unlike MP3.

I updated, and it still have the same problem, where I can report it to developer?

Скриншот 30-03-2024 140059

I tried this, maybe, I don't understand how it works, but it also doesn't write any tags automatically from .cue file. I still need to paste it manually through Mp3tag after splitting into separate .wav files.

Please upload the CUE file.
We can then investigate and experiment.

That's odd, in my experience you can either choose to tag and name the split files based on what's in the cue file or (if it finds the release) use musicbrainz tags. However I've never tried it with japanese characters.

Here it is.

What do you mean when you say "to open .cue sheet throught (sic) mp3tag" and "when mp3tag opened it"?
You might use a Mp3tag tool to open a CUE file with some text reader, but that is not the same as Mp3tag opening it.

I tested by importing the cue file into the COMMENTS field, using the "Import text file" action.
That produced incorrect characters, as you report.
Notepad shows the CUE file as ANSI encoded, so I was not surprised.
However, after I re-encoded the CUE file to UTF-8 (using Notepad++), the characters seem to appear correctly after importing the new file.
But I'm no expert about character encoding and I can't read Japanese.

Maybe the CUE file was produced improperly when attempting to show unicode characters.

In order to get the tag values from the CUE file, you may be able to parse it using Mp3tag functions after importing it into any desired field.
That is easier said than done!

My CUE files are always in UTF-8. Anyway, they still opens wrong in mp3tag. When I open .cue file on Notepad++, it shows it's UTF-8.

I just don't want to manually copy each tag name from .cue in Notepad++ to paste it manually in mp3tag.
It's so exhausting.

UPD.
I tried to change the file coding to UTF-8-BOM from UTF-8 in Notepad++, and this .cue finally opens normally in mp3tag, I don't know what's wrong, to be honest.

In my case, when I choose .cue file in UTF-8-BOM coding, CUEtools writes normally only name of files (not actual tags in file - name, artists, track no, year, etc) in output separated .wav files. So, I still need to use Mp3tag to open .cue sheet, copy all tags values, then open all .wav files in Mp3tag and paste values, saving them, and only then it all works.

Not the one you uploaded, at least not according to Notepad++.

CueTools will populate tag fields if you split a WAV file into FLAC or MP3 (and probably others).
I suspect it does not, when producing WAV files, because there are very few applications that support tags in WAV files.
If tags for audio files are important to you, another lossless file type (FLAC or WavPack or ALAC) is better suited.

If you don't want to parse a cue file, but still use WAV audio, then you could use CueTools to create both MP3 and WAV files and then use Mp3tag to copy tags from the MP3s to the WAVs.

And it is still unclear how you open a cue file in Mp3tag.

I just drag and drop .cue file onto MP3tag interface. I don't know how I can open it otherwise.

Thanks for advices anyway.
I still don't know why UTF-8 .cue files doesn't supports, but I will try to attach normal UTF-8 file later.

I am pleasantly surprised that Mp3tag can expand a CUE file to create lines in the file list that contain the tags for the corresponding files.
Maybe that is an undocumented feature. It's news to me.
But that means Mp3tag (ie Florian) has done all the heavy lifting when tagging files using a CUE file.

There is no need to parse the CUE file, as I suggested earlier.
Instead, we can easily copy the tags from the list created from the CUE file to the individual WAV files.
That means the CUE file must be added to Mp3tag with all the WAV files that were split by using it.