![]() ![]() So, by using the C:\vst folder, elevated privileges will not be needed, then you have all 3rd party VST2 format VST's in one location, some installers insist on placing the dll's in "C:\Program Files\Steinberg" why? I have no idea, but if you can, always install 3rd party VST's including VSTi's into a folder on "C:\vst", I use the 'vst' location as an example, it can be named whatever you want, as long as it's added to the list of CbB plugin locations, by going to:- Utilities->Cakewalk Plug-In Manager, then click on 'Options' then click on 'Add' then navigate to where the 3rd party VST's are located.We are making the software completely free to use to ensure that anyone, regardless of their resources, technology or stage in their career, can have access to the highest level of professional music production tools. This is part of our ongoing effort to empower musicians to make and share their music around the world. Professional products like Cakewalk are essential to those who make their living in music production and the natural next step for musicians who use platforms like BandLab to simplify their creative and collaborative process. ![]() Wil my experience, I had to create a folder in the C root EG: "C\vst" and install ALL 3rd party VST's there, then add that location to CbB plugin options, then do a scan, this is because some 3rd party VST's create a data folder and if the VST is placed in the default CbB vst folder "C:\Program Files\Cakewalk\VstPlugins", then when CbB scans the folder and detects the new VST's, the scan initiates the VST to create a data folder that contains modules for various instruments, but windows will NOT allow this unless the scanning module has elevated privileges, IE admin access, and will cause an error pop up showing that modules are not available, etc etc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |