Subject: [linux-audio-dev] My Hopes for an Open Plugin Specification
From: est_AT_hyperreal.org
Date: pe elo 27 1999 - 14:02:54 EDT
Hello, people,
First of all, I hope more people will participate in the dialog. :)
My personal hopes for an open plugin specification are based on
frustration with the current situation. There's a *lot* of existing
code out there. Usually when I want to use a piece of code for my
purposes, I have to hack it up a little. I'd much rather hack it up
to a common specification so that everyone can use it. Similarly for
the code I write (or that my programs write :) I suspect most coders
here can empathize with this.
This means I want a specification that can accomodate most of the code
out there that I'll probably end up using and most of the code that
I'll end up writing. I hope other people's needs will be accomodated
as well. This means that the specification should accomodate styles
and paradigms that I don't plan on using and may even find
distasteful.
There's an incredible variety of approaches and concerns with respect
to audio software on this list. If someone really wants a feature in
the plugin specification, I think it should go in unless the cost for
those who don't use it is overwhelming. That's how we can build a
consensus specification. Applications that want to require/exclude
certain types of plugins should have the means to do so. Plugin
authors that don't want to worry about setting all the
parameters/predicates right should be provided with reasonable
defaults.
Anyhow, I hope this helps explain where I'm coming from as I make my
more technical comments. :)
Now, lets move on to audio world domination!
Eric
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:25:53 EST