Can you do a test by modifying the Audio dialog's TCL script? It's in the Pd folder: tcl/audio_dialog.tclModify the "set audio_indev" & "set audio_outdev" lines starting at 103 from:set audio_indev1 $indev1toset audio_indev1 [encoding convertfrom $indev1]This should convert the device name from the system encoding to UTF8 which the Tk GUI should be able to handle.Basically, modify those lines, then save the file and (re)start Pd. If it doesn't appear or crashes right away, then there is a low-level script error. It's a good idea to make a backup of the file just in case this happens.We may have to escape more strings throughout the GUI and probably re-encode the device strings when sending them back to the pd-core.On Jul 30, 2018, at 6:11 PM, Dan Wilcox <danomatika@gmail.com> wrote:It's a bug. Pd should be able to handle unicode in this case.In the meantime, you can set the LANG environment variable when starting Pd to English as detailed in https://github.com/pure-data/pure-data/blob/master/po/ README.txt#L42 Hello,
Pure Data throws the following error when I try to open up Media>Audio
Settings:
(Tcl) UNHANDLED ERROR: extra characters after close-brace
while executing
"lappend audio_indevlist {}CN (Realtek High Definition}
global audio_outdevlist; set audio_outdevlist {}
lappend audio_outdevlist {Xs [J ..."
("uplevel" body line 2)
invoked from within
"uplevel #0 $docmds"
My OS is in Japanese and, according to this page (
https://drugscore.blog.fc2.com/blog-entry-194.html ), I need to change the
language setting of my OS to English (presumably other European languages
would work, since I've used PD on a German-language system) to bypass this
system.
Just wondering if there was another fix- it's not a big deal for me to
change the settings, but maybe for Japanese people interested in PD it
would be.