Closed yuna0x0 closed 2 years ago
It's a Windows code page conversion issue. I have solved it by enabling system-wide UTF-8 support (beta) in Windows 11.
Thanks for the info, very interesting!
It's worth noting that in theory you shouldn't have to do this. This is still a bug in FlexASIO GUI. Most likely it has something to do with something somewhere in FlexASIO GUI using codepage-dependent ("ANSI") Windows APIs instead of Unicode (UTF-16) APIs. This would explain why Chinese characters are not being handled correctly on a system configured to use a western code page.
Related to #7.
The GUI does not handle the device with Unicode name correctly. It is resulting in a corrupted config file.