The LSP project is an open-source project and cares about quality of developed software.

Still there is no absolute warranty about stability of the software on different platforms, so you're using this software on your own risk.

Unless many commercial or proprietary projects, LSP project does not sell license keys or offer technical support for enterprise solutions.

Binary distribution

You may download the latest release from

Download LSP Plugins

You also may view all previous releases here.

Source code

Source code is accessible from GIT repository at

You may stimulate development of plugins by subscribing or donating the project.

Because project needs regular support, small bounty subscription is much more preferred rather than huge but one-time donation.


You may build plugins from scratch.

For successful build you need the following packages to be installed:

Currently there is no automake/CMake supported, so to build plugins you have to type:

make clean
make install

By default, all supported formats of plugins are built. You may control list of built plugin formats by specifying BUILD_MODULES variable:

make clean
make BUILD_MODULES='lv2 vst doc'
make install

Available modules are:

Also possible (but not recommended) to specify compile targets:

make clean
make build_ladspa
make build_lv2
make build_vst
make build_jack
make build_doc

By default plugins use '/usr/local' path as installation directory. To override this path, you can run build with specifying PREFIX variable:

make clean
make PREFIX=/usr
make install

By default, 'make install' will install all plugin formats (LADSPA, LV2, LinuxVST, JACK) and documentation. To install them separately, you can issue following commands:

make clean
make install_ladspa
make install_lv2
make install_vst
make install_jack
make install_doc

To build binaries for debugging/profiling, use the following commands:

make clean
make profile

To build binaries for testing (developers only), use the following commands:

make clean
make test

To build both release binaries and binaries for testing, use the following commands:

make clean
make all test

After issuing this command, the system will build release binaries into '.build' subdirectory and test binaries into '.test' subdirectory

You may also specify the installation root by specifying DESTDIR attribute:

make install DESTDIR=<installation-root>

To perform cross-building between different architectures, you first should have a corresponding toolchain. By default, LSP plugins use 'uname' tool for detecting target architecture and set internal variable BUILD_PROFILE to the detected value. Currently supported values are 'x86_64', 'i586', 'armv7a'. To build plugins for another architecture, just issue following commands:

make clean
make BUILD_PROFILE=<target architecture>

To automatically build tarballs with binaries, you may use 'release' target:

make clean
make release

After issuing these commands, '.release' subdirectory will contain tarballs with binaries, documentation and sources. To perform release for another architecture, same way with BUILD_PROFILE is possible:

make clean
make BUILD_PROFILE=<target architecture> release

To remove all previsously built tarballs, just issue:

make unrelease 

System requirements

Current matrix of hardware architecture and platform (OS) support is:

│Arch / OS  │ GNU/Linux │ FreeBSD │
│i586       │     F     │    E    │
│x86_64     │     F     │    E    │
│armv6-a    │     E     │    E    │
│armv7-ar   │     E     │    E    │
│aarch64    │     E     │    U    │
│ppc64      │     C     │    U    │
│s390x      │     C     │    U    │

  F - Full support.
  C - The code does compile, not enough knowledge about it's correct work.
  E - Experimental support, not enough feedback from users.
  U - Unknown, the code may be built but the correctness of it's work has not been tested.
  N - No support, the code may compile but the work has not been tested.

Details about architectures supported in experimental mode:

Supported plugin formats:

The LADSPA distribution requirements:

The LV2 distribution requirements:

The LinuxVST distribution requirements:

The JACK distribution requirements:

The profiling distribution requirements:

Known list of supported plugin hosts: