[chuck-users] cheap parallel ChucKing

mike clemow gelfmuse at gmail.com
Tue Feb 10 12:13:55 EST 2009

This makes me wish that there was a way to specify which TCP port the
chuck VM listens to when invoked on the commandline.  That way I can
chuck code at both VMs.

I suppose that OSC listeners on both VMs will work properly.  I could
have nearly doubled the power of my granular synthesis project last
semester.  *sigh*  But you could easily set up an OSC inter-process
communication scheme between the two VMs and have one VM act as a
slave to the other.  UDP is bad for maintaining state, since you can
easily lose packets.  For the most part, though, I tend to just design
the system so that packet-loss isn't that important.

Let's here it for the creative mis-use of OSC!


On Tue, Feb 10, 2009 at 6:51 AM, Graham Percival
<graham at percival-music.ca> wrote:
> On Sat, Feb 07, 2009 at 11:34:37AM -0600, Rogan Carr wrote:
>> The only drawback that I can see is that the OS will need to use one
>> of the cores from time to time, so you shouldn't be able to max out
>> both 100% of the time.
> That's fine; 160% (two cores at 80%) is much better than 100%.  :)
> Besides, I can't reach 100 anyway -- when I get to about 90%
> usage, chuck decides to drop the audio and the CPU usage falls in
> half.  I suppose I might be able to max out the cpu by doubling
> the number of (now-silent) ugens, but that isn't very useful for
> my interactive concert.
> Cheers,
> - Graham Percival
> _______________________________________________
> chuck-users mailing list
> chuck-users at lists.cs.princeton.edu
> https://lists.cs.princeton.edu/mailman/listinfo/chuck-users


More information about the chuck-users mailing list