<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Spencer<div>Thanks a lot for the answer. It is very clear. You could almost insert it in the documentation, I was looking for this for a while, maybe more people would too. The hint about running several instances of chuck is a good one, for some reason I did not think about it and for some stuff for sure useful. (just chuck from different commandline taps)</div><div>-- Yes by closer thought one can imagine that the calculations in chuck must be kept tight together,, very different than for instance generating images with 'Processing'</div><div><br></div><div>Chuck is fabulous and the first place to try out new ideas for algorithms at sample accuracy. This week I was looking at waveforms generated from quaternions rotating around each other. One need at least 4 quaternions to move beyond periodicity, but this is actually not doable on a high-end PC at audio sample rate. Too many multiplications. Got to go back to the 70ties style and generate a dataset over night I guess.</div><div><br></div><div>greetings</div><div><br></div><div><br><div><div>On Dec 15, 2014, at 11:20 PM, Spencer Salazar wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi <span style="font-size:13px">Vilbjørg,</span><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">ChucK does not spread processing load for multiple shreds over multiple CPUs/cores -- all shred and audio processing occurs on a single logical core. This is mainly because ChucK makes several strong guarantees about the timing between shreds and audio processing, and these are difficult to maintain across multiple cores. </span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">Its not uncommon to run multiple chuck instances if multiple-core utilization is necessary, using OSC to communicate data between them. You lose a lot of the power of shreds in ChucK, but as I mentioned these attributes are difficult to implement with multi-core awareness anyways. </span></div><div><span style="font-size:13px"><br></span></div><div><span style="font-size:13px">spencer</span></div><div><span style="font-size:13px"><br></span></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Dec 15, 2014 at 5:14 AM, vilbjørg broch <span dir="ltr"><<a href="mailto:vilbjorg@antidelusionmechanism.org" target="_blank">vilbjorg@antidelusionmechanism.org</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">hi<br>
<br>
I have problems getting shreds to spread load over multiple cpus neither from miniAudicle nor commandline chuck<br>
Running linux Debian 3.2.0-4-amd64, chuck 1.3.4.0 jack, miniAudicle 1.3.2 jack<br>
<br>
I just tested the same .ck files on a mac and it looks like that the sporked shreds automatically spreads over at least 2 of 4 (4 of 8) cores.<br>
<br>
<br>
Is there any more information to find about how to handle or understand these issues, or does anyone have any tricks to share?<br>
<br>
Much greetings<br>
Vilbjørg<br>
<br>
<br>
_______________________________________________<br>
chuck-users mailing list<br>
<a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br>
<a href="https://lists.cs.princeton.edu/mailman/listinfo/chuck-users" target="_blank">https://lists.cs.princeton.edu/mailman/listinfo/chuck-users</a><br>
<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div style="font-family:arial;font-size:small"><div>Spencer Salazar<br></div><div>Doctoral Candidate</div><div>Center for Computer Research in Music and Acoustics</div><div>Stanford University</div><div><br></div><div><a href="mailto:spencer@ccrma.stanford.edu" target="_blank">spencer@ccrma.stanford.edu</a></div><div></div><div>+1 831.277.4654<br></div><div><a href="https://ccrma.stanford.edu/~spencer/" style="color:rgb(17,85,204)" target="_blank">https://ccrma.stanford.edu/~spencer/</a><br></div><div><br></div></div></div></div></div></div></div></div></div></div>
</div>
_______________________________________________<br>chuck-users mailing list<br><a href="mailto:chuck-users@lists.cs.princeton.edu">chuck-users@lists.cs.princeton.edu</a><br>https://lists.cs.princeton.edu/mailman/listinfo/chuck-users<br></blockquote></div><br></div></body></html>