Elise

I'm having some issues with getting a standalone to instantiate plugins through vst~ objects in 4.6.3. I've never had trouble with this in other versions, but I've been poring over the forums and tweaking my app script for hours in vain.

Standalone contains vst~ objects with plugin names as passed arguements through the inspector. I have demo versions of both Hipno and Pluggo installed on the machine, which is a Mac Intel. I have added the plugins explicitly to the standalone script with the folder containing them listed in my path prefs as well. The script compiles fine, but when I launch the standalone, I get the usual vst "can't find" error:

? error: +decimate.vst: no such file in collective

I have the rootLibrary C74 Plug-In Support folder in my path prefs. The only thing that appears to be of mild interest is that the Library C74 Plug-In Support doesn't show when I print my filepaths even though it is definitely in the Preferences pane. Perhaps this is irrelevant, I don't know. I've tried every flavor of the standalone object search prefs, with the only notable difference being that the application compile beachballs if I check the "Search for Files Not in the Application's Collective" box.

? error: +decimate.vst: no such file in collective
vst~: can't find plug-in, using default
The 1 parameter of Default is:
P1

I have the rootLibrary C74 Plug-In Support folder in my path prefs. The only thing that appears to be of mild interest is that the Library C74 Plug-In Support doesn't show when I print my filepaths even though it is definitely in the Preferences pane. Perhaps this is irrelevant, I don't know. I've tried every flavor of the standalone object search prefs, with the only notable difference being that the application compile beachballs if I check the "Search for Files Not in the Application's Collective" box. 

4-6-3-standalone-vst-issues-2

You'll definitely need to work around this one.

How about just putting the vst plugs in the app bundle somewhere?

If you are putting plugs in your collective because you do not want people to use them in other apps then it should be easy enough to write some kind of handshaking which is specific to your app.

Sorry, I should have mentioned that placing them inside the package was my first approach. It didn't work (same symptoms) and I naively assumed that perhaps something about that functionality had changed in the 4.6.3 update, rather then thinking something was off with my MaxMSP config. Going to do a clean install on everything and see if that fixes the issue. Will report back.

I have reproduced what you see. Sorry if this has gone and changed on you between MaxMSP versions. We'll look at the problem for a future version of MaxMSP but for now please workaround it by either placing the plugs in the same folder as your app or in the System VST folder.

Thanks Andrew. I've tried both these approaches (placing inside the app folder and also in the /Library/Audio/Plug-Ins/VST directory) with the plugs referenced explicitly in the app script, resulting in the same error "no such file in collective." I assume these are working for you.

Hmmm...seems like maybe a filepath thing (?) although I've never seen the put-it-in-the-same-folder-as-the-app approach not work before.

Thanks Andrew. I've tried both these approaches (placing inside the app folder and also in the /Library/Audio/Plug-Ins/VST directory) with the plugs referenced explicitly in the app script, resulting in the same error "no such file in collective." I assume these are working for you. 

One thing that I find helps with standalones is to create a "lib" folder 

in the same folder as the app, and then referencing the files inside 

"lib" with a relative path, e.g. "./lib/myplugin.vst"

One thing that I find helps with standalones is to create a "lib" folder 
in the same folder as the app, and then referencing the files inside 
"lib" with a relative path, e.g. "./lib/myplugin.vst"

thanks- i tried it without the explicit reference initially (and then again just now b/c it's been a couple days) and no difference. Even without the vst referenced in the build script (and the plug in the same folder as the built app), i get the error.

This sounds like you have some other problem going on.

I get no errors with a plug in the same folder as my app.

Nor do I with the plug in the System VST folder - all is good.

Please send a stripped down patch (which we can turn into and app) and your plug with the exact steps you are taking to build and run to

support @ cycling74 dot com and we'll have a look at it for you.

This sounds like you have some other problem going on.
I get no errors with a plug in the same folder as my app.
Nor do I with the plug in the System VST folder - all is good.

4.6.3 standalone vst~ issues