Subject: Re: [linux-audio-dev] Plugin APIs (again)
From: David Olofson (david_AT_olofson.net)
Date: Sun Dec 08 2002 - 02:19:08 EET
On Sunday 08 December 2002 01.02, Tim Hockin wrote:
> > > Why? What is it that LADSPA does that would be so complicated
> > > that an instrument API must not support it?
> >
> > Nothing, OAPI or whatever will be a superset I imagine, but that
> > implies that LADSPA will still be simpler.
>
> yeah, and I want to make it easy for an OAPI (I HATE that name -
> open to ideas..) host to use LADSPA plugins. That is very
> important.
Of course. And there should be nothing preventing that. Unless I'm
missing something, the only really significant difference is that
LADSPA plugins don't have event ports, while "New API" plugins will.
You could probably even build a simple event->control semi-wrapper
into the host, to make LADSPA plugins fit in with minimal impact on
the rest of the host code. LADSPA plugins will then act just like
"New API" plugins that quantize timestamps to buffer boundaries. Or
you can have the semi-wrapper do full or quantized buffer splitting...
//David Olofson - Programmer, Composer, Open Source Advocate
.- The Return of Audiality! --------------------------------.
| Free/Open Source Audio Engine for use in Games or Studio. |
| RT and off-line synth. Scripting. Sample accurate timing. |
`---------------------------> http://olofson.net/audiality -'
.- M A I A -------------------------------------------------.
| The Multimedia Application Integration Architecture |
`----------------------------> http://www.linuxdj.com/maia -'
--- http://olofson.net --- http://www.reologica.se ---
This archive was generated by hypermail 2b28 : Sun Dec 08 2002 - 02:23:46 EET