-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I'm new here, and not so much into audio programming (yet), but I'm interested in ChucK from a software perspective. I'm trying to code a little "live coding" app (python+gtk+glade), much like the miniAudicle, but interfacing with ChucK through shell commands (like chuck-mode for emacs). So I wondered whether it's possible to get information on the running chuck process. In the simplest form, I would like to get the output of the "chuck --status" command. That command now lets the VM write on its stdout; not on the stdout of the calling process. Can somebody point me in the right direction? Thanks, Arjan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklhOLUACgkQigE4AbflYeoMagCfeqLMlrG6hXKFmfV2IuuPkauD HsgAn0RvcVJnjHcXHJHoOCv7sy5Rj+nP =spEn -----END PGP SIGNATURE-----
2009/1/4 Arjan Scherpenisse
I'm new here, and not so much into audio programming (yet), but I'm interested in ChucK from a software perspective. I'm trying to code a little "live coding" app (python+gtk+glade), much like the miniAudicle, but interfacing with ChucK through shell commands (like chuck-mode for emacs).
So I wondered whether it's possible to get information on the running chuck process. In the simplest form, I would like to get the output of the "chuck --status" command. That command now lets the VM write on its stdout; not on the stdout of the calling process.
Can somebody point me in the right direction? Thanks,
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. -- Tom Lieber http://AllTom.com/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. Arjan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAklhyaIACgkQigE4AbflYerSVACeO0NUkb/ztbZDPQC9mXvxC8ug mNIAnjv3B7hYMZJmmyYIwAjxSzGZvIjp =L8Jg -----END PGP SIGNATURE-----
2009/1/5 Arjan Scherpenisse
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? -- Tom Lieber http://AllTom.com/
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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 instead? regards, Arjan Tom Lieber wrote:
2009/1/5 Arjan Scherpenisse
: 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 iEYEARECAAYFAkllF6cACgkQigE4AbflYerVTwCfU5Dy+2FB/yAg8gklrCiycTGQ x4wAniERRdV4n3aYtzqqeQcoW3xBVfz1 =R4tv -----END PGP SIGNATURE-----
Arjan;
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 instead?
I feel it should be safe to assume the dev's read this list, then again; I also feel *I* should get back to people that mail me which at times can require some further "poking" as well :¬). In the interest of convenience I've taken to mentioning the word "bug" in the topic of emails concerning those, to facilitate searches of the archive, maybe we should also use "patch" or "[patch]" that way? If you get no reaction I'd try the dev list for a reminder; our devs are friendly, enthusiastic, tallented.... and starved for time as well as occasionally chaotic. Kinda like normal people, except more so. It's very good to see another Dutchman on the ChucK list, BTW. Your name looked Dutch so I had a peek at your site. Do give a shout if you're doing anything pupblic and ChucKian, Amsterdam is only 45 minutes or so by train from The hague after all. Yours, Kas.
participants (3)
-
Arjan Scherpenisse
-
Kassen
-
Tom Lieber