<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:12pt"><div><div>You might have a look at:<br><span><a rel="nofollow" target="_blank" href="http://www.youtube.com/watch?v=2rpk461T6l4"><span class="yshortcuts" id="lw_1275365202_0">http://www.youtube.com/watch?v=2rpk461T6l4</span></a></span><br>where
Ge Wang gives a detailed ChucK demo.<br></div><br>(The shreds
going to shred heaven at 46:00 are cute.)<br><br>-Jonathan</div><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;"><br><div style="font-family: arial,helvetica,sans-serif; font-size: 10pt;"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Spencer Russell <spencer.f.russell@gmail.com><br><b><span style="font-weight: bold;">To:</span></b> Ivica Ico Bukvic <ico@vt.edu><br><b><span style="font-weight: bold;">Cc:</span></b> pd-list@iem.at<br><b><span style="font-weight: bold;">Sent:</span></b> Mon, May 31, 2010 8:08:55 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: [PD] ChucK vs. Pd<br></font><br>
PD's blocking behaviour is also configurable with the [block~] object,<br>so you can set the blocksize to a single sample if you like.<br><br>I think I remember reading that ChucK can operate with variable-sized<br>blocks as well, but I could be wrong.<br><br>-spencer<br><br>On Mon, May 31, 2010 at 7:08 PM, Ivica Ico Bukvic <<a ymailto="mailto:ico@vt.edu" href="mailto:ico@vt.edu">ico@vt.edu</a>> wrote:<br>><br>>> FWIW I looked at chuck to run on my performance wearable (500 MHz<br>>> P3) and all I got was dropouts. Pd runs great in realtime on the same<br>>> machine ...<br>><br>> 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.<br>><br>> HTH<br>><br>> ico<br>><br>><br>> _______________________________________________<br>> <a ymailto="mailto:Pd-list@iem.at" href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br><span>> UNSUBSCRIBE and account-management -> <a target="_blank" href="http://lists.puredata.info/listinfo/pd-list">http://lists.puredata.info/listinfo/pd-list</a></span><br>><br><br>_______________________________________________<br><a ymailto="mailto:Pd-list@iem.at" href="mailto:Pd-list@iem.at">Pd-list@iem.at</a> mailing list<br>UNSUBSCRIBE and account-management -> <a href="http://lists.puredata.info/listinfo/pd-list" target="_blank">http://lists.puredata.info/listinfo/pd-list</a><br></div></div>
</div><br>
</body></html>