Can Ecasound Load Linux VST Plugins Directly?
Ecasound does not natively load Linux VST (LXVST) or VST3 plugins directly, as its built-in plugin architecture is restricted to LADSPA and its own native effect system. While Ecasound excels at multitrack recording, routing, and batch audio processing from the command line, using VST effects requires bridging mechanisms or external routing through the JACK Audio Connection Kit rather than native command-line arguments.
Ecasound's Native Plugin Architecture
Ecasound’s internal audio engine was designed around the Linux Audio
Developer's Simple Plugin API (LADSPA). Native plugin loading in
Ecasound relies on operators such as -el (to select an
effect) and -eli (to inspect plugin inputs and outputs).
These operators query directories defined by the
LADSPA_PATH environment variable and expect
.so files implementing the LADSPA specification.
Because Linux VST plugins utilize different interfaces, APIs, and parameter models, Ecasound's plugin loader cannot parse or execute VST binaries directly. Attempting to point Ecasound to a native Linux VST binary using standard effect flags will result in an initialization failure.
Workarounds for Using VST Plugins with Ecasound
Although direct loading is not supported, you can incorporate Linux VSTs into an Ecasound pipeline using external audio routing:
- Routing via JACK: The standard method for applying VST plugins to Ecasound chains is through the JACK Audio Connection Kit. Ecasound can output its signal to a JACK client, which routes the audio into a dedicated VST-capable host (such as Carla, Jalv, or Ardour), and then routes the processed signal back to an Ecasound input or a hardware output.
- Plugin Wrappers and Bridges: Some utilities act as LADSPA wrappers around VST plugins. If a bridge successfully exposes a VST through a valid LADSPA interface and descriptor, Ecasound can interact with the wrapper as if it were a standard LADSPA plugin. However, compatibility depends heavily on the specific bridge and whether the VST requires an active graphical user interface (GUI), which Ecasound does not support.
For standalone, headless operations inside Ecasound without external hosts, audio processing is restricted to internal effects and standard LADSPA plugins.