[PD] plugin~ external
kim at anechoicmedia.com
Sat Jun 5 20:56:39 CEST 2010
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
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!
*my Linux audio perf config:*
Dell Studio 15 Core2 Duo 2.0GHz 3G-RAM
jackd version 0.116.1 tmpdir /dev/shm protocol 24
USB iMic audio interface
cpufreq-set - both cpu's are set to 2.0GHz and userspace
More information about the Pd-list