-
himi
Hello, does anyone use the object [pd~] to successfully create sub-processes?
I have a patch running on a headless raspberry pi 3.
Now I want to move parts from the patch to subprocesses to move cpu load to another core.The main-patch runs perfectly and I get all the output via ssh terminal.
After activating dsp in the main patch I start a sub-process, as described in the [pd~] help patch.
For testing, I print something with a [loadbang], which appears on the terminal,
but then it just seems to stop.
The process is still there, running and consuming cpu time, but a second, delayed print after the initial loadbang wont appear. An [osc~440] object also won't be hearable.Now I'm wondering if it's a problem with the [pd~] object?
It prints "pd~ version 0.3" when the sub-process is started."puredata -version" prints "Pd-0.46.2 ("") compiled 07:48:11 Oct 29 2014"
Many greetings!
-
himi
In the past for applications where no video was involved I used this:
pd-extended -nogui
I'm using Raspbian Jessie Lite on a Raspberry Pi 3 and as I want to use GEM
-nogui
is not an option.
At first I thought just a window manager is needed, so I tried various, but all returned something like "can't connect to display".Finally I installed LXDE: https://www.raspberrypi.org/forums/viewtopic.php?f=66&t=133691
Now I can run pd without problems and get video output at the hdmi port:
sudo startx /usr/bin/pd-extended <...arguments for pd...>
Tricky is that you need to specify the absolute path to pd. If you do not you can't pass any arguments to pd.Maybe anyone has another (more lightweight) solution which avoids installing LXDE?
OMXplayer for example can output video without LXDE.
Or is it not that easy and some rendering/video-card-communication has to be done by LXDE and isn't built into pd?