VST Effects Configuration
Audio effects: Activate VST plugins
MTE provides an interface to include VST 2.4 and VST 3 effect Plugins by 3rd party distributors. To activate this feature open the DigaSystem Administrator and enter the following parameters in the path …|MultiTrack|Settings|:
Parameter | Description |
|---|---|
MultiRecVSTEffectsPath | Defines the path where MTE will search recursively for VST Plugin dlls (including subfolders) |
MultiRecVST3EffectsPath | Defines the path where MTE will search recursively for VST 3 Plugin dlls (including subfolders). By default all VST 3 plugins are installed to the %ProgramFiles(x86)%\Common Files\VST3 folder. |
UseVSTEffects | Set to 1 to activate the VST effects in the MultiTrack Editor |
The first MTE launch with the plugins will take more time than usual because the plugins need to be recognized and installed.
Define Preset Paths
All plugin preset-settings are saved into an xml file per plugin (also applies for non-VST plugins). To be able to use such presets you need to define the following parameters in the DigaSystem Administrator path …|MultiTrack|Settings|:
Parameter | Description |
|---|---|
AudioFilterPresetPath | Define a network path, so you can provide general presets for all machines. It is recommended to enter this parameter in the Global Settings. Then copy all preset files into this directory, manually. These presets cannot be changed or deleted by users |
LocalAudioFilterPresetPath | Define a local path for user specific presets that can be changed and deleted. |
To make a user specific preset available for all users, simply copy the xml files into the AudioFilterPresetPath. The xml files may have confusing file names, but the VST filter name should be mentioned in the file names.
Information about the plugins is cached in the file %alluserprofiles%\DigaSystem\MultiRec\Vst3FilterList.xml.
Configure the appearance of the plugin’s presets
Some but not all plugins have an own preset button that can be used to save the currently defined effect settings as a template. With these preset buttons you can load already existing presets, but you cannot create new presets or edit existing ones.
VST 2 plugins: To create or edit any templates use the Preset button that is provided by the MultiTrack Editor and is located in the effect window as well.
VST 3 plugins: Only user-defined presets are managed by MTE's "Preset" button in the plugin view's window title bar. Built-in presets must be loaded using the plugin's GUI. Of course you can load a built-in preset, and save it without any changes as a user-defined one.
The appearance of the presets menu items can be configured by setting the following parameter in the DigaSystem Administrator path …|MultiTrack|Settings|:
Parameter | Default Value | Description |
|---|---|---|
EffectPresetsMenu_Limit | (20;15;50) | Defines how the presets menu entries appear. To do so, the following specifications have to be made (n1;n2;n3). User and factory presets can be moved into sub menus of the "Presets" menu, if the total number of presets exceeds n1, or if the number of user or factory presets exceeds n2. You can force this changed behavior by setting n1 or n2 to 0. n3 defines the maximal number of entries per menu column. For example, with n3=10, a menu that has 12 entries would be broken into two columns of 10 and 2 items. |
MakeAllVst3WindowsResizable | 0 | If this is set to "1" or "TRUE", all VST3 plugin windows are resizable, even if the plugin doesn't say that it actually supports resizing. This is a work-around in situations, where the user wants to use faulty plugins, which report a wrong preferred size and/or a wrong "resizability" status. |
Audio Effects Waves Version 9 Plugins
If you would like to use the Version 9 effects of WAVES in the MultiTrack Page, enter the path of the file "WaveShell-VST 9.2.dll" (32bit variant) as value of the parameter "MultiRecVSTEffectsPath”. This file will make all installed plugins available for MTE. Further this file can be copied into another folder in case you already refer to additional plugins via this parameter.
Important! Some but not all plugins have an own preset button that can be used to save the currently defined effect settings as a template. With these preset buttons you can load already existing presets, but you cannot create new presets or edit existing ones!
Removing Effects from the Configuration
At times you may want to remove single effect plugins from the editor, for example because they are instable up to a point where they prevent MTE from starting, or because they unexpectedly pop up dialogs or other user interface elements. Rather than uninstalling the complete bundle of effects, you can set a parameter which removes just one effect, or a few effects, from MTE. These effects will be reated as though they didn’t exist in your system; MTE won’t offer them in the clipboard at all.
To remove effects from MTE, define the ExcludeEffects parameters at MutliTrack | Settings. This parameter takes a list of effect specifications, separated by semicolons or line breaks (to enter a line break using Digas Admin, press Ctrl+Enter). Each single specification takes one of the following forms:
The effect name, such as “CLA Nx Stereo”
The effect name and, separated by a vertical bar, its version number, such as “CLA Nx Stereo|16.0.23.24”
The effect name and, separated by a vertical bar, its version number, and, separated by another vertical bar, its vendor, such as “CLA Nx Stereo|16.0.23.24|Waves”
The effect name and, separated by two vertical bars, its vendor, such as “CLA Nx Stereo||Waves”
Note that you must observe exact spelling, including upper/lower case. Wildcards are not supported.
The MultiRec log file, when enabled, contains a log of all effects which MTE tries to load. If one of them crashes MTE, this one is contained in one of the last entries of the log file. It is a good idea to use the log file to copy effect names etc. and past them into the parameter as this save you the time to track down subtle errors like misreading a comma for a dot or a digit 0 for a letter O.
The ExcludeEffects pamater requires MTE version 8.4.1863.0 or above, and MultiRec version 4.8.349.0 or above.