Hi all,
what is the proper way to call a LADSPA plugin in the plugin~ object?
Some, like "flanger", seem simple enough, But trying to invoke "dj_flanger" or even "dj_flanger_1438.so" doesn't do a damned thing!
Does this have to do with "dj_flanger" being a plugin which is part of a bigger library? Even so, why can I not invoke it by it's actual name in /usr/lib/ladspa, where all my other ladspa plugins live.
thx, D.
Hallo, derek holzer hat gesagt: // derek holzer wrote:
what is the proper way to call a LADSPA plugin in the plugin~ object?
If you do a "listplugins" you get something like:
$ listplugins | grep dj /usr/lib/ladspa/dj_flanger_1438.so: DJ flanger (1438/djFlanger)
The "djFlanger" after the id is the one you need to supply to plugin~.
ciao
Frank Barknecht _ ______footils.org__
Hi Frank,
Frank Barknecht wrote:
If you do a "listplugins" you get something like:
$ listplugins | grep dj /usr/lib/ladspa/dj_flanger_1438.so: DJ flanger (1438/djFlanger)
The "djFlanger" after the id is the one you need to supply to plugin~.
nice trick! I didn't know this listplugins command.
Now, about setting the environmental variable...
Where would be a good place for that? I can export LADSPA_PATH=/usr/lib/ladspa every time, but isn't that what things like the .pdrc are for? But, of course, it doesn't go there...
D.
Hallo, derek holzer hat gesagt: // derek holzer wrote:
Now, about setting the environmental variable...
Where would be a good place for that? I can export LADSPA_PATH=/usr/lib/ladspa every time, but isn't that what things like the .pdrc are for? But, of course, it doesn't go there...
No, .pdrc is not a good place, as LADSPA_PATH is also used by other LADSPA enabled applications. Normally you would put things like that into /etc/profile or ~/.bash_profile rsp. .bashrc I use /etc/environment and ~/.environment for that, and source this file in .xsession and similar places. Example:
# ~/.environment # ... PAGER=less LADSPA_PATH=/usr/lib/ladspa/:$HOME/lib/ladspa # ...
Then in ~/.bash_profile I have this:
# source and export env:
if [ -f ~/.environment ] ; then
. ~/.environment
for n in grep -v ^# ~/.environment | cut -s -d= -f1; do export $n; done
fi
and I do the same in ~/.xsession
The advantage is, that .environment contains just simple "var=value" pairs and I can extend or shorten the list very easily. (.environment is also used by ssh, BTW.)
ciao
Frank Barknecht _ ______footils.org__
-
derek holzer -
Frank Barknecht