Das ist schlecht. Jetzt so aus dem Hut, ohne das am Rechner kontrollieren zu können:
Gibt es nicht auch noch einen VST Plugins-Ordner direkt unter ....\Steinberg - also dem übergeordneten Ordner vor Cubase 7? Da würd ich´s dann auch noch mal probieren.
Darüber hinaus: Du hast offensichtlich ein 64 bit Betriebssystem. Hast Du das PlugIn hoffentlich auch in der 64 bit-Version?
Aus der XLN Knowledgebase:
-------------------------------------------
VST on Windows2012-07-05 11:55
If you have a VST host on Windows, and your plugin is not showing up, this information might come in handy. (The below refers to any VST plugins, not just ours)
Background:
In OSX all VST plugins are always installed in the same folder, and the same plugin file contains both the 32 and 64 bit version. Platform wars aside, that is a very clean solution.
On Windows the situation is different, and it is unfortunately a bit messy:
- VST plugins can be installed in any folder, and you can have several VST folders if you like. This means that your host (Cubase, Reaper, Live etc) needs to be told where to look for them. This is usually done by adding "VST paths" in some preferences window, and
performing a "re-scan plugins" action.
On 64 bit Windows there are additional issues:
- 32 and 64 bit versions are 2 separate files, usually with the same name, meaning they need to be in separate folders.
- if you have a 64 bit system and want to run the 64 bit version, but have both 32 and 64 bit versions of the same plugin installed, the host may be confused about which one to load. For instance, Cubase uses whichever one it finds first when scanning (come on, Steinberg..).
Where should plugins go?
There is no strict standard saying where 3rd party developers like us should install our plugins as default. In your computer's Registry, there is a Key ("Software/VST Path") that we check, and if it is found we will install to what it says. If we find a previous XLN installation in the Registry, we will install to the paths provided there.
If no keys are found (fresh installation), we go with what Steinberg (inventors of VST) used to say: "C:\Program Files\Steinberg\VSTplugins". Unfortunately, many versions of Steinberg's Cubase itself did not include that folder in the list of folders to scan, resulting in users not seeing their plugins in their plugin list.
To summarize: either the plugins should be installed where your host is looking for them - or your host should look where your plugins are installed!
Can't I just move the plugin after install?
Although you can move your VST plugins to the folder you want after installation, this can cause trouble: an uninstaller won't be able to remove it and an updater will not be able to overwrite it, resulting in possibly non-functioning installations. Not recommended (unless we're talking small free plugins (yay KVRaudio.com!) that may not even come with a proper installer)
Suggested solution:
-
Keep your 32 bit VSTs in one folder, and your 64 bit VSTs in another. Everytime you install a new plugin, choose those folders.
- Add these VST path(s) in your host. If you're on a 64 bit Windows, add the 64 bit path first, to make sure it is scanned first.
- Don't move plugins manually after installation!
- For XLN Audio products: Use the "Advanced" page in the Online Installer to move the XLN Audio VST plugins to the location of your choice.
-------------------------------------------
Also ggf. 64er downloaden (
http://www.xlnaudio.com/api/download/95) und nochmal neu installieren.
(June 2012: The 64 bit Windows version of AD is released. Just go to xlnaudio.com/install to download the Online Installer (if you haven't already), which will install AD 1.5.3 (or later) VST in both 32 and 64 bit versions. Please note that you can specify/move your desired VST paths in the 'Advanced' tab in the Online Installer, making sure they are always updated correctly. And make sure your host scans those folder so it finds the plugins).
.
Bräuchten wir daher sicher nicht nochmal da vortragen. Aber trotzdem danke.
