Set Vst Plugin Paths

Posted on by

You can manage your effects and VST instruments in the Plug-in Manager window.

  1. Free Trap Vst Plugins
  2. Set Vst Plugin Paths Plugin
  3. New Free Vst Plugins
  4. Add Area Path Vsts

Open the plug-in manager and click ‘VST 2.x Plug-in Paths’. Click Add, and navigate to the location that the plug-in file is on your hard drive (default paths previously listed). Finally, in the main page of the plugin manager, click Update and your Toontrack plug-ins should appear under the found plug-ins. Set the default Steinberg VST plugins path The setVSTpath application was designed to be a small utility to set the default Steinberg VST plugins path. Install setVSTpath by copying the.

  • To open the Plug-in Manager window, select Devices > Plug-in Manager.

The Plug-in Manager window shows the following:

VST Effects

This tab lists all VST effects that are loaded in Cubase. You can sort the list by name, vendor, category, etc. by clicking the corresponding column heading.

VST Instruments

This tab lists all VST instruments that are loaded in Cubase. You can sort the list by name, vendor, category, etc. by clicking the corresponding column heading.

Blacklist

This tab lists all VST effects and VST instruments that are installed on your system but not loaded in Cubase. These plug-ins might lead to stability problems or even cause the program to crash. As Cubase does not support 32-bit, all 32-bit plug-ins are shown in this list.

Note

You can reactivate a blacklisted 64-bit plug-in by selecting it and clicking Reactivate. This causes Cubase to rescan the plug-in and remove it from the blacklist. To move the plug-in back to the blacklist, you must rescan all plug-ins and restart Cubase.

Collection list

By default, the window section to the right shows the Default collection, which contains all effects or VST instruments loaded by the program. The Default collection cannot be changed.

You can compile your own collections of effects or VST instruments by clicking New Collection and dragging and dropping items from the list of all effects or VST instruments to the collection list.

Plugins

Collections are shown in the selectors for effects/VST instruments, and all changes made to collections in the Plug-in Manager are immediately reflected in the selectors.

Search Field

Enter the name of a plug-in in the search field. The list of all effects or VST instruments is filtered to show only those plug-ins whose names contain the text that you entered.

Toggle list to show all/show only FX/VSTi not in current collection

Allows you to filter the lists of all effects or VST instruments to show either all loaded plug-ins, or only those that are not part of the current collection.

New Folder

Allows you to create a new folder in the current collection.

Delete

Allows you to delete the selected item in the current collection.

New Collection

Allows you to create a new collection.

To create a new, empty list, select Empty. To create a new collection based on the list of all effect, select Add All Plug-ins. To create a new collection based on the current collection, select Add Current Collection.

User Collections

Allows you to select a different collection, and to rename or delete the current collection.

To remove unavailable plug-ins from all collections, select Remove Unavailable Plug-ins from All Collections.

Show Plug-in Information

Opens a section at the bottom of the window in which more information about the selected item is shown. If you select several plug-ins, the information for the plug-in that you have selected first is shown. In this section, you can also deactivate selected plug-ins. Deactivated plug-ins are no longer available in collections. This is useful if you have plug-ins installed that you do not want to use in Cubase.

Plug-in Manager Settings

Opens a section at the bottom of the window in which all current paths to VST 2 plug-ins are listed. You can add or remove folder locations by using the corresponding buttons. Click Rescan All to rescan your computer for plug-ins.

It's been a long time coming, but Cantabile now supports VST 3 plugins!

At this stage, this should be considered experimental and is still under testing but it's basically working and certainly good enough for an early access release.

Build 3616 introduces:

  • VST 3 plugin hosting support.
  • New preset model support.
  • New VST path options UI in Options -> Plugin Options.

Disclaimer

This build also introduces some file format changes which I haven't decided are final yet so:

  • Don't run this build until you've backed up all your Cantabile song, rack and set list files.
  • Don't use this build for live performance.
  • Everything in this build is subject to change and files saved by this build might not be loadable in future builds.

Using VST 3 Plugins

There's nothing special about using VST 3 plugins in Cantabile.

VST 3 defines a standard folder to which plugins should be installed however Cantabile requires you to explicitly include this path in your VST search path:

C:Program FilesCommon FilesVST 3

Cantabile will add this folder to the VST path on first run so this should just work and your VST 3 plugins should automatically show up in the Insert Plugin window.

If you don't have Cantabile configured to re-scan plugin folders on startup you'll need to run Tools -> Scan Plugin Folders (Quick) once to pick up the VST 3 plugins.

The second column of the Insert Plugin window now includes an indicator of whether the plugin is VST 2 or 3:

Upgrading VST 2 Plugin Instances to VST 3

You can upgrade an existing VST 2 plugin instance and maintain the plugin's configuration:

  1. Right click on the plugin slot in Cantabile's main window.
  2. Choose 'Upgrade Plugin...'

If the command is disabled it means the plugin doesn't support upgrading. If the command is enabled but it fails it means the plugin says it supports upgrading, but doesn't. In this case use Edit -> Undo to revert to the VST 2 instance.

After upgrading a VST 2 to VST 3, you may need to tweak its incoming and outgoing routes. For VST 3 plugins the names of the plugins ports are derived from the bus names of the plugin and probably won't match the old names generated by Cantabile.

(Note: this post has been updated to reflect recent changes to the above user-interface. The previous method of using Replace Plugin to upgrade a plugin no longer applies and will now always replace the plugin and discard the previous state. To upgrade a plugin and maintain state you must use the new Upgrade Plugin command).

Plugin Information

You can now view detailed information about a plugin by right clicking and choosing 'Plugin Information':

New Preset Model Feature

Cantabile now supports 'Preset Models' which let you adjust the way presets work for a particular plugin.

For full details on this, see Preset Models in the guides.

New VST Plugin Path User Interface

Cantabile's user-interface for configuring the VST path has undergone some improvements.

Free Trap Vst Plugins

The old text field has been replaced with a check list and an 'Add' button lets you browse for a folder, type a folder path, paste a copied folder or choose from one of the standard VST path folders (if they exist).

You'll also notice buttons for re-ordering the list. The order of plugin paths is now significant and plugins in early folders in the list will be used in preference to later ones.

Finally, Cantabile now performs various checks on the selected folders to make sure they exist, that you don't have duplicates or folders that are sub-folders of others.

Set Vst Plugin Paths Plugin

Disabling VST 3 Support

If you're not ready, willing or able to start using VST 3 yet you can effectively disable support for it by removing (or unchecking) the VST 3 folders in Options -> Plugin Options.

New Free Vst Plugins

Please Report All Issues

Given the number of VST 3 plugins available it's impossible for me to test every one in Cantabile and I'm sure there will be cases where things don't work perfectly.

Add Area Path Vsts

Please report any issues including details on the plugin in question and I'll look into it. If something crashes and you're prompted to send a crash report, please click the Send button.

This is all available now in build 3616 - available here.