As Whole-Play becomes more complex, the need to monitor various values of the composition has increased, and logging to a console is not particularly comfortable. Since I'm a web developer, I thought that creating a UI in the browser would be the best solution for me, so I set out to find a way to make Chuck talk to a browser. Here's my findings, using node.js and OSC.

I've been having some problems recording the MIDI generated by Whole-Play, but I think I've found a solution (slightly clunky, but workable). I'm writing this for future personal reference, and also in case it helps someone using Chuck with the IAC Driver, or in general anyone having trouble with Chuck and Midi Clock.

Well, for starters there are no constructors in Chuck (using v1.3.2.0). But it would be so good to have them, and to be able to call the parent's class constructor... but I'm getting ahead of myself, read on for the full story (you should be comfortable with OO concepts). Spoiler alert: I didn't really succeed. :)

I needed a singleton class for Whole-Play, here's how I went about it.