On 3/28/06, Jamie Bullock jamie@postlude.co.uk wrote:
Hi,
On Tue Mar 28 12:48 , 'Libero Mureddu' libero.mureddu@gmail.com sent:
Hi,
now I've got dssi~ to compile correctly. It also loads in pd correctly. However, listplugins crashes. I didn't have ladspa SDK installed, because the ladspa packages provided in the ardour website contain only the plugin, so I've installed ladspa SDK via Fink. So, now I have listplugins working.
In any case, I don't know how to check if dssi~ can read my ladspa plugins, because I don't know how to control the plugins parameters with pd. Can you send me a test patch to try a ladspa plugin?
The updated help file in CVS now shows how it should all work. It requires sine.so and hexter.so. In essence, once the plugin has loaded, sending an 'info' message to the object will tell you the LADSPA control and audio ports supported by the plugin, suggested minimum, maximum and default values. All control port data is sent via the first inlet in the following form
|control #<portnumber> <value> <instance>( | [dssi~ <pluginname> <instances>]
Audio rate inlets and outlets will be built dynamically depending on how many audio ports there are, and how many instances of the plugin you are running.
If this isn't clear, let me know, and I will produce some better documentation (i should do that anyway ;-)
Jamie
Hi, sending the 'info' message, doesn't produce anything, not even an error message in the pd window. The 'listplugins' message crashes pd, and also opening your patch causes the crash, I think because I don't have hexter installed, so I'm trying to compile dssi (not dssi~!) and hexter but I have some problems compiling them.
But the good news are that dssi~ loads the plugins correctly it seems, at least it creates different inlets according to different plugins. I read from another email that it is not necessary to install ladspa SDK in order to have listplugins working, but I couldn't understand if I have to install jutils, or in which way jutils are related with dssi~.
Thanks
Libero
Hi,
On Thu, 30 Mar 2006 12:59:20 +0300 "Libero Mureddu" libero.mureddu@gmail.com wrote:
<snip> > > > Hi, > sending the 'info' message, doesn't produce anything, not even an > error message in the pd window. The 'listplugins' message crashes pd, > and also opening your patch causes the crash, None of these things should make PD crash, and I can't reproduce the problem. On my machines if you try to load a non-existant plugin the PD console just reports that it couldn't load the plugin.
Could you send me your dssi~.pd_darwin file off list.
I think because I don't have hexter installed, so I'm trying to compile dssi (not dssi~!) and hexter but I have some problems compiling them.
The substance of DSSI is really just a header file. The other things that get installed when you install the package are things like jack-dssi-host (another host), and some example plugins. All you need for dssi~ is dssi.h.
But the good news are that dssi~ loads the plugins correctly it seems, at least it creates different inlets according to different plugins.
And do you get audio? Please find attached a very simple test patch. It only requires filter.so and sine.so.
If you still have problems loading the patch, I suggest you temporarily remove all other libaries from the path, as it is possible that a particular plugin is crashing dssi~ when it searches through your path.
I read from another email that it is not necessary to install ladspa SDK in order to have listplugins working, but I couldn't understand if I have to install jutils, or in which way jutils are related with dssi~.
Just like the DSSI 'package', the LADSPA SDK is not a real dependency. Only ladspa.h is required. I should probably modify the README so this is a bit clearer. You don't need to install 'jutils'; a modified version is already provided with the dssi~ sources, and it is compiled into dssi~.pd_darwin as part of the 'make' process. It contains the functions for searching for and loading plugins.
Jamie
On 3/31/06, Jamie Bullock jamie@postlude.co.uk wrote:
Hi,
On Thu, 30 Mar 2006 12:59:20 +0300 "Libero Mureddu" libero.mureddu@gmail.com wrote:
<snip> > > > Hi, > sending the 'info' message, doesn't produce anything, not even an > error message in the pd window. The 'listplugins' message crashes pd, > and also opening your patch causes the crash, None of these things should make PD crash, and I can't reproduce the problem. On my machines if you try to load a non-existant plugin the PD console just reports that it couldn't load the plugin.
Could you send me your dssi~.pd_darwin file off list.
Yes.
I think because I don't have hexter installed, so I'm trying to compile dssi (not dssi~!) and hexter but I have some problems compiling them.
The substance of DSSI is really just a header file. The other things that get installed when you install the package are things like jack-dssi-host (another host), and some example plugins. All you need for dssi~ is dssi.h.
Yes, this is clear. My point is that it seems that if the plugin doesn't exists, pd crashes. If I write in an object box 'dssi~ ciao', pd quits.
But the good news are that dssi~ loads the plugins correctly it seems, at least it creates different inlets according to different plugins.
And do you get audio? Please find attached a very simple test patch. It only requires filter.so and sine.so.
I modified the patch with a text editor in order to give the right path to the sine.so, and canceled the line containing 'dssi~ lpf' otherwise, crash! But yes, I get a nice and warm sinusoid!
If you still have problems loading the patch, I suggest you temporarily remove all other libaries from the path, as it is possible that a particular plugin is crashing dssi~ when it searches through your path.
I did, but I still cannot open your patch.
I read from another email that it is not necessary to install ladspa SDK in order to have listplugins working, but I couldn't understand if I have to install jutils, or in which way jutils are related with dssi~.
Just like the DSSI 'package', the LADSPA SDK is not a real dependency. Only ladspa.h is required. I should probably modify the README so this is a bit clearer. You don't need to install 'jutils'; a modified version is already provided with the dssi~ sources, and it is compiled into dssi~.pd_darwin as part of the 'make' process. It contains the functions for searching for and loading plugins.
Ok, thanks for the clarification. Anyway I want to compile by myself the ladspa plugins, in order to understand better why some of them don't work with ardour. But of course with pd I've tried only those that I remember were working with ardour.
BTW, 'info' message works! I 'just' forgot to connect the print object... sorry!
Libero
Jamie
-
Jamie Bullock -
Libero Mureddu