This section contains a number of considerations, and some advice, for LADSPA hosts.
Of course, LADSPA hosts vary a lot more than the plugins, so we cannot specify a cookbook recipe.
Before trying to host LADSPA plugins, figure you what the limits of your host's support should be. Hopefully these guidelines will be of some value:
Hosts should obey the
LADSPA_PATH environment variable,
and may actively seek out plugins there.
Here is how the host should use a plugin:
instantiateto make each instance you want.
activateto prepare/clear the instance for use and call
connect_portfor each port (the host may run these in any order it wants).
run_addingas many times as you want. It may also run
connect_portmore times to change the buffer locations.
deactivateif it is not
NULL. Then the plugin may be destroyed or re-
cleanupon the plugin handle (returned from