File - VST Settings

Figure 343. 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:

VST Scan Paths

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 Music Creator.

To add folders, remove folders, or set defaults for the listed folders, use the following buttons:

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.

Scan Options

This group of commands controls the following options:

Specify when to scan for new VST plug-ins. The options are as follows:

Automatic Background Scan. Music Creator 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 Music Creator. 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 existing 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. 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.

VST3 Migration

Hide Related VST2 Plug-ins. If you have both VST2 and VST3 versions of a plug-in, you can instruct Music Creator to automatically hide any redundant VST2 plug-ins from Music Creator’s plug-in menus.

Replace VST2 Plug-ins When Opening Projects. If you have both VST2 and VST3 versions of a plug-in, you can instruct Music Creator to automatically upgrade to the VST3 version when loading a project that uses VST2 plug-ins.

There are a few permutations for how VST plug-ins are substituted depending on whether you are loading in Music Creator X86 or X64 and the chosen VST2 to VST3 migration flag settings.

The following table shows the expected plug-in substitution results when opening projects containing VST plug-ins.

 

Table 214. VST2 to VST3 migration  

Source	Music Creator x86 (32-bit)		Music Creator x64 (64-bit)
	Replace VST2 Plug-ins When Opening Projects enabled	Replace VST2 Plug-ins When Opening Projects disabled	Replace VST2 Plug-ins When Opening Projects enabled	Replace VST2 Plug-ins When Opening Projects disabled
VST2	Use 32-bit VST3, if available, otherwise use 32-bit VST2	Use 32-bit VST2	Use 64-bit VST3, if available, otherwise use 64-bit or 32-bit VST2 as available	Use 64-bit or 32-bit VST2 as available
VST3	Use 32-bit VST3	Use 32-bit VST3	Use 64-bit VST3	Use 64-bit VST3

BitBridge Server Configuration

Cakewalk’s BitBridge technology allows you to use 32-bit VST effects and instruments when using the x64 version of Music Creator.

By default, Music Creator 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 Music Creator's automatic memory management. This also applies when you load a project that contains VST plug-ins.

Tip: To more optimally use your available memory, assign memory hungry VSTs to their own private BitBridge server. The actual memory consumed by a server instance is shown in the server list, allowing you choose which server you may want to load into.

Custom server assignments are saved with the project file.

Note: Server management is common for all loaded projects. If you have multiple projects open simultaneously, you can potentially overflow the 4GB capacity of a server if the projects reference the same server. Under this condition, a plug-in may fail to load. If this occurs, close the current project before opening another project.

Tip: To open a BitBridge plug-ins preset window in addition to its UI, hold down the ALT key and click the BitBridge plug-in in an FX Rack.

General

Recycle Plug-in Windows. By default, Music Creator 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 Music Creator 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. 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.

 

See also:

Preferences dialog

File - Folder Locations

File - Audio Data

File - Advanced