cue encoding
-
- Posts: 3
- Joined: Tue Sep 03, 2013 11:40 pm
cue encoding
I have some cue files with songs names in Russian language, player won't recognize it.
Is there a way to change cue file characxter encoding?
Note: may be duplicate of:
viewtopic.php?f=3&t=3003&p=7832&hilit=c ... 24ec#p7832
I have many cue+FLAC, cue+WavPack album data.
Usualy they are used on FooBar2k on Windows PC, that use OS's ANSI code page to reading cue file character encoding.
then most cue files are encoded as CP932 (Japanese Shift_JIS like)
I had import them on Neutron Music Player, but cue file character encoding is parsed as UTF-8.
- Is there a way to change cue file character encoding in app settings?
- or, Is there a way to indicate cue file characxter encoding in cue file itself?
viewtopic.php?f=3&t=3003&p=7832&hilit=c ... 24ec#p7832
I have many cue+FLAC, cue+WavPack album data.
Usualy they are used on FooBar2k on Windows PC, that use OS's ANSI code page to reading cue file character encoding.
then most cue files are encoded as CP932 (Japanese Shift_JIS like)
I had import them on Neutron Music Player, but cue file character encoding is parsed as UTF-8.
- Is there a way to change cue file character encoding in app settings?
- or, Is there a way to indicate cue file characxter encoding in cue file itself?
Re: Is there a way to change cue file characxter encoding?
Well, once upon a time it should have worked:
I suggest you contact neutronmp@gmail.com for clarification.
Re: cue encoding
> ! Fixed CUE could not locate music file it CUE encoding wasn't UTF-8.
seems it fix about "CUE could not locate", not fixing guess character encoding.
then I found fb2k supports CUE file with UTF-8 BOM marker, but neutron can not read it.
seems it fix about "CUE could not locate", not fixing guess character encoding.
then I found fb2k supports CUE file with UTF-8 BOM marker, but neutron can not read it.
Re: cue encoding
I sent mail to neutronmp@gmail.com.
Hi,
I have a problem about using cue files on fb2k(PC) and Neutron Player.
my post on forum:
viewtopic.php?f=3&t=3003&p=19225&sid=8a ... f1f#p19225
If there exists UTF-8 BOM marker:
- fb2k recognizes cue files encoded in UTF-8.
- Neutron can't recognize cue files.
If not exists UTF-8 BOM marker:
- fb2k recognizes cue files encoded in PC's current code page.
- Neutron ecognizes cue files encoded in UTF-8.
Please help:
- can the app skip the UTF-8 BOM marker?
- Is there a way to indicate cue file character encoding in the cue file itself?
- Is there a way to change cue file character encoding in app settings?
Re: cue encoding
Oh, I haven't been able to reproduce the problem about cue with UTF-8 BOM marker.
Who is online
Users browsing this forum: No registered users and 38 guests