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.
does anyone happen to know what exactly IN the patch is making pd crash? has anyone tried fixing it by editing the help patch as a text file?
[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.
is this done instead of creating a path to the LADSPA plugs dir in pd? or does it have to be done in addition to a pd path?
If you use the terminal command "listplugins",
you should point out in the FOSS manual that one needs to have the ladspa-sdk installed to use this command
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...)
interesting I'll try this...
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.
ok I'll take another look...thanks Derek! :)
now, anyone know if [vst~] has been compiled on Linux?
Best! Derek
On 6/7/10 1:48 AM, Kim Cascone wrote:
does anyone happen to know what exactly IN the patch is making pd crash? has anyone tried fixing it by editing the help patch as a text file?
Replace the existing [plugin~] help patch with one posted by Frank Barknecht some years ago. For the five thousandth time in several years, can someone with CVS write access *please* just change this friggin' thing!!!!!!!!!!!!!!!!!!!
[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.
is this done instead of creating a path to the LADSPA plugs dir in pd? or does it have to be done in addition to a pd path?
This is done in bash and not at all in Pd.
If you use the terminal command "listplugins",
you should point out in the FOSS manual that one needs to have the ladspa-sdk installed to use this command
Thanks. Of course, you could create a FLOSS Manuals login and add this piece of info yourself ;-) I may not get around to it...
Best! D.
On Mon, 7 Jun 2010, Derek Holzer wrote:
Replace the existing [plugin~] help patch with one posted by Frank Barknecht some years ago. For the five thousandth time in several years, can someone with CVS write access *please* just change this friggin' thing!!!!!!!!!!!!!!!!!!!
Given the time it took to replace "Max OSX" by "Mac OSX" and the shit I got for it, you can count another five thousand times.
Do you know that the new committer has to get permission from the previous official maintainer ? (who is Jarno Seppänen ?)
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
On Jun 7, 2010, at 1:56 AM, Derek Holzer wrote:
On 6/7/10 1:48 AM, Kim Cascone wrote:
does anyone happen to know what exactly IN the patch is making pd crash? has anyone tried fixing it by editing the help patch as a text file?
Replace the existing [plugin~] help patch with one posted by Frank Barknecht some years ago. For the five thousandth time in several years, can someone with CVS write access *please* just change this friggin' thing!!!!!!!!!!!!!!!!!!!
Post the bug to the tracker with the updated patch: http://sourceforge.net/tracker/?group_id=55736&atid=478070
That's the easiest way to get it fixed for those of us without SVN commit access.
Dan Wilcox danomatika.com robotcowboy.com
Updated patch:
http://sourceforge.net/tracker/?func=detail&aid=3012451&group_id=557...
Maybe sometime in the next millennium this will make it into the distribution....
D.
On 6/7/10 9:42 AM, Dan Wilcox wrote:
On Jun 7, 2010, at 1:56 AM, Derek Holzer wrote:
On 6/7/10 1:48 AM, Kim Cascone wrote:
does anyone happen to know what exactly IN the patch is making pd crash? has anyone tried fixing it by editing the help patch as a text file?
Replace the existing [plugin~] help patch with one posted by Frank Barknecht some years ago. For the five thousandth time in several years, can someone with CVS write access *please* just change this friggin' thing!!!!!!!!!!!!!!!!!!!
Post the bug to the tracker with the updated patch: http://sourceforge.net/tracker/?group_id=55736&atid=478070 http://sourceforge.net/tracker/?group_id=55736&atid=478070
That's the easiest way to get it fixed for those of us without SVN commit access.
Dan Wilcox danomatika.com http://danomatika.com robotcowboy.com http://robotcowboy.com
On 2010-06-07 11:13, Derek Holzer wrote:
Updated patch:
http://sourceforge.net/tracker/?func=detail&aid=3012451&group_id=557...
Maybe sometime in the next millennium this will make it into the distribution....
as noted in the patch tracker: your patch crashes my Pd just as well as the original one.
anyhow, i have committed some changes to plugin~ that will hopefully fix most issues. (read: it doesn't crash here AND it doesn't make text-vanish)
please test (personally, i don't use LV2, ladspa, vst,...) if it is good enough, it should probably go into the PdX-0.42 release before it's too late.
Thanks. It's not my patch, it's one from Frank from a few years ago. Others have reported [more] success with it.
Best! D.
On 6/7/10 4:34 PM, IOhannes m zmoelnig wrote:
On 2010-06-07 11:13, Derek Holzer wrote:
Updated patch:
http://sourceforge.net/tracker/?func=detail&aid=3012451&group_id=557...
Maybe sometime in the next millennium this will make it into the distribution....
as noted in the patch tracker: your patch crashes my Pd just as well as the original one.
anyhow, i have committed some changes to plugin~ that will hopefully fix most issues. (read: it doesn't crash here AND it doesn't make text-vanish)
please test (personally, i don't use LV2, ladspa, vst,...) if it is good enough, it should probably go into the PdX-0.42 release before it's too late.
On 2010-06-07 18:24, Derek Holzer wrote:
Thanks. It's not my patch, it's one from Frank from a few years ago.
whosever patch it was, it crashed here. so could you try to confirm whether the new code works as expected?
if it does work, then no help-patch should crash anymore.
e.g. the load a plugin from a dll (e.g. [plugin~ stereo_amp amp.so]) doesn't work for me, but it seems like it doesn't work with the original version either.
fgmasdr IOhannes
the larger problem is that plugin~ crashes whenever a non-existent plugin is requested. that is an issue i have no idea how to fix. maybe the help patch in question should not request any plugins then, but simply include syntax for how it works.
d.
On 6/7/10 6:40 PM, IOhannes m zmoelnig wrote:
On 2010-06-07 18:24, Derek Holzer wrote:
Thanks. It's not my patch, it's one from Frank from a few years ago.
whosever patch it was, it crashed here. so could you try to confirm whether the new code works as expected?
if it does work, then no help-patch should crash anymore.
e.g. the load a plugin from a dll (e.g. [plugin~ stereo_amp amp.so]) doesn't work for me, but it seems like it doesn't work with the original version either.
fgmasdr IOhannes
hello derek,
i'm not sure whether you read my emails or whether i write nonsense.
On 2010-06-07 18:43, Derek Holzer wrote:
the larger problem is that plugin~ crashes whenever a non-existent plugin is requested. that is an issue i have no idea how to fix. maybe the help patch in question should not request any plugins then, but simply include syntax for how it works.
about 2 hours ago, i committed a changeset to the plugin~.c source code, that should fix all these problems. (read: there is a bugfix, which fixes the bug rather than trying to avoid triggering it)
i ask you (and everybody else, who is interested in a working [plugin~]), to get the source-code, compile the external and test whether it works. i'm pressing this a bit, in order to get the bugfix into PdX.
fgam,sdr IOhannes
sorry, maybe i read quickly. i read that you made changes, but i did not understand you wanted those tested. i was still discussing the help patch. if i find time later i will check it. is it in the CVS? i've never tested release candidates for Pd before so pls excuse my ignorance.
d.
On 6/7/10 6:51 PM, IOhannes m zmoelnig wrote:
hello derek,
i'm not sure whether you read my emails or whether i write nonsense.
On 2010-06-07 18:43, Derek Holzer wrote:
the larger problem is that plugin~ crashes whenever a non-existent plugin is requested. that is an issue i have no idea how to fix. maybe the help patch in question should not request any plugins then, but simply include syntax for how it works.
about 2 hours ago, i committed a changeset to the plugin~.c source code, that should fix all these problems. (read: there is a bugfix, which fixes the bug rather than trying to avoid triggering it)
i ask you (and everybody else, who is interested in a working [plugin~]), to get the source-code, compile the external and test whether it works. i'm pressing this a bit, in order to get the bugfix into PdX.
fgam,sdr IOhannes
On 2010-06-07 19:19, Derek Holzer wrote:
sorry, maybe i read quickly. i read that you made changes, but i did not understand you wanted those tested. i was still discussing the help patch. if i find time later i will check it. is it in the CVS? i've
the code is in Pd's repository (which is Subversion-based for about 9 years and 4 months now; CVS is dead and gone)
the source code can be downloaded either via svn (https://pure-data.svn.sourceforge.net/svnroot/pure-data/trunk/externals/plug...) or as a tarball from: http://pure-data.svn.sourceforge.net/viewvc/pure-data/trunk/externals/plugin...
the build-system is scons based ("apt-get install scons"; and then run "scons" in the directory)
fmasdr IOhannes
IOhannes, feel free to commit/copy this directly to the pd-extended/
0.42 release branch. One we are in the release cycle, I prefer to do
bug fixes in the release branch, then merge them to trunk when its all
over. Otherwise, if its a small fix, then I just commit to both trunk
and the branch.
.hc
On Jun 7, 2010, at 12:51 PM, IOhannes m zmoelnig wrote:
hello derek,
i'm not sure whether you read my emails or whether i write nonsense.
On 2010-06-07 18:43, Derek Holzer wrote:
the larger problem is that plugin~ crashes whenever a non-existent plugin is requested. that is an issue i have no idea how to fix.
maybe the help patch in question should not request any plugins then, but simply include syntax for how it works.about 2 hours ago, i committed a changeset to the plugin~.c source
code, that should fix all these problems. (read: there is a bugfix, which fixes the bug rather than trying to avoid triggering it)i ask you (and everybody else, who is interested in a working [plugin~]), to get the source-code, compile the external and test whether it works. i'm pressing this a bit, in order to get the bugfix into PdX.
fgam,sdr IOhannes
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
http://at.or.at/hans/
On Mon, 7 Jun 2010, Derek Holzer wrote:
Updated patch: http://sourceforge.net/tracker/?func=detail&aid=3012451&group_id=557... Maybe sometime in the next millennium this will make it into the distribution....
According to computer-assisted geology, in the year 75.000.000 approx, two tectonic plates will have converged enough to accidentally apply the patch to the software.
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard, Montréal, Québec. téléphone: +1.514.383.3801
On 2010-06-07 17:38, Mathieu Bouchard wrote:
On Mon, 7 Jun 2010, Derek Holzer wrote:
Updated patch: http://sourceforge.net/tracker/?func=detail&aid=3012451&group_id=557...
Maybe sometime in the next millennium this will make it into the distribution....
According to computer-assisted geology, in the year 75.000.000 approx, two tectonic plates will have converged enough to accidentally apply the patch to the software.
do you have proof for this?
fgamsdr IOhannes
-
Dan Wilcox -
Derek Holzer -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
Kim Cascone -
Mathieu Bouchard