Subject: Re: Plugin chains and EDLs, was Re: [linux-audio-dev] ardour, LADSPA, a marriage
From: Paul Winkler (slinkp23_AT_yahoo.com)
Date: Fri Nov 17 2000 - 13:57:56 EET
> > > >You can uniquly describe a LADSPA net by stating what each plugin is
> > > >connected to and what all its parameters are. Infact it's probably
> > > >possible to create a LADSPA plugin which reads a nets description and then
> > > >offers all the unconnected inputs and outputs as its input and outputs.
> >
> > brain not working right... what does that let the user do exactly?
>
> It means that any package that can load LADSPA plugins can load your
> predefined plugin net. A lamda plugin as Paul would have it ;)
>
> - Steve
Oh, WOW.
This sounds like a better way to deal with such nets; applications
don't have to know about them at all, there can be just one plugin
that deals with it in all cases.
Very cool. Wasn't code re-use part of the whole point of plugins
anyway?
Sorting out a reasonable GUI that makes sense of this is left as an
exercise to... um... any takers?
: )
--
................. paul winkler ..................
slinkP arts: music, sound, illustration, design, etc.
web page: http://www.slinkp.com
A member of ARMS: http://www.reacharms.com
This archive was generated by hypermail 2b28 : Fri Nov 17 2000 - 14:45:41 EET