OK!
On Wed, Jan 30, 2019 at 10:00 PM Dan Wilcox danomatika@gmail.com wrote:
Best would be to print the strings somehow. My laptop is away for repair. When I get it back, I can write a small bit of tcl you can add to the Pd gui that will print the devices to the console and you can then export the console log. I'll get back to you...
On Wed, Jan 30, 2019 at 11:08 AM S.E.P. < dreamoftheshoreofanotherworld@gmail.com> wrote:
Hello!
I'm very sorry I never saw your reply, Dan. I just kept using PD without access to the Audio Settings... Today, I finally changed the OS language and system region to English (U.S.) and can open Audio Settings.
To answer your questions, I'm not tech-savvy enough to know how to "get a copy of the string that causes the error". I've used error logs for Android before, do I need to open something like that, but for Windows and look at it while I click on Media>Audio Settings?
As for the setup, it's Windows 10 on a Dell Inspiron 15 7577 NG55VR-7WL.
Let me know how I can help.
Best, Elliot
On Mon, Aug 13, 2018 at 10:56 PM Dan Wilcox danomatika@gmail.com wrote:
Internationalization support is definitely high on my list. Is there some way you could get a copy of the string that causes the error? It's hard to debug/fix things without the same set up, ie. it could be a problem with Tcl/Tk or Portaudio string handling on Windows, etc. In any case, the audio dialog shouldn't crash Pd on our friends in Japan!
On Aug 2, 2018, at 5:52 AM, S.E.P. < dreamoftheshoreofanotherworld@gmail.com> wrote:
I guess I'll have to change my system settings to a European language then. Too bad! It was good for my vocabulary to have the JP settings.
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com robotcowboy.com
-- Dan Wilcox @danomatika danomatika.com robotcowboy.com