I know this topic has been brought up in the past and I searched the archives hoping to find some more info but...
I'm unable to get plugin~ working on Pd version 0.41-4extended I have set a path to my LADSPA library as well as the plugin~ dir in my extras directory
I can instantiate an object but I get the following error when loading the tap_autopanner and tap_eq plugins with the plugin~ object:
plugin~: constructed plugin "TAP AutoPanner" successfully plugin~: plugin ports: audio 2/2 ctrl 3/0 plugin~: plugin active plugin~: close_plugin (x) plugin~: destructed plugin successfully config listed below
I chose to test with the TAP plugs because a) they've been around a long time and still being worked on IIRC b) they work in Ardour and AMS for me and c) they are from the same collection of LADSPA plugs made by the same developer
so my questions are:
- why do some LADSPA plugs work while others do not?
- I remember Derek mentioning a 'workaround' in the archives but was
unable to find the solution - (was it recompiling the plugin~ object?) can someone point me to the workaround?
- does anyone else use this external and have it working on Linux?
- is there a newer, more robust or another external for hosting LADSPA,
LV2 and/or VST plugins?
any help is appreciated! ciao! KIM
I've tried a little but its always seemed like blackmagic to me. If
someone figures out a way to streamline it, I'd happily include that
in Pd-extended.
.hc
On Jun 5, 2010, at 2:56 PM, Kim Cascone wrote:
I know this topic has been brought up in the past and I searched the
archives hoping to find some more info but...I'm unable to get plugin~ working on Pd version 0.41-4extended I have set a path to my LADSPA library as well as the plugin~ dir in my extras directory
I can instantiate an object but I get the following error when loading the tap_autopanner and tap_eq plugins with the plugin~ object:
plugin~: constructed plugin "TAP AutoPanner" successfully plugin~: plugin ports: audio 2/2 ctrl 3/0 plugin~: plugin active plugin~: close_plugin (x) plugin~: destructed plugin successfully config listed below
I chose to test with the TAP plugs because a) they've been around a long time and still being worked on IIRC b) they work in Ardour and AMS for me and c) they are from the same collection of LADSPA plugs made by the
same developerso my questions are:
- why do some LADSPA plugs work while others do not?
- I remember Derek mentioning a 'workaround' in the archives but was
unable to find the solution - (was it recompiling the plugin~
object?) can someone point me to the workaround?
- does anyone else use this external and have it working on Linux?
- is there a newer, more robust or another external for hosting
LADSPA, LV2 and/or VST plugins?
any help is appreciated! ciao! KIM
-- *my Linux audio perf config:* Dell Studio 15 Core2 Duo 2.0GHz 3G-RAM Ubuntu 9.04 kernel 2.6.28.19-generic jackd version 0.116.1 tmpdir /dev/shm protocol 24 Ardour 2.8.2 USB iMic audio interface Korg nanoKontrol cpufreq-set - both cpu's are set to 2.0GHz and userspace
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
Using ReBirth is like trying to play an 808 with a long stick. - David Zicarelli
On 6/5/10 8:56 PM, Kim Cascone wrote:
- I remember Derek mentioning a 'workaround' in the archives but was
unable to find the solution - (was it recompiling the plugin~ object?) can someone point me to the workaround?
I've pasted my reply from the thread "easy effects", and I also started a page on plugin~/LADSPA in the FLOSS Manual (*very* rough, needs a lot of expansion!):
http://en.flossmanuals.net/bin/view/PureData/UsingLADSPAplugins
[plugin~] can be tricky or just a plain pain the wazoo to use simply because it can crash when given the wrong creation arguments, such as the name of a plugin that doesn't exist on your computer. Of course, a help patch which crashed on anybody's computer should be a high priority to fix, but maybe not everybody around here seems to agree with that ;-) I posted about this problem in 2005 and still it hasn't really been dealt with.
[plugin~] requires the path to your LADSPA directory to be set as the LADSPA_PATH in the environment. Look up "setting environmental variables" plus either "bash" or "shell" on Google to see how this is done if you don't know how.
If you use the terminal command "listplugins", you should see a list of the LADSPA plugins on your system. You must use the exact name listed there, for example, if "listplugins" gives you:
/usr/local/lib/ladspa/noise.so: White Noise Source (1050/noise_white)
then you would use [plugin~ noise_white]. (Somebody correct me if this is wrong, I am not on a Linux system where I can check this for the next several days...)
Then, you need to send the proper control parameter number, and NOT the control parameter name. For example, if sending the message "info" to the plugin lists the following to your Pd window via [print]:
Loaded from library "/usr/lib/ladspa/mvclpf24.so". Control input(s): #1 "Input gain (dB)" #2 "Frequency" #3 "Exp FM gain" #4 "Resonance" #5 "Resonance gain" #6 "Filter poles" #7 "Output gain (dB)" Control output(s): Audio input(s): #1 "Input" #2 "Frequency" #3 "Exp FM" #4 "Resonance" Audio output(s): #1 "Output"
Then you would have to make a message "1 $1" to send a variable to control the input gain from a number box or slider.
More info on LADSPAs in general:
http://linuxdevcenter.com/pub/a/linux/2001/02/02/ladspa.html
If somebody would like to make a chapter on this in the Pd FLOSS Manual, I would jump for joy. I just haven't had the time to do it myself. Feel free to copy paste from this email and make some screenshots! ;-)
You can also search for "plugin~" in the list archives and find much discussion on this. The two threads I started were called "plugin~ ladspa" and "setting plugin~ control inputs" in about 2005, when I was trying to figure this all out.
Best! Derek
-
Derek Holzer -
Hans-Christoph Steiner -
Kim Cascone