<div dir="ltr">Tried running the pd~-help patch here (Arch), and it just runs at 100% on 1 cpu hogging all available RAM without doing anything. :(<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Apr 3, 2018 at 2:44 AM, Jonathan Wilkes <span dir="ltr"><<a href="mailto:jon.w.wilkes@gmail.com" target="_blank">jon.w.wilkes@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Mon, Apr 2, 2018 at 8:34 PM, Albert Graef <<a href="mailto:aggraef@gmail.com">aggraef@gmail.com</a>> wrote:<br>
> On Tue, Apr 3, 2018 at 1:19 AM, João Pais <<a href="mailto:jmmmpais@gmail.com">jmmmpais@gmail.com</a>> wrote:<br>
>> I was thinking rather mainly of dsp processing - although the gui can be<br>
>> heavy in some cases, mostly it's dsp that goes to the limits.<br>
><br>
> Pd's real-time core is single-threaded by design, so don't expect that<br>
> to change anytime soon. Coarse parallelism is available by running<br>
> different instances of the real-time engine using the pd~ object, cf.<br>
> extra/pd~. Unfortunately, this object doesn't seem to work in Purr<br>
> Data yet. (At least I couldn't get it to work, YMMV.)<br>
<br>
</span>Since when? It works for me-- at least I can a) instantiate the object,<br>
b) send Pd messages to [stdout] and receive them in the parent<br>
[pd~], and c) send audio to the parent instance and get output<br>
from the parent [pd~].<br>
<span class="HOEnZb"><font color="#888888"><br>
-Jonathan<br>
</font></span><span class="im HOEnZb"><br>
><br>
> Albert<br>
><br>
> --<br>
> Dr. Albert Gr"af<br>
> Computer Music Research Group, JGU Mainz, Germany<br>
> Email:  <a href="mailto:aggraef@gmail.com">aggraef@gmail.com</a><br>
> WWW:    <a href="https://plus.google.com/+AlbertGraef" rel="noreferrer" target="_blank">https://plus.google.com/+<wbr>AlbertGraef</a><br>
</span><div class="HOEnZb"><div class="h5">> ______________________________<wbr>_________________<br>
> L2Ork-dev mailing list<br>
> <a href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a><br>
> <a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/<wbr>listinfo/l2ork-dev</a><br>
______________________________<wbr>_________________<br>
L2Ork-dev mailing list<br>
<a href="mailto:L2Ork-dev@disis.music.vt.edu">L2Ork-dev@disis.music.vt.edu</a><br>
<a href="https://disis.music.vt.edu/listinfo/l2ork-dev" rel="noreferrer" target="_blank">https://disis.music.vt.edu/<wbr>listinfo/l2ork-dev</a></div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">Dr. Albert Gr"af<br>Computer Music Research Group, JGU Mainz, Germany<br>Email:  <a href="mailto:aggraef@gmail.com" target="_blank">aggraef@gmail.com</a><br>WWW:    <a href="https://plus.google.com/+AlbertGraef" target="_blank">https://plus.google.com/+AlbertGraef</a></div></div>
</div>