Subject: Re: [linux-audio-dev] Ladspa Gui's (Is ladspa actually la-dsp-a?)
From: Dave Robillard (drobilla_AT_connect.carleton.ca)
Date: Tue Jun 08 2004 - 22:26:03 EEST
On Tue, 2004-06-08 at 15:26, Chris Cannam wrote:
> On Tuesday 08 Jun 2004 6:59 pm, Tim Orford wrote:
> > is it possible to summarise the objections to the dssi approach
> > for ladspa?
>
> One objection is that it completely avoids addressing the problem of
> how to embed the GUI inside the host on-screen. Each GUI is
> basically assumed to run up as a separate top-level window.
Maybe it's just me personally, but I don't see much of a problem with
this. I think of ams, where the modules themselves are just shown as,
er, little boxes with ports, but you can click 'em to get the gui and
change all the parameters. Ardour is the same way.
All we need IMHO is a way to have that parameter view be a custom GUI.
I can't honestly even think of a case where embedding the plugin UIs
would even be wanted (though I'm sure someone can).. plugin GUIs are
huge and take up a lot of space. I just want to be able to pop the
thing up, fiddle with it, and make it go away.
Maybe if you want to do a reason-like virtual rack type of thing, but..
well, reason's UI is stupid. :)
-Dave Robillard
This archive was generated by hypermail 2b28 : Tue Jun 08 2004 - 22:28:19 EEST