The other plus side would seem to be tighter integration with a hosts
parameter modulation, though this could be ameliorated by using a
ladspa plugin that outputs osc, such as the ladosc plugins, to send
control signals to your synthesis environment.<br>
<br>Also not mentioned in this thread is that the CLAM network
prototyper is able to build ladpsa plugins and is, as far as I know,
quite far along the path of being able to build vsts. Given its
integration of faust and the versatility of its graphical environment,
I would think it a viable candidate. It is actively developed, but the
last stable release was over a year ago now. <br><font color="#888888">
<br>-michael</font><br><br><div class="gmail_quote">On Mon, Sep 14, 2009 at 9:31 AM, Malte Steiner <span dir="ltr"><<a href="mailto:steiner@block4.com">steiner@block4.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im"><br>
><br>
> Isn't one of those languages already able to spit out various plug-in<br>
> formats and/or at least C code? Was it csound, supercollider or chuck?<br>
><br>
</div>I guess you refer to Faust which can generate several formats and plugins<br>
<br>
<a href="http://faust.grame.fr/" target="_blank">http://faust.grame.fr/</a><br>
<br>
There is also csLadspa which converts csound patches to Ladspa plugins.<br>
<br>
But actually you guys lost me a bit, what is so important about the<br>
plugin paradigma? The only benefit I can see is total recall but apart<br>
from it I see no use over using stand alone applications. The plugin<br>
idea comes from closed source environment which doesnt allow to make<br>
interapplication connection like you can do now and here with Jack and<br>
Alsamidi.<br>
<br>
Cheers,<br>
<br>
Malte<br>
<font color="#888888">-</font><br>
</blockquote></div><br>