Skip to guide
← Tool guides

Audio, explained · 35 / 36

VST Plugin

Use a compatible installed x64 VST effect in an isolated worker.

Visual walkthrough2 configuration controlsAnimated walkthrough
See how it works ↓

An effect processes the branch through its isolated worker. A failed processor on protected voice produces silence until deliberate recovery.

01 / Understand

The idea, before the settings.

Each plugin defines its own automatable controls; scanning discovers metadata, while adding and preparing a plugin is a separate action.

SourceChosen VST effectMeter → Output

Use it in AudioRouter

  1. Scan an explicitly chosen installed x64 plugin directory and inspect a supported result.
  2. Add the intended exact plugin to the draft and wire it into the branch.
  3. Save and Play, then verify plugin running telemetry and the downstream meter.
  4. Use the plugin-defined parameter ranges and matched-level Bypass comparisons.

What success looks like

The chosen plugin identity and its own parameter metadata determine the controls. A scan result alone does not prove successful live processing.

If it does not work

If it faults, inspect the error and recover deliberately. Protected voice paths remain silent rather than silently bypassing a failed processor.

Select the node to open Properties. Click its name to rename it. While playing, supported parameter-only edits save after a short pause. For structural edits, use Save when the canvas marks a change. Enabled and Bypass are distinct live controls; see the in-app help for their behavior.

02 / Explore

Make the behavior visible.

A generic website sound cannot demonstrate an arbitrary installed plugin. This page uses a visual lifecycle explanation and teaches how to verify the real effect.

This animated diagram is conceptual. It is not a DSP measurement or control for your running AudioRouter session.

03 / Configure

Every control, with a reason.

01

Scanned plugin

path

Scan an explicitly chosen absolute directory, inspect a supported result, then Add to draft. The selected exact binary identity is preserved.

Range / choicesDepends on your selectionDefaultChoose explicitly

Try thisScan your installed x64 VST3 directory and add the intended effect.

Keep in mind Compatibility labels are not a guarantee every plugin works. x64 VST2 remains qualification-gated.

02

Plugin-provided parameter title

pluginParameter:<parameterId>

The scanned plugin provides each title, minimum, maximum and default. The inspector offers a slider and precise value with a 0.001 step.

Range / choicesDepends on your selectionDefaultChoose explicitly

Try thisAdjust the plugin-defined threshold control using the range returned for that exact plugin.

Keep in mind No universal parameter ranges or physical units can be assumed. Some plugins expose no automatable parameters.

04 / Put it to work

Start with a useful example.

Example 1

Add one effect safely

  1. Scan the explicit installed plugin directory.
  2. Inspect a supported result and Add to draft.
  3. Wire it into the intended branch, Save, then check running telemetry and the output meter.
Example 2

Compare with the dry route

  1. Use Bypass for a deliberate dry comparison.
  2. Match perceived loudness before judging the result.
  3. If the plugin faults, inspect the error and recover deliberately.

These are starting points. Compare at a comfortable monitoring level and adjust for your own source.

05 / Get unstuck

Small details that matter.

  • Scan completion does not mean plugin code has been loaded or has processed audio.
  • A running session can contain a silent failed plugin path.
  • Do not use another plugin’s values as though parameter IDs or scales were shared.