Subject: Re: [linux-audio-dev] Mustajuuri -> LADSPA plugins.
From: Steve Harris (S.W.Harris_AT_ecs.soton.ac.uk)
Date: Wed Mar 28 2001 - 13:10:45 EEST
On Wed, Mar 28, 2001 at 10:39:34AM +0300, Tommi Ilmonen wrote:
> Besides, the user interfaces can be really different. We would need new
> XML-spec for any new GUI element (right ?). Example: A modeling reverb
> plugin might want to show an interactive 3D-model of the room to
> the user. So, if you wanted a GUI like that, then we'd need a XML spec for
> 3D rendering and interaction and everybody needs to implement the XML spec
> (or lose the plugin). There are many GUI strategies people have come up
> with (and will come up with). If we want to support all of them then the
> XML-spec will become huge.
I agree, but no-one could suggest a good way of providing a GUI to a
LADSPA plugin. I would suggest that anything that complicated probably
shouldn't be implemented in LADSPA, athough there is not much choice if
you want your plugins to be usable by more than one host.
> This is what I was expecting to do. So the plugin checks all control
> parameters to see if they have changed and generates events for itself.
>
> Sidenote: When a user adjusts a parameter in Mustajuuri an event is
> generated. This event is passed to the LADSPA plugin wrapper. The wrapper
> turns the event to a value change in a control port. A "Harris-plugin"
> then converts the value change back to an event and processes it. Cool (!)
Actually this only happens for parameters where recalculating the internal
parameters is expensive enough to justify it. One of the virues of a
LADSPA plugin is supposed to be constant CPU use, allthough many of mine
don't meet that.
- Steve
This archive was generated by hypermail 2b28 : Sat Apr 07 2001 - 15:39:11 EEST