Windows installer: Detecting the VST plug-in directory is unstable

[Benjamin Klum]

One way to make it more stable would be to install the Playtime VST plugin into its very own directory (e.g. C:\Program Files\Playtime\VstPlugins\*.dll) and let the installer modify the REAPER VST plugin scanning path to pick it up.

This would prevent all sorts of possible annoyances:

• Installing Playtime into the wrong directory (e.g. a VST 3 directory)
• Error message when scanning Playtime with other DAWs (wouldn't happen anymore)
• 32-bit/64-bit conflicts

Questions:

• How does REAPER deal with existing Playtime DLL that is installed in the old VST directory? Will it prefer the latest one? Do I need to prepend or append to the VST plugin scanning path to let the new plugin have priority?

Side effects:

• Won't be automatically available anymore in freshly installed portable REAPER if VST standard paths have been used (portable Playtime should be used with portable REAPER)
• If REAPER app data is removed, REAPER won't find Playtime anymore (Playtime reinstall will solve that)

[Benjamin Klum]

re #313 Make Windows installer more predictable and easier to use

• User doesn't have to choose the VST directory anymore
• Playtime will always be installed into a fixed dedicated VST directory
• REAPER VST scanning path will be modified if necessary so the Playtime VstPlugins directory is the last one (last one has highest priority, so old installed versions are just ignored)

→ <<cset 0a8d73968875>>