Bug 181 - no choice for alternate vstplugins folder during install...
Summary: no choice for alternate vstplugins folder during install...
Status: CLOSED WORKSFORME
Alias: None
Product: LinuxSampler
Classification: Unclassified
Component: other (show other bugs)
Version: 0.5.1
Hardware: PC Mac OS X 10.7 (Lion)
: P5 blocker
Assignee: Christian Schoenebeck
URL:
Depends on:
Blocks:
 
Reported: 2012-05-28 07:32 CEST by earlyfirst
Modified: 2021-05-11 14:00 CEST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description earlyfirst 2012-05-28 07:32:16 CEST
Which in turn makes the plugin useless as ableton in all it's bullshit doesn't recognise it it merely moved to correct folder .. :(

I don't know perhaps the 20 mins I have spent with linux sampler is my problem ..
Comment 1 Christian Schoenebeck 2019-03-10 17:04:06 CET
The Windows installer automatically detects and installs the sampler's VST plugin into your common VST plugin directory.

If you don't have any VST host application installed on your Windows machine yet, then the LinuxSampler installer will install the VST plugin into Steinberg's default VST plugin directory which is "$PROGRAMFILES\Steinberg\VstPlugins".

However for the case you already have a VST host application installed, the LS installer will also check the Windows Registry for the following registry keys in this order:

1. HKCU "Software\VST" "VSTPluginPath"

2. HKLM "Software\VST" "VSTPluginPath"

These Windows registry keys are commonly set by VST host applications to specify that the default location for VST plugins has been overridden for some reason (e.g. by user request).

So in case your VST host application did not set one of these 2 registry keys, you still have the option to create them by yourself and then VST plugins (including the LS VST) will install into the appropriate VST directory desired by you.

Additionally all recent VST host applications support multiple VST plugin directories to be used simultaniously nowadays, so I don't think this is still an issue and will close this report.