Subject: Re: [linux-audio-dev] MuCoS, Glame, API Issues
From: David Olofson (david_AT_gardena.net)
Date: la maalis 11 2000 - 19:47:13 EST
On Fri, 10 Mar 2000, Richard Guenther wrote:
> > "host controlled allocation" doesn't specify any particular way of
> > allocating buffers. it describes the division of responsibility. if
> > plugins allocate their own buffers, their actions may not be optimal
> > given the current global situation. if the host does it, it can
> > (presumably) make the best decisions about how to allocate buffers and
> > pass them around. whether it allocates one per plugin, makes them all
> > share, or whatever else, is invisible to the plugins and should be
> > assumed to be "taken care of" by plugin writers.
>
> Umm, well who does know more about which kind of buffer it will need and
> how to allocate/forward it most efficiently but the plugin itself???
There is an important distinction between data _types_ and _actual_
data here. Of course, the plugins get to tell the host what they
support (init time), but after that it's up to the host to manage the
buffers (process time).
Separating these two also has the bonus effect that the host may
change connections in real time as long as this doesn't change what
kind of data the plugins involved will see. (Which is a non-issue
with LADSPA anyway, as a plugins have no dynamic port typing
whatsoever.)
//David
.- M u C o S --------------------------------. .- David Olofson ------.
| A Free/Open Multimedia | | Audio Hacker |
| Plugin and Integration Standard | | Linux Advocate |
`------------> http://www.linuxdj.com/mucos -' | Open Source Advocate |
.- A u d i a l i t y ------------------------. | Singer |
| Rock Solid Low Latency Signal Processing | | Songwriter |
`---> http://www.angelfire.com/or/audiality -' `-> david_AT_linuxdj.com -'
This archive was generated by hypermail 2b28 : su maalis 12 2000 - 09:14:06 EST