Chuck on windows7 64-bit - OTF and OSC not working
I'm using latest chuck 1.3.4.0 on windows7 64-bit. I can’t seem to get chuck to deal with the network at all. * -- probe crashes chuck; * any otf command like + crashes chuck; * chuck –loop seems to work, but subsequent otf commands like + cause a crash, even when specifying host and port explicitly The looped process crashes with the windows error (unexpected error – program needs to close)... The chuck + command reports “remote operation timed out”. I’ve tried with various combinations of --remote and --port in the "chuck +" command and combinations of --port and --loop and --server in the initial process. I also happen to be blind, so the miniaudical doesn't work for me at all! THe --probe command crashes chuck so its difficult to get an error report, but windows just says that a critical error has occured and the program needs to close; no other info is given. I've not been able to find any info on similar crashes online.
Hello Rich,
There is a DLL issue with the latest release of chuck on Windows with
command line, which might be related to this. However, the issue I know
about would typically cause chuck to not run at all on the command line,
not even --loop.
If you have a chance, please try the latest beta, which fixes the
previously known DLL issue, and let us know if it fixes the problems you
are experiencing:
https://ccrma.stanford.edu/~spencer/chuck/chuck-1.3.5.0-beta-4.msi
spencer
On Thu, Sep 11, 2014 at 12:36 AM, Rich Caloggero
I'm using latest chuck 1.3.4.0 on windows7 64-bit.
I can’t seem to get chuck to deal with the network at all.
* -- probe crashes chuck;
* any otf command like + crashes chuck;
* chuck –loop seems to work, but subsequent otf commands like + cause a crash, even when specifying host and port explicitly The looped process crashes with the windows error (unexpected error – program needs to close)... The chuck + command reports “remote operation timed out”. I’ve tried with various combinations of --remote and --port in the "chuck +" command and combinations of --port and --loop and --server in the initial process.
I also happen to be blind, so the miniaudical doesn't work for me at all!
THe --probe command crashes chuck so its difficult to get an error report, but windows just says that a critical error has occured and the program needs to close; no other info is given.
I've not been able to find any info on similar crashes online.
_______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users
Hi Spencer, thanx very much for the note.
It didn’t seem to fix thr problem. Detailed debugging is attached.
Anxiously awaiting any other suggestions!!
-- Rich
From: Spencer Salazar
Sent: Thursday, September 11, 2014 3:47 AM
To: ChucK Users Mailing List
Subject: Re: [chuck-users] Chuck on windows7 64-bit - OTF and OSC not working
Hello Rich,
There is a DLL issue with the latest release of chuck on Windows with command line, which might be related to this. However, the issue I know about would typically cause chuck to not run at all on the command line, not even --loop.
If you have a chance, please try the latest beta, which fixes the previously known DLL issue, and let us know if it fixes the problems you are experiencing:
https://ccrma.stanford.edu/~spencer/chuck/chuck-1.3.5.0-beta-4.msi
spencer
On Thu, Sep 11, 2014 at 12:36 AM, Rich Caloggero
participants (2)
-
Rich Caloggero -
Spencer Salazar