sptest.pd

sp3.pd

hi,

I have some questions about the pd~ object. My Raspberry Pi 3 has one processor running at 100% and the other 3 running at almost 0%. So I’d like to allocate some processing power to those other processors. I’m guessing that’s what the pd~ object is for correct?

If I have an audio signal and I go into the inputs of a pd~ object will all the processing above that pd~ object be allocated to another processor? Or do I need to make a separate patch and open it with the pd~ object, and everything in that patch is run on another processor?

Or if I send audio into a pd~ object and have reverb and delay effects happen in a subprocess, would just those effects be created on a different processor?

I read this document:

http://www.pdpatchrepo.info/hurleur/multiprocessing.pdf

which explains the concept behind why the pd~ object is necessary. And I looked at the pd~ help file, but I can’t get this to work.

I uploaded some of the things I tried out. If anyone can alter these to demonstrate how this object works I’d appreciate it.

thanks, Nick

If you put something like [sigmund~] or another CPU-hungry object on the patch that gets instantiated by [pd~] you should see the computation being done on a different CPU than the one used by the parent patch.

I'd try it with a patch in the parent Pd instance that is less CPU-intensive than the one you're currently testing with. It's too difficult to do a sanity test when the patch is already at 100%.

Exactly, you need to split your main patch in multiple patches: main (trying to be around 80% of a single core), FX (for example) also around 80% (on second core), etc... you get the idea.

There's a trick btw to send midi to pd~ I don't recall exactly what was it, but poke me if you need that too.

Cheers~

Hi everyone,

thanks for your replies. The problem I am having is that I can't open a separate patch with the pd~ object. I was thinking I would put my audio delays and reverbs (audio effects in general) in a pd~ patch to start. But I can't open a patch with pd~. Do you create a patch with inlets and outlets, store it in the same folder as the parent patch, then send the pd~ a message like "pd~ start -mypatchname.pd" ? Because that isn't working for me.

When I send "pd~ start -mypatchname.pd" to pd~ object a new terminal window opens. I can't get audio into or out of a pd~ object, I can't view what's happening in mypatchname.pd, and I can't tell if it even opened that patch. If someone can just explain how this works I'd appreciate it.

thanks.

In [pd~]'s help patch it writes pd~ start pd~-maypatchname.pd(
Did you miss the pd~ part attached to the name of the patch?

@nicnut Here's how I use it

Hey Everyone. I finally figured this out.

For me sending a message with: pd~ start pd~-mypatch.pd didn't work for some reason. I had to send my message as: pd~ start mypatch.pd I don't know if the help file should be changed, but thank you to @EEight for your example image.

Also I am using 2 channels of audio in/out. inside the patch that my pd~ object is opening I had to have an [adc~ 1] and [adc~2] to get the audio in. I was trying to use inlet~ or just two adc~ objects and that wasn't working.

To get audio out I needed [dac~ 1 2] instead of an outlet~ or just dac~. I thought dac~ would work because that has left and right. I also had to have a load bang inside the patch that pd~ is opening that starts the audio.

Anyway, I have something working. Now I'm gonna divide up all my patches.

Thank you all for your help.