Re: [linux-audio-dev] more on plugins/LADSPA

New Message Reply About this list Date view Thread view Subject view Author view Other groups

Subject: Re: [linux-audio-dev] more on plugins/LADSPA
From: Kai Vehmanen (kaiv_AT_wakkanet.fi)
Date: Wed Mar 15 2000 - 15:51:49 EST

On Wed, 15 Mar 2000, Paul Barton-Davis wrote:

>> 1) Something like BeOS MediaNodes. Very heavy weight, more like full
>> apps that can be piped together.
>> 2) Statically allocated large processes/effects with GUIs,
>> automation. VST
>> and TDM plugins fall here.
>> 3) Lightweight unit generators. MSP, Csound, SC unit generators.
> I think that this is *VERY, VERY* important. We need to make sure that
> we define the level(s) that LADSPA is intended to cover. Then we need

Yes, this is an important question. I'm leaning towards option '2'.
It's the easiest one, and thus fits the "simple" in LADSPA
(and the current model). A good specification in case '1' requires a lot
more work, while '3' isn't enough for everybody (= requires a more complex
host).

But hey, everyone else, what do you think? If our goal is to make LADSPA
as widely accepted as possible, then the initial design should be usable
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
API :)). When applications range from SuperCollider/Quasimodo -> mp3
players, we have to make compromises.

PS Added a htdig-based search to LAD archives - http://eca.cx/lad 

-- 
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

New Message Reply About this list Date view Thread view Subject view Author view Other groups

This archive was generated by hypermail 2b28 : Wed Mar 15 2000 - 23:16:22 EST