Thanx Spencer for being willing to look into this. Sorry for being a pain. I’m forced to use windows because I use a screen reader and find it much easier to deal with than Linux at present.
I’m incredibly glad that chuck development has gotten into high gear; this can only mean great things ahead for the language! I love it!
 
-- Rich
 
 
Sent: Tuesday, February 24, 2015 2:27 AM
Subject: Re: [chuck-users] chuck --loop not working on windows
 
Hey Rich,
 
Thanks for looking into this and narrowing it down a bit- I can probably check the diff between 1.2.1.3 and the current version to see what might have introduced this problem. Lately ChucK development has switched into a higher gear, so its an unfortunate side-effect that as some parts march forward, other less popular features can fall behind.
 
Once I figure out whats going wrong here, be ready for some beta builds to test out!
 
spencer
 
 
On Mon, Feb 23, 2015 at 6:09 PM, Rich Caloggero <rjc@mit.edu> wrote:
Sorry to keep adding to this, but the latest version does work correctly on Windows when adding schreds with Machine.add(); you just can’t do it with command-line options! Seems very strange to me!
 
Does anyone besides me cChucK on windows!  DOes anyone have any idea, however implausible, what might be causing this problem?
 
 
Sent: Sunday, February 22, 2015 3:03 PM
Subject: Re: [chuck-users] chuck --loop not working on windows
 
I’ve verified that v1.2.1.3 does handle this correctly on windows.
I’ve also verified that latest version fails on both 32-bit and 64-bit systems.
-- Rich
 
 
Sent: Saturday, February 21, 2015 12:00 PM
Subject: [chuck-users] chuck --loop not working on windows
 
I’ve written about this before, but the problem persists even with the latest build: 1.3.5.0 (beta 7), win32
 
I’m running on 64-bit windows; might this be the issue?
Using bash syntax here. I’ve run under cmd.exe and under git bash with exactly same results.
 
If I say:
$ chuck –loop &
 
then say:
chuck + otf_01.ck
while in the examples directory,
 
I get:
-- chuck: remote operation timed out
 
the shell tells me that the first process exited with code 23
 
windows does it’'s “unknown error” dialog box thing and offers to close the program. I click “close” or “cancel” ...
 
I’ve used other permutations of “-p” with numberic argument on both invocations and –remote with hostname of 127.0.0.1, added –server (seems to be valid option but not described anywhere), and same result. 
 
 
However, if I start two terminals, cd to examples/osc, and in one say:
chuck r.ck #with no trailing “&” so it stays in foreground
 
and in second terminal say:
chuck s.ck #separate vm invocation – no “+” here
 
then things work fine – i.e. the two separate VMs communicate via OSC just fine.
 
 
Any idea what’s going on here?
 
-- Rich
 
 

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users

_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users



 
--
Spencer Salazar
Doctoral Candidate
Center for Computer Research in Music and Acoustics
Stanford University
 
+1 831.277.4654
 


_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users