My problem is simple: I like to use both the standalone AND the vst versions, but as of now they seem to be designed to function completely independent from each other. In some cases this might be useful, but in other cases this might be inconvenient, i.e. for usability reasons I'd prefer to have a shared installation but as of now I have to download, install and configure both versions separately.
I believe this might be doable now by simply copying the standalone folder over the vst one, but i see 2 problems with this:
1) I'm not sure that the config options would "merge", probably there would be some issues
2) This would have to be done within the VSTPlugins folder, which is suboptimal as it means to add a few hundred new files to that folder (hence slowing down plugin scanning for some hosts) including several non-plugin dll files (which also interfere with plugin scanning in some hosts and can even lead to crashes).
For all these reasons, I would suggest to implement the ability to "merge" both standalone and vst installations into one single folder, OUTSIDE the vstplugins folder. For example this might be easily done by implementing a simple .ini text file to go along with each usinevst dll (using the same filename as the dll). This file would include a path to the actual installation folder which could be anywhere, allowing:
a) to place only 2 files (the dll and the ini file) within the vstplugins folder
b) to have as many separate vst installations/setups as needed, by simply renaming the dll/ini file pairs and pointing the paths within the ini files to different folders.
I believe I've mentioned this before somewhere, but I felt like submitting it as an actual FR. It's just an idea and I totally understand that it might not be urgent or even desirable for other users, but anyway...
