[linux-audio-dev] LADSPA Extension for Extra GUI Data
S.W.Harris at ecs.soton.ac.uk
Mon Jun 26 08:19:21 EDT 2006
On Mon, Jun 26, 2006 at 01:53:13 +0200, Alfons Adriaensen wrote:
> On Mon, Jun 26, 2006 at 09:07:11AM +0100, Steve Harris wrote:
> > On Sun, Jun 25, 2006 at 04:30:40 -0400, Dave Robillard wrote:
> > > Plus, it's completely useless for GUIs in a separate process, while LV2
> > > is not (it's just a data file, anything can load it, it's not even
> > > architechture dependent).
> > >
> > > Just my two cents, but definitely not the right thing.
> > That's possibly a bit harsh. I think it's reasonable to say that based on
> > our experiences of LADSPA we know that's not the best way to go.
> If the GUI is in a separate process and connected by e.g. OSC, it
> could as well be on a machine that doesn't have the plugin files.
> Or that has a different version of them (for perfectly good reasons).
> To ensure consistency the GUI should get its plugin descriptions from
> the host anyway. This works even with POL (Plain Old Ladspa).
True enough, but with POL if the frontend and backend mahcines are different
architectures or operating systems then you have a problem.
More information about the linux-audio-dev