Jakob Jørgensen

I hope someone out there can help me out with this little problem.

I’m using a VST plugin in my patch to generate sounds (through the vst~ object) and I need to make a stand alone EXE build of my patch. I’m developing on Windows 8.

When running the patch inside MAX, there’s no problem loading the VST, as long as the file path reference to the VST is correct.

But when I’m building a stand alone EXE, the VST won’t load. It seem like the stand alone can't see the VST plugin. I’ve tried to include the VST plugin folder in the build script dialogue to see if that did the trick, but no luck.

I’m pretty sure that this is all trivial but I just can’t seem to figure out how to solve this.

Any help would be deeply appreciated! :-)

I’m using a VST plugin in my patch to generate sounds (through the vst~ object) and I need to make a stand alone EXE build of my patch. I’m developing on Windows 8.
When running the patch inside MAX, there’s no problem loading the VST, as long as the file path reference to the VST is correct.

I’m pretty sure that this is all trivial but I just can’t seem to figure out how to solve this.
Any help would be deeply appreciated! :-)

building-stand-alone-with-a-vst-plugin

Found a solution: Providing the vst~ object an absolute path to the VST plugin seems to do the trick. :-)

Could you elaborate ? My .exe will go on various different computers so the drive name may change... so it might not always be c/patch or whatever - anyway how did you write the path name in on the actual object or as a message ?

he probably means "a path inside the search path", because that is what will work.

put a copy of the plug-in somewhere in your search path, call it by its name (withouth path), after biulding the app put another copy of the plug-in beside the app.

yeah I tried that it didnt work but I found a workaround

Building stand-alone with a VST plugin