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|:

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|:

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|:

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

ExcludeEffects

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.

ExcludeEffectFiles

Lists VST, VST3, or DLL filter (effect) files that the audio editor should not load. This helps avoid loading problematic effect files when a user or administrator has installed a large bundle of effects.

For System Administrators or Power Users managing MTE/MultiRec installations, this parameter provides the ability to completely bypass specific files during the initial startup scan using a filename-based exclusion list.

How It Differs from ExcludeEffects

• ExcludeEffects (Metadata-based): Filters based on the internal name of the effect (e.g., “Oxford EQ Native”). Because of this, MTE must first open and scan the physical file to read its metadata before it can decide to hide it. This opening action triggers hardware dongle checks and license windows, causing startup delays and user interruptions.

• ExcludeEffectFiles (File-based): Filters strictly by the physical filename on the disk. When a file is listed here, the MultiRec scanner ignores it entirely—it will not be opened, and no metadata (name, version, vendor) will be read.

Key Benefits

• Prevents License Pop-ups: Stops automated license activation prompts (like iLok) or copyright dialogs from interrupting the user experience and forcing users to manually click "Cancel" or "Close" during application startup when a license is missing or unavailable.

• Increases Stability: Allows known corrupt, unstable, or incompatible VST3 or DLL files to be completely bypassed before they can cause a startup crash.

• Improves Deployment Flexibility: Allows specific plugins to be easily "silenced" via central configuration rather than requiring a physical uninstallation across workstations.

Configuration Format

The data in this parameter is a list of file names, separated by semicolons or line breaks.

• Each entry must contain the raw filename and extension.

• Optional: It can contain the tail part of its directory path so that the exclusion targets a specific version or folder location only.

• Unlike ExcludeEffects, upper/lower case is not significant for this parameter.

Requirements: This parameter only works with MTE 8.5.1877.0 or newer and MultiRec 4.10.366.0 or newer.