Subject: Re: [linux-audio-dev] LADSPA Instruments
From: torbenh_AT_gmx.de
Date: Thu Apr 10 2003 - 18:05:31 EEST
On Thu, Apr 10, 2003 at 04:53:15AM +0100, Steve Harris wrote:
> On Wed, Apr 09, 2003 at 06:39:39 -0700, robbins jacob wrote:
> > This is important because it means that we can implement _right_now_
> > ladspa instruments that can be used without the user having to hook up
> > control A to port B or generally know what the hell they're doing. In fact,
> > the sine oscillator plugin, provided by Richard Furse as an example plugin
> > for the ladspa sdk, is a reference example that host programmers can code
> > off of _right_now_. Just remember that each ladspa plugin instance is a
> > single voice, so polyphony must be implemented in the host. Fortunately,
> > this is not that hard(*).
>
> It still means a fair ammount of manual wiring, you need to express things
> like velocity, aftertouch and gate open/closed-ness.
yeah...
>
> Also implementing polyphony control in the host is less efficient, and it
> means you can't have things like shared LFOs, which are very common.
these LFOs must be implemented in the host also.
>
> OTOH, I agree that you can make very good synths out of LADSPA, but I
> think it requires modular synth style wiring.
which is implemented in ams, beast, galan, ssm...
-- torben Hohn http://galan.sourceforge.net -- The graphical Audio language
This archive was generated by hypermail 2b28 : Thu Apr 10 2003 - 15:22:12 EEST