Cakewalk // Documentation // Cakewalk // File - VST Settings
Table of Contents Previous Next Index

Dialog box referencePreferences dialog ► File - VST Settings

The VST Settings section lets you manage VST effect and instrument plug-ins.
The VST Settings section contains the following settings:
*
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.
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.
*
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 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.
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.
Copyright © 2019 Cakewalk, Inc. All rights reserved
Sitemap | Privacy Policy | Legal