On 6/1/25 10:14, Miller Puckette wrote:
I think that must be exactly what's going on. I never use the automake system (it's far too complicated for me to understand) and so I don't end up confusing the libpd build. So yes, as Dan says, or alternatively just get a clean copy of the Pd source and build libpd in it using only the Makefile in the libpd directory. I'll update the pureVST README accordingly :)
Miller
On 5/31/25 9:32 PM, Dan Wilcox wrote:
Maybe my comment was a red herring, but to explain: I have run into the issue on my own system (and by an issue or two others have posted), that if you build desktop pd, at least using the auto tools build, the generated .o files will not contain the multi instance stuff. If you later build libpd within the libpd directory, the makefile there will reuse the existing .o files even though it's trying to build with PDINSTANCE set, which can lead to link issues. The way forward is to clean the main dir before building libpd itself to be sure.
I downloaded Pd's source and built libpd only (I have already built Pd) and the whole process worked! Is what I'm looking for the PureVST.so file? When I set the path to this file in Reaper's or Ardour's VST search paths I do get a PureVST-0.5(msp)(20 ch) plugin, but it's a window with 20 sliders. There's an "open" button for Pd's gui, but clicking on it just freezes both software (Reaper or Ardour) whether the track where I set the plugin plays or not.
I've read that Reaper has some issues with this, not sure if it's this one. Are we supposed to be able to patch within the plugin like it is with plugdata? If not, what do these sliders do?
Thanks for the help so far.