Subject: Re: [linux-audio-dev] more on plugins/LADSPA
From: Kai Vehmanen (kaiv_AT_wakkanet.fi)
Date: Fri Mar 17 2000 - 13:59:08 EST
On Thu, 16 Mar 2000, David Olofson wrote:
>> in as many projects as possible. It might not be such a bad idea to develop
>> multiple APIs in paraller (MuCoS, LADSPA, LUGAPI (Linux Unit Generator
> Parallel development of a few, slightly different APIs is good, but I
> just don't think they'll end up being different enough to end up as
> individual APIs.
Hmm, I just feel that trying to put everything under the same interface -
although maybe possible - will slow down the development. We already
have many different approaches:
- the current LADSPA model
- realtime bounded API (memory allocation issues, realtime
requirements, etc. - mostly unsolved)
- GUI interaction -> GUI-specific plugin-APIs (no agreement)
- sample-accurate, event-based API (MuCoS, as you've said, still
vaporware)
- ...
The first one is ready (well, at least very close) for real use, but
the rest is still pretty much an open field. Parallel development
would mean, that we would start using LADSPA, while still continuing
to discuss the other issues and plugin models. Sometime in the future,
we may combine all (or some) of these APIs to one all-around API.
And just to make sure, I'm not trying to say that the current LADSPA
model is ready - I'm just saying that we have to draw the line
somewhere.
-- Kai Vehmanen <kaiv_AT_wakkanet.fi> -------- CS, University of Turku, Finland . http://www.wakkanet.fi/ecasound/ - linux multitrack audio processing . http://www.wakkanet.fi/sculpscape/ - ambient-idm-rock-... mp3/ra/wav
This archive was generated by hypermail 2b28 : Fri Mar 17 2000 - 21:15:49 EST