hi list,
i patched plugin~ to make it run correctly and renamed the object to ladspa~ to make it less confusing. http://bitbucket.org/moumar/ladspa/
Feel free to give me suggestions.
On 18 Jan 2009, at 23:34, moumar@laposte.net wrote:
hi list,
i patched plugin~ to make it run correctly and renamed the object to ladspa~ to make it less confusing. http://bitbucket.org/moumar/ladspa/
Feel free to give me suggestions.
My suggestion is that you try using dssi~. It supports LADSPA just
the same as plugin~, but is more full-featured.
It has been discussed recently that we bring the dssi~ Pd interface in
line with plugin~ (It almost already is) and then simply rename it to
plugin~, replacing the old one. I'd like to add LV2 support and ensure
that dssi-vst support works as well.
Then the generic name 'plugin~' becomes a bit more justified ;-)
Jamie
oh ok, i was not aware of the merging process between dssi~ and plugin~. However i had some little issues with dssi~, that i'm currently fixing. I'll send you a patch soon :)
regards
On Mon, Jan 19, 2009 at 9:34 AM, Jamie Bullock jamie@postlude.co.uk wrote:
On 18 Jan 2009, at 23:34, moumar@laposte.net wrote:
hi list,
i patched plugin~ to make it run correctly and renamed the object to ladspa~ to make it less confusing. http://bitbucket.org/moumar/ladspa/
Feel free to give me suggestions.
My suggestion is that you try using dssi~. It supports LADSPA just the same as plugin~, but is more full-featured.
It has been discussed recently that we bring the dssi~ Pd interface in line with plugin~ (It almost already is) and then simply rename it to plugin~, replacing the old one. I'd like to add LV2 support and ensure that dssi-vst support works as well.
Then the generic name 'plugin~' becomes a bit more justified ;-)
Jamie
-
Jamie Bullock -
moumar＠laposte.net