[linux-audio-dev] Modular synths of the world, unite and take over :-)

Lukas Degener AFBLukas at gmx.de
Tue Mar 18 14:51:01 UTC 2003


>
>
>I'm new to LADSPA, but isn't that what LADSPA control
>protocol does? 
>
Dunno. have to do some reading. What is Open Sound Control?

>
>Say I wanted to make a snazzy analogue modelled
>filter. Someone else wanted to integrate it into their
>modular. They could do that and make it just another
>module and keep the look of their app consistent. When
>their app is running the gui-less version of the
>plugin, all their app needs to do is have a mechanism
>for controlling the important paremeters, in this
>case, cutoff, resonance and so forth.
>
As pointed out before, i think it's not so much a problem of reusing 
modules.
This should work already, just have ladspa for them.

The point is, that there are some things that e.g. are possible in 
gAlan, which aren't possible in
ams and vice versa. Those things are not that much related to a certain 
module, but rather to the way this modules are used.
It would therefor be great (but difficult) if we could come up with an 
abstraction of the whole problem, or adaequat parts of it.

An ideal scenario (in my eays) would be:
- you have a patch (or want to creat one)
- you choose the components that you think are best for this job,
- you let them all work on the same patch instance at the same time.


A (maybe) possible way to do this:
- we try to modell as much functionality of our apps as possible, by 
using apis already available (ladspa and friends)
- we find a common abstraction for all that is left after that. (*)
e.g. for ams that would meen: Forget about parameters, we use control 
ports like ladspa, we have the midi control center replaced
by some "intelligent" mcv modules, module uis would could also become 
special modules, that only have control io and are bind to some widget(s).

I don't know enough about the design of the other projects to make any 
statements here. But something similar should be possible,

And finaly, we would have to think about what a "patch" realy is, and 
define an api interface for editing/displaying it (*)

(*)  this are the tricky parts, i think ;-)

>
>one  question i have is how does the licensing work?
>provided the program is linked to the LADSPA lib, the
>plugin and the app don't need to match licensing, eh?
>i could have a commercial host w/ gpl client or vice
>versa? mix bsd and gpl?
>
Hmm... maybe lgpl for modules?
Well its not realy an interesting question as long there is nothing to 
put a licens on.
I'm sure we would find a solution for that.

Regards,
Lukas




More information about the Linux-audio-dev mailing list