![]() ![]() That page instructs " In all cases mentioned above, a logic and clean folder organization will allow you to reliably bridge where needed and get rid of the additional software when the need for a bridge no longer exists." Generally speaking, as Steinberg created the VST plugin standard, I find it best to use their directories that get created when you install a Steinberg product like Cubase or Nuendo:Ĭ:\Program Files (x86)\Steinberg\VstPluginsĪs of now, Steinberg includes their own 32bit to 64bit VST bridge in modern versions of Cubase (to bridge old 32bit binary plugins to work in 64bit Cubase), and also has a documentation page here that discusses this concern and your options. Many installers default back to something like C:\Program Files(x86)\Vstplugins in the absense of one defined by the Registry or when none exists. However not all installers USE this path, which is why it's important as the computer operator to know your system and your common install directories for applications that are important to you. Ok so, now we know we can define a registry key and most installers MAY pick that up. Since companies presume you've already installed a bunch of content, when you come along later and now install some other DAW/Sequencer, it tends to continue to try to use that same registry key. If this key didn't exist, it was created by most apps (including Sonar as you mentioned). Then companies improved in terms of stability/compatibility with 3rd party VST plugins (there's many! lots to debug) and most added a feature to let you 'point to' an additional VST plugins directory.Īt that point, it became common to 'look up' the plugin folder location in the registry at the key that Steinberg was setting. In years past, you would install them to your steinberg plugin folder (assuming you had a steinberg app installed) and then copy the ones that worked in other programs to that application's subfolder for vstplugins (Ableton Live, Renoise, Sonar etc). Unfortunately, there's no 100% standard for installing VST plugins. Scope doesn't support XTC mode in any of its current iterations, and so this information isn't really relevant to a Scope forum, but I'm loathe to spend several minutes doing something and not make future use of that time (if possible) so I'm replicating this information here for others who may need it:įirst off, on 64bit versions of windows, you'll find 2 program files directories:Ĭ:\Program Files\ << This is for 64bit (memory addressing range) binariesĬ:\Program Files(x86)\ << This is for 32bit (memory addressing range) binaries Having written this up for another poster, I'm going to replicate the information below and add a disclaimer to USE THIS INFORMATION AT YOUR OWN RISK.
0 Comments
Leave a Reply. |