You might have a look at: http://www.youtube.com/watch?v=2rpk461T6l4 where Ge Wang gives a detailed ChucK demo.
(The shreds going to shred heaven at 46:00 are cute.)
-Jonathan
From: Spencer Russell spencer.f.russell@gmail.com To: Ivica Ico Bukvic ico@vt.edu Cc: pd-list@iem.at Sent: Mon, May 31, 2010 8:08:55 PM Subject: Re: [PD] ChucK vs. Pd
PD's blocking behaviour is also configurable with the [block~] object, so you can set the blocksize to a single sample if you like.
I think I remember reading that ChucK can operate with variable-sized blocks as well, but I could be wrong.
-spencer
On Mon, May 31, 2010 at 7:08 PM, Ivica Ico Bukvic ico@vt.edu wrote:
FWIW I looked at chuck to run on my performance wearable (500 MHz P3) and all I got was dropouts. Pd runs great in realtime on the same machine ...
That's because ChucK has its DSP loop set at per sample whereas Pd calculates everything in 64-byte chunks. While latter gives you a relief from the CPU load, it also lowers the actual control over DSP processes, so you can't exactly pinpoint a sample and translate its trigger into a non-signal domain beyond being sure that the event was triggered when the sample in question was located within the last 64-byte buffer.
HTH
ico
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list