2.7. Plugins (LADSPA)

Since release 3.70 terminatorX supports LADSPA-plugins. LADSPA is the "Linux Audio Developer's Simple Plugin API" which was designed by developers on the Linux-Audio-Developer-Mailinglist and is maintained by Richard W.E. Furse. For more information on LADSPA, other LADSPA-hosts and LADSPA-plugins checkout the LADSPA homepage.

Not every plugin is supported by terminatorX though. As the plugins are inserted into the per-turntable effect-queue, they have to be mono plugins (as is that queue) for now. This is why terminatorX will load plugins with one audio-in port and one audio-out port only.

The decision on wether a plugin is terminatorX-suitable is made on terminatorX startup, so only plugins that fit into the effect queue will be offered in the plugin-menu that pops up when the FX button is clicked. On startup terminatorX will print some information on the LADSPA-plugins analysis process to the standard output. Watch the terminal you run terminatorX from for that info if you have problems loading a plugin.

As specified in the LADSPA-standard LADSPA-plugins can be located in multiple directories across the filesystem. To enable LADSPA-hosts to find those plugins you have to set the environment variable LADSPA_PATH accordingly. Let's say you store your plugins in /usr/lib/ladspa and /home/yourlogin/plugins then you would have to set:

LADSPA_PATH= /usr/lib/ladspa:/home/yourlogin/plugins

As a fallback terminatorX will look in the standard directories /usr/lib/ladspa and /usr/local/lib/ladspa if the environment variable is not set. Note that this is just a convenience-function, in order for other LADSPA-hosts to work properly, be sure to set your LADSPA_PATH correctly. It is a good idea to do that from somewhere in your system configuration (either in your rc-scripts or /etc/profile or whereever you perefer).