Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Non-ASCII device names are not handled correctly #7

Closed
dechamps opened this issue Sep 5, 2020 · 3 comments
Closed

Non-ASCII device names are not handled correctly #7

dechamps opened this issue Sep 5, 2020 · 3 comments

Comments

@dechamps
Copy link

dechamps commented Sep 5, 2020

Related: dechamps/FlexASIO#73

FlexASIO uses UTF-8 for device names everywhere, on the output of PortAudioDevices and in the configuration file.

However, FlexASIO GUI appears to be using the wrong encoding, as shown below when using the device name "Headéset":

image

It seems to be interpreting the device name in some kind of local 8-bit encoding (maybe CP 850 or ISO-8859-1) instead of UTF-8. FlexASIO GUI then ends up writing a configuration file with the wrong device name.

@flipswitchingmonkey
Copy link
Owner

This should be fixed with v0.2 now. (had to encode the incoming names from Portaudio to Windows-1252 and back to Unicode...

@dechamps
Copy link
Author

dechamps commented Sep 6, 2020

Thanks. I'm a bit confused as to why you'd need to do any conversions. I certainly don't do any in FlexASIO - PortAudio natively exposes device names as UTF-8 in its API, and I just use them as-is. I'm baffled as to why you'd need to use Windows-1252 anywhere, and I suspect it might cause problems with non-western-European character sets.

@flipswitchingmonkey
Copy link
Owner

Portaudio, at least as implemented in PortaudioSharp, give me the mangled names. But once converted to 1252 and then back to UTF, they appear fine. I don't have any way to configure Portaudio through the abstraction layer of portaudiosharp (don't even remember where I found that....). But it works. So... let's not question it too much :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants