Figure 3171. The VST Settings section.The VST Settings section lets you manage VST effect and instrument plug-ins.The VST Settings section contains the following settings:This window lists the folders that are scanned for VST plug-ins. “Scanning” a VST plug-in means adapting the plug-in’s file format so that the plug-in works in Cakewalk.
Add. This button opens the Browse for Folder dialog box, which allows you to select a new folder to be scanned.
Remove. To remove a folder from the to-be-scanned list, first select the folder, and then click the Remove button.
Automatic Background Scan. Cakewalk automatically scans the folders in the VST Scan Paths list in the background by periodically detecting when data in the folders have been updated, or the scan paths have changed.
Scan On Startup. The folders listed in the VST Scan Paths list are searched for new plug-ins whenever you start Cakewalk. Scanning occurs in the background.
Manual Scan. The folders listed in the VST Scan Paths list are searched for new plug-ins when you click the Scan button.
Rescan Failed Plug-Ins. Checking this option causes any plug-in(s) that didn’t scan correctly to be rescanned during the next scan.
Rescan All Plug-Ins. Checking this option causes plug-in(s) that did scan correctly to be rescanned during the next scan. This is a way to implement any changes you’ve made to the Folder defaults settings.
Scan in Sandbox. Scan each plug-in within a private scanner process. While this is slightly slower, it is more robust and prevents plug-ins from corrupting or stopping the scanning process.
Generate Scan Log. Log the VST scanning progress to %APPDATA%\Cakewalk\Logs\VstScan.log. This can be useful to troubleshoot problems when plug-ins fail to scan properly.
Note: Logging is intended for diagnostic purposes, and can have overhead. Generate Scan Log should only be enabled if instructed by BandLab technical support.
Scan. Click this button to immediately scan the folders listed in the VST Scan Paths list.
Reset. Click this button to remove all scanning records and settings from all your VST plug-ins. Use this button if you want to completely start over.
Hide Related VST2 Plug-Ins. If you have both VST2 and VST3 versions of a plug-in, you can instruct Cakewalk to automatically hide any redundant VST2 plug-ins from Cakewalk’s plug-in menus.
Replace If Possible on Project Load. If you have both VST2 and VST3 versions of a plug-in, you can instruct Cakewalk to automatically upgrade to the VST3 version when loading a project that uses VST2 plug-ins.The following table shows the expected plug-in substitution results when opening projects containing VST plug-ins.
Table 578. VST2 to VST3 migration Cakewalk’s BitBridge technology allows you to use 32-bit VST effects and instruments when using the x64 version of Cakewalk.32-bit VST effects and instruments are loaded into “servers”, and each server can address up to 4GB of RAM. BitBridge supports up to 32 independent plug-in servers, and each server can address up to 4GB of RAM, allowing access to a massive 128GB of RAM. This allows Cakewalk x64 to address all available RAM in your computer.By default, Cakewalk manages memory automatically, and will allocate and allow access to all available RAM dynamically as plug-in's are used. This is done by dynamically creating new BitBridge servers only when necessary, up to a maximum of the available RAM.Server loading is either automatic or customizable, giving you full control over which server to load plug-ins into. To enable automatic server loading, select Automatic (Based on available RAM). To manually manage BitBridge servers, select the server that you want plug-ins to be loaded into.After a specific server is selected, all plug-ins subsequently loaded will be loaded into that specific server, bypassing Cakewalk's automatic memory management. This also applies when you load a project that contains VST plug-ins.
Recycle Plug-In Windows. By default, Cakewalk recycles the currently-open plug-in window when you open a new plug-in UI, and all previously open plug-in windows are closed. This prevents Cakewalk from being filled with numerous open plug-in windows, and you don’t have to manually close plug-in windows that are no longer needed.If you prefer to always open a separate window for each plug-in, clear the Recycle Plug-In Windows check box.
If Recycle Plug-In Windows is enabled when you hold down the CTRL key to open a plug-in, all other open plug-in widows also become pinned.
If Recycle Plug-In Windows is disabled when you hold down the CTRL key to open a plug-in, all other open plug-in widows close, and the new plug-in window is unpinned.You can also pin individual plug-in windows so they remain open when you open another plug-in window. To do so, click the Pin Plug-In Window button on the plug-in property page.
Note: Plug-ins that are docked in the MultiDock are not affected by the Recycle Plug-In Windows setting. Docked plug-ins are automatically pinned and cannot be unpinned. To dock a plug-in window, hold down the CTRL key and drag the window to the MultiDock.
Tip - Searching Documentation
Tip: To search for a specific topic, type your search query in the Search Cakewalk.com field at the top right of this page.
When the search results appear, click which product's documentation you would like to search to filter the search results further.
Note - Using Offline Help
Note: If you prefer to always use offline Help, go to Edit > Preferences > File > Advanced in your Cakewalk software and select Always Use Offline Help.
If you are not connected to the internet, your Cakewalk software will default to showing offline help until an internet connection becomes available.