vst~ inside standalone


    Feb 17 2013 | 8:19 pm
    I have tried to get to the bottom of an issue, but have failed. Sorry if it is has been asked before, or the answer is obvious.
    Is there a way to get a vst~ to remain in a standalone, so that another user can open the standalone without having the .vst file on their computer? and yes the vst is a freeware plugin.
    this is the best i have found on the topic, but it is quite old...
    i have tried including the .vst to the standalone file path when building the application, but no joy.
    All the other user gets is a vst not found message in the max window.

    • Feb 18 2013 | 12:13 am
      You don't need to add it to the standalone path, I don't think. Just manually copy the vst~ into the standalone folder after you've made the standalone and it should be able to find it. If not, you can have the user select it with the "plug" message, or you can get the standalone path by sending the
      ;max sendapppath
      message. (Note that this is different than [thispatcher] path message.) Check "Messages to Max" in the docs to see how it works, and check the little example below.
      With that path and [sprintf] you can specify where to auto-load the vst~ (or any other files for that matter). Check [sprintf] help file for constructing the file path, there are a few gotchas.
    • Feb 18 2013 | 10:38 am
      so in other words there is no way to package up the vst into the standalone?
      It has to reside in a folder along with the application, and then you have to specify where the application should look for the vst, either automatically, or manually?
    • Feb 18 2013 | 4:26 pm
      As far as I know, yes, but I could be wrong. Not entirely sure what happens when you "Include File" or "Include Folder" in the Build settings sometimes. It sounds like you're incorporating it into the .mxf but I think that's only the case for some types of files...? and other ones it puts in the folder?
      Example: with a matrixctrl that has an image associated with it, it seems to automatically include the image. But that's not always the case with objects and associated files...is it?
      Yes, it's been a bit of a mystery for me as well...
    • Feb 18 2013 | 4:41 pm
      I certainly used to work that if the plug-in was at the same level as the standalone, you could loadmess it in or even use it's name as an argument; I used to use a dummy Pluggo plug to load into vst~ on start-up just to prevent a bunch of "vst~ doesn't want midi events" messages in the Max window. Even if putting it into the package did work, it sort of seems like hiding someone else's work within your own, and I guess you should check with the plug-in's author that they're OK with it being used in this way, even if it is freeware, Cheers Roger
    • May 17 2014 | 10:23 pm
      Sorry to revive this topic but I've yet to actually get it to work. Personally, I don't care if the VST is or isn't visible within the max file path as I'll mostly be using this for private things. However, when I include a VST within the standalone, I know it's there because of the different sizes of the .app but I cannot find it within the search path. I tried different things on seejayjames' patch but couldn't get it to work. Any tips of more examples?
      Thanks a lot