A common plugin repository (WAS:Re: [LAD] ladspa qa?)

Juuso Alasuutari juuso.alasuutari at gmail.com
Wed Sep 5 07:23:05 UTC 2007

On Tuesday 04 September 2007 22:56:04 Tim Blechmann wrote:
> > > have there been some thoughts of introducing some kind of ladspa qa?
> >
> > Not that I know of, but it's a brilliant idea.
> >
> > I've been meaning to setup some kind of wiki based thing where users
> > can share problems/experiences, but just never had the time.
> a wiki is probably a good starting point ... this may also lead to less
> duplicate plugins if people collaborate ... like, there is not really
> the need for 5 different lowpass filters, especially, if only 2
> implementations are stable ... :/

That gives me a thought.

Please excuse me if the following sounds like it's too central 
management-based, and it may well be that. But if we as a community would 
take more responsibility for managing plugin sets written for specific 
purposes, perhaps we could reduce duplication of work and help people 
concentrate on shared codebases.

I'm not suggesting that individually written, "external" plugins and plugin 
sets should be considered fringe material, let alone shunned. But seeing how 
the Linux kernel community works, I think that creating something like "The 
Linuxaudio.org Plugin Collection" could benefit a common purpose.

There could be separate sets for filters, delays, reverbs, oscillators, etc, 
all being individual parts of a larger common code repository. And individual 
("external") developers could actively campaign for the inclusion of their 
plugins and/or code refinements to the said plugin sets. Additionally, the 
linuxaudio.org plugin set developers could keep an eye on new and promising 
plugins, and approach their developers in hopes of gaining new contributions.

Of course the whole purpose of such a centrally managed plugin repository 
would be to give birth to Very Good Code. That implies that any contributions 
would need to adhere to accepted common standards and practices, just like 
contributions to the Linux kernel need to adhere to the standards and 
practices of the kernel community.


More information about the Linux-audio-dev mailing list