DSP Robotics Support

I'm looking for an installer for a VST that will default to the user's VST folder. I understand it usually has a registry value:

HKLM\SOFTWARE\VST

Has anyone had success with any such installers?

It was working, but also FL studio now does not add it to the registry.

maybe this gives some insights:

http://www.kvraudio.com/forum/viewtopic ... 3&t=362555

I saw that KVR post and I've tried innoscript without alot of success yet.

We need a really good solution here for Flowstone.

I was using it in the past.. but the existance of that key depends on the DAW installer.
So many hosts (like FL that was saving as Default ../program files/ VST plugins..) now seems to not add that registry key.

So that key can works for many poeple (where the key exists) and for many not.

Also, if you do find the key, it may not always be correct...
For example, the user's current choice of software does not set the key, but an old software did this long ago. Also the host may allow multiple paths - e.g. Reaper allows any number of custom folders to be scanned. For example, my plugins are now all on a USB3 SSD drive, so that I can easily take them with me to another studio, or "quarantine" plugins that I am only testing - I don't want them on my C: drive!

I think the best that one can do reliably is to ask the user for a folder at install time, and know that at least the plugin's "internal" folder structure will be correct - with a default path suggested in the box if it can be found.

trogluddite wrote:Also, if you do find the key, it may not always be correct...
For example, the user's current choice of software does not set the key, but an old software did this long ago. Also the host may allow multiple paths - e.g. Reaper allows any number of custom folders to be scanned. For example, my plugins are now all on a USB3 SSD drive, so that I can easily take them with me to another studio, or "quarantine" plugins that I am only testing - I don't want them on my C: drive!

I think the best that one can do reliably is to ask the user for a folder at install time, and know that at least the plugin's "internal" folder structure will be correct - with a default path suggested in the box if it can be found.

Yes!
I do that. I prompt user for VST folder.
Other directories used from my plugins are instead decided by the installer and does not change (Documents, appdata etc etc).
This allow user to select VST destination, and if you need to store other data you can decide where place it.