[chuck-users] Status on running shreds?
arjan at scherpenisse.net
Wed Jan 7 15:59:19 EST 2009
-----BEGIN PGP SIGNED MESSAGE-----
I tried spawning a "chuck --loop" myself and capturing chuck's output.
However, while parsing the "status" command, I found 2 problems:
1) The host program does need to know how many shred lines will be
printed beforehand, because otherwise it will hang trying to read more input
2) The status command did not flush the standard output.
Ive made a small patch for this, and now I can control chuck (add/remove
shreds, view status info, etc) from a python script, hurray! I'm in the
process of writing a class for this and will share it as soon as i'm done.
For the two problems I mentioned, I made 2 tiny changes to chuck_vm.cpp;
i'm attaching that. Or should I post this stuf to the developers list
Tom Lieber wrote:
> 2009/1/5 Arjan Scherpenisse <arjan at scherpenisse.net>:
>> Tom Lieber wrote:
>>> Well miniAudicle "owns" its ChucK server; you could take that
>>> approach. At the very least I mean spawning the ChucK server so that
>>> you have its stdout.
>> Jep, I was thinking about that too.. but ideally i'd prefer a separate
>> server process so multiple instances could hook into it at the same time.
> A wrapper script for chuck which serves its output on a socket?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 369 bytes
Desc: not available
More information about the chuck-users