I prefer a 'tighter' connection between the DSP engine (in this case chuck) and the enclosing app-environment. Although I need to update it to reflect the latest chuck-ness (which shouldn't be too hard), I set chuck up for the maxp/msp chuck~ object as a loadable lib that can be built right into the application. This gives access to all chuck functionality within the app. brad http://music.columbia.edu/~brad On Oct 16, 2009, at 12:07 AM, Andrew C. Smith wrote:
Has anyone tried to wrap ChucK into a standalone program? I'm thinking (at the very least) it could just be made to run simultaneously and communication could be made over OSC, but it would be cool to have the whole thing communicate through 8888, the port that the console communicates on. Basically, the mini is an effective wrapper, right? I'm just wondering if anyone has created anything simpler, like even just a program that outputs ChucK sounds when you click buttons or something. It would be really cool for games (or toys, not really games) that let users play around with sounds using an integrated graphical interface. Anyone try it?
Andrew _______________________________________________ chuck-users mailing list chuck-users@lists.cs.princeton.edu https://lists.cs.princeton.edu/mailman/listinfo/chuck-users