I think I've made this mistake before.
However, when I start [pd~], it definitely makes a terminal window and a Pd console.
I'll try this other method with the controls and Gem in the mother patch and put all the sound generation in the child process.
By the way, the Gem process is creating an oscilloscope from external signals while the LFOs are simply generative CV to go out the dacs. The two processes should be happening together but aren't related. This connects with an Expert Sleepers ES-8.
On Sun, Apr 11, 2021, 11:42 AM Martin Peach chakekatzil@gmail.com wrote:
Hi Samuel, I think you have it backwards -- you should run the audio in [pd~] as it already has no GUI. And if you don't care about latency (it sounds like you're using prerecorded or generated dmaterial), just increase the audio block size until you don't get dropouts.
Martin
On Sun, Apr 11, 2021 at 11:23 AM Samuel Burt composer.samuel.burt@gmail.com wrote:
Here's what I'm trying to do: On a Raspberry Pi 3, I want to run an audio patch that generates LFOs
and also have a Gem window that shows [scopeXYZ]. There are tremendous dropouts unless [scopeXYZ] has a very short length of samples to process.
Here's one problem I've run into: I'm prototyping on Windows 10. I decided to try running the Gem
component in a subprocess [pd~]. The [pd~] object doesn't seem to accept the "-nogui" tag. How do I use it? Will it also hide the terminal window that launches the second copy of Pd?
Is this an effective method of separating Gem from audio on a Raspberry
Pi? Is there a better way?
Hi. I find it difficult to search for discussions related to pd~ because
Google uses ~ for synonym searches. Any tips for searching for [pd~] on the web and the mailing list?
Thanks! Sam
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management ->