[L2Ork-dev] GSOC: multi-core Purr?

Albert Graef aggraef at gmail.com
Mon Apr 2 20:58:05 EDT 2018


Tried running the pd~-help patch here (Arch), and it just runs at 100% on 1
cpu hogging all available RAM without doing anything. :(

On Tue, Apr 3, 2018 at 2:44 AM, Jonathan Wilkes <jon.w.wilkes at gmail.com>
wrote:

> On Mon, Apr 2, 2018 at 8:34 PM, Albert Graef <aggraef at gmail.com> wrote:
> > On Tue, Apr 3, 2018 at 1:19 AM, João Pais <jmmmpais at gmail.com> wrote:
> >> I was thinking rather mainly of dsp processing - although the gui can be
> >> heavy in some cases, mostly it's dsp that goes to the limits.
> >
> > Pd's real-time core is single-threaded by design, so don't expect that
> > to change anytime soon. Coarse parallelism is available by running
> > different instances of the real-time engine using the pd~ object, cf.
> > extra/pd~. Unfortunately, this object doesn't seem to work in Purr
> > Data yet. (At least I couldn't get it to work, YMMV.)
>
> Since when? It works for me-- at least I can a) instantiate the object,
> b) send Pd messages to [stdout] and receive them in the parent
> [pd~], and c) send audio to the parent instance and get output
> from the parent [pd~].
>
> -Jonathan
>
> >
> > Albert
> >
> > --
> > Dr. Albert Gr"af
> > Computer Music Research Group, JGU Mainz, Germany
> > Email:  aggraef at gmail.com
> > WWW:    https://plus.google.com/+AlbertGraef
> > _______________________________________________
> > L2Ork-dev mailing list
> > L2Ork-dev at disis.music.vt.edu
> > https://disis.music.vt.edu/listinfo/l2ork-dev
> _______________________________________________
> L2Ork-dev mailing list
> L2Ork-dev at disis.music.vt.edu
> https://disis.music.vt.edu/listinfo/l2ork-dev
>



-- 
Dr. Albert Gr"af
Computer Music Research Group, JGU Mainz, Germany
Email:  aggraef at gmail.com
WWW:    https://plus.google.com/+AlbertGraef
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20180403/a6ecfa91/attachment-0001.html>


More information about the L2Ork-dev mailing list