I just did a project where I ran two instances of Chuck each listening to different sound cards, since Chuck (or RTaudio) has problems with aggregate devices for some reason. I just used the --port flag to separate one of them, and didn't get the complaint. The complaint, of course, won't ever bother you unless you're doing
chuck + myfile.ck
in another window. to choose a specific chuck instance to send code to, you'll need to specify the port as well:
chuck --port8686 + myfile.ck
like that. then, you're sending myfile.ck to the Chuck instance listening on port 8686 and not the one listening to the default port (8888).
I was doing this on Snow Leopard... that's 10.6, right?
is it the case that you're not even able to get the other instance to run?
-Mike
2010/1/6 Kassen <signal.automatique@gmail.com>:
> Might this be a combination of a undocumented change to CoreAudio, combinedI just tested an app that uses the latest RtAudio, and when it's
> with our RTAudio being out of date?
launched twice they share the sound card. So either ChucK uses RtAudio
differently, or it's the version difference.
--
Tom Lieber
http://AllTom.com/
http://ckvlang.org/
_______________________________________________
chuck-users mailing list
chuck-users@lists.cs.princeton.edu
https://lists.cs.princeton.edu/mailman/listinfo/chuck-users