[linux-audio-dev] LADSPA 2

Dave Robillard drobilla at connect.carleton.ca
Sat Apr 22 23:35:42 UTC 2006


On Sun, 2006-04-23 at 01:10 +0200, Luis Garrido wrote:
> > I'm going to assume this is a shot at me for rather obvious reasons.
> 
> No, I was more thinking in Phil Frost's contribution to this
> discussion (contribution that I find very interesting and pertinent,
> but as a musician I am not interested in LADSPA becoming another low
> level LEGO api to build modular synths, there are already some good
> solutions to that problem).

My apologies then.  I've become accustomed to knee-jerk anti modular
reactions whenever I use anything remotely modular as an example for
something. :)

Frankly I don't understand the phenomenon at all, your comments are a
perfect example.  The source code idea would mostly be beneficial for
building stand-alone static (ie non modular) synths.  The UI
for /creating/ them would be modular probably, since that's really the
only really reasonable UI for doing so, but it wouldn't /have/ to be.

Yet, you say the word "modular" and the idea is automatically cast aside
by everyone.  You make the exact same point without saying the magic M
word, and my, what an interesting idea!

I Don't Get It(TM), but whatever.  I suppose it's like math, non math
people see one Sigma and their brains just turn off immediately.

I just make sure not to say the magic M word wherever possible to avoid
it. ;)

[/digression]

> > *sigh* someone just had to do it, didn't they?
> 
> GUIs appeared in the thread long before my post.
> 
> > LAD_S_PA2 is not going to have GUIs.  http://dssi.sf.net.  Enjoy.
> 
> I am well aware of that. Thanks for the pointer, anyway.
> 
> http://flam.sf.net
> 
> But still there are some parts of LADSPA that have to provide
> information for effective (auto)building of GUIs.

I am of the opinion that auto generated UIs is not the way to go in
general, but regardless that's the beauty of external metadata.  You can
experiment with whatever added data you like, if it works well people
will start using it and it might become part of the standard eventually.
 
LADSPA has long been hindered by the draconian pre-defined nature of C
ABIs.  With rigorously seperated metadata we'll finally be able to
experiment with things like this without breaking things and LADSPA can
evolve...

-DR-




More information about the Linux-audio-dev mailing list