So I guess the tcl files are in /usr/local/puredata/tcl/ ? In this case, you could just make a symbolic link to your home directory:
ln -s /usr/local/puredata ~/pd
(this will clutter your home directory; I need to make /usr/local/puredata be one of the places pureVST searches by default. I also just learned that on Debian pd seems to live in /usr/lib/puredata and not /usr/lib/pd as I had assumed.
Alternatively, you could just go change "/usr/lib/pd" to /usr/local/puredata in the pureVST source and remake - but I imagine it's sompler for now to just make the symbolic link.
cheers Miller
On 6/2/25 3:51 PM, Alexandros Drymonitis wrote:
On 6/1/25 11:53, Miller Puckette wrote:
It sounds like pureVST is loading (hence the sliders and the 20 channels) but that it isn't finding its way to the GUI, which it borrows from an installed Pd application. The plug-in searches in ~/pd and in /usr/lib/pd (which I think is the normal place that the automake stuff puts it) - or more specifically, it needs to find TCL files as ~/pd/tcl/pd-gui.tcl (etc) or as /usr/lib/pd/tcl/pd-gui.tcl etc. Next on my own dolist is to search for derivative filenames such as "pd-0.55-2" etc.
I've built Pd from source so all these files are in /usr/local/ on my computer. Is there to force PureVST to look there? I also built the new source I downloaded where I built libpd prior to building Pd, but still no luck.