This is a companion discussion topic for the original entry at https://blokas.io/pisound/docs/pisound-puredata/
This is a companion discussion topic for the original entry at https://blokas.io/pisound/docs/pisound-puredata/
Hi,
is there any extra doc ?
- how do I start pd with my own patch in the pisound ecosystem ?
- how to make sure a service starts puredata on boot ?
thanks
The Pisound scripts don’t auto-launch Pure Data on boot, for that, use the Pure Data module of Patchbox OS.
I enabled the puredata module
but there is virtually no documentation
and this does not tell me how to have my own .pd files in place of these
(without copying my code base in the same folder I mean)
I found a way by using logincal link to wmy folder
sudo ln -s /home/patch/ /usr/local/puredata-patches/Phil/
then I copied the blokas yaml in my folder /usr/local/puredata-patches/Phil/blokas.yml
and it shows up, so I can select it in the config utility
note that one canno create a symbolic link from /usr/local/puredata-patches/, it requires a proper normal folder
also I whish there were documentation that explains where are all these puredata/pisound settings stored
You can either create a ‘blokas.yml’ file in your PD patch folder, or name the entrypoint fail as ‘main.pd’.
Some documentation on these files are here:
