Does Ecasound Support 64-Bit LADSPA Plugins?

Ecasound fully supports LADSPA plugins compiled for 64-bit architectures, provided that the Ecasound binary itself is also compiled as a 64-bit application. This guide explains how 64-bit LADSPA integration works within Ecasound, the environment requirements for proper operation, and how to verify that your plugins are recognized correctly.

Architecture Matching and Compatibility

In Linux and Unix-like operating systems, dynamic shared libraries (.so files) must match the binary architecture of the host process. Because LADSPA plugins are shared object files, a 64-bit version of Ecasound can only load 64-bit LADSPA plugins. Modern 64-bit Linux distributions (such as Ubuntu, Debian, Fedora, and Arch) provide 64-bit builds of both Ecasound and common LADSPA plugin packages (like CMT, SWH, and TAP) by default, making them compatible out of the box.

Attempting to load a 32-bit LADSPA plugin into a 64-bit Ecasound binary will fail due to binary format incompatibility.

Configuring the Plugin Path

To ensure Ecasound locates your 64-bit plugins, the directory containing the .so files must be defined in your environment. Typically, 64-bit plugins reside in /usr/lib/ladspa, /usr/lib64/ladspa, or /usr/local/lib/ladspa.

You can define the search directory using the LADSPA_PATH environment variable:

export LADSPA_PATH=/usr/lib/ladspa:/usr/lib64/ladspa

Verifying 64-Bit LADSPA Support

You can verify that Ecasound detects your 64-bit plugins using the interactive mode or command-line query tools.

  1. Check plugin discovery in Ecasound: Run the following command to display all recognized LADSPA effects:

    ecasound -el

    If your 64-bit plugins appear in the list, Ecasound has loaded them successfully.

  2. Verify the plugin architecture: If a plugin fails to load, inspect the binary architecture of the plugin file using the file utility:

    file /usr/lib/ladspa/plugin_name.so

    The output should confirm ELF 64-bit LSB shared object matching your system's architecture (e.g., x86-64 or aarch64).

Using 64-Bit LADSPA Plugins in Chainset Commands

Once identified, plugins are invoked in Ecasound processing chains using the -el (enable LADSPA) operator followed by the plugin's unique label or numeric identifier and its required parameters:

ecasound -i input.wav -el:amp_mono,2.0 -o output.wav

As long as the host application and the dynamic libraries share the same 64-bit compilation target, Ecasound will process LADSPA effects with native 64-bit performance and memory addressing capabilities.