![]() Therefore, moving a plug-in from one folder to a different folder can render it unusable. ![]() Apart from that, the original installation path might be stored in the registry of Windows. Plug-ins can consist of several files on the hard disk and might be spread over several folders. In Cubase and Nuendo, the list of monitored VST2 folders can be managed here: Cubase 8/Nuendo 7ĭevices > Plug-in Manager > Plug-in Manager Settings (click on gear symbol)ĭevices > Plug-in Information > VST Plug-ins > VST 2.x Plug-in Paths In any case, remember that your VST host application must know the installation paths of your VST2 plug-ins. ![]() FormatĬ:\Program Files\Common Files\Steinberg\VST2ģ2-bit plug-ins on 64-bit Windows: C:\Program Files (x86)\Steinberg\VstPlugins Depending on the program version, these folders are the default VST2 folders in Cubase and Nuendo. The following chart includes other common VST2 paths. But, to keep plug-in installations independent from a specific VST host release, never install plug-ins into the program folder of the VST host application or any other program! Since it corresponds to the defined VST3 plug-in folder, this path is a good choice for all VST2 plug-ins:ģ2-bit plug-ins on 64-bit Windows: C:\Program Files (x86)\Common Files\VST2Īny other folder your VST host application is scanning during startup by default is also suitable. ![]() To prevent a plug-in mess, it is recommended to decide on a single installation folder for all VST2 plug-ins and stick with it as far as possible. In general, it's not easy for users to keep track of their VST2 plug-ins, which is why VST plug-ins installations often are all over the place even on well-maintained Windows systems. Since then, many different plug-in manufacturers used many different folders. The original installation path used when VST had been introduced in 1996 is C:\Program Files\Steinberg\VSTPlugins. In this case, only the documentation can tell you where to find the plug-in. But VST2 plug-ins can also have a fixed installation path predefined by the manufacturer. All your VST3 plug-ins should be installed here: Formatģ2-bit VST3 plug-ins on 64-bit Windows: C:\Program Files (x86)\Common Files\VST3Īs the VST2 standard does not know a dedicated installation folder, VST2 plug-in installers usually let the user select an installation path. The VST3 format has a dedicated installation path all VST3 plug-ins must comply with. The installation path of a plug-in depends on several factors: It's really just the VSTplugins folder that's giving me issues because I have a lot of plugins to reinstall, and I keep needing to redirect the VST installs, to what actually should ordinarily be the default location, but I done goofed and accidentally told windows the default was something different.An installed plug-in is missing in your VST host application or you just wonder where your VST plug-ins (virtual instruments and effects) are located? This article provides detailed information on VST plug-in installation paths on Windows.Ĭlick here to switch to VST plug-in locations on Mac OS X and macOS.Ĭlick here to switch to Locations of internal Cubase and Nuendo plug-ins.įirst of all, it is important to understand that not all VST plug-ins are being installed into the same folder. ![]() I wouldn't change the default in the registry if it exists, it's just asking for trouble when you have to deal with installing non-VST applications and so on because the registry setting knows or cares nothing about VSTs, only that something is being installed as if it were a program. The installer in most cases should ask you this, first the metadata location, then where you want the actual VST. so it's better to properly direct the installer to both locations during the install and chances are the program files location for most meta data is fine, or your own apps directory if you want to move it but you really should keep them separate. Then there is the location of the actual plugin VST/DLL. There are two install locations, metadata such as presets, settings, manuals and so on, those do NOT go into the same directory as the plugin or you'll end up with the dreaded "Reaper takes forever to scan plugins" problem. Installers assume Program Files by default but that isn't the real issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |