Subject: Re: [linux-audio-dev] LAAGA - how are we doing ?
From: Kai Vehmanen (kaiv_AT_wakkanet.fi)
Date: Sat May 05 2001 - 20:42:41 EEST
On Sat, 5 May 2001, Jim Peters wrote:
> I think we are going to have to talk about how applications are going
> to get connected together once they have loaded their plugin into the
> server. Paul mentioned some idea about each application providing the
> means to select the channels or busses it uses. I put forward the
Like I said on one of my early LAAGA posts, I'd like to avoid talking
about channels, busses or plugin networks when it comes to LAAGA. A LAAGA
client requests for a set of audio channels or ports, and gets a set of
integer ids from the server. When plugin then wants to access
(read/write) the actual audio buffer, it uses the
write_to_channel/read_from_channel callbacks provided by the server, and
gives the assigned channel identifier as an argument to these
functions.
Paul already suggested to extend this design by allowing clients for
getting 'available_channels() type information from the server. But I'm
still not sure if this is needed. I'd like to concentrate on just passing
the data.
In my desing, it's up to the server to care about which buffers are
assigned to plugins, whether multiple plugins are assigned to same
channels, whether input and output buffers are physically the same
(=inplace), etc, etc ... The LAAGA API definition does not even mention
these things.
-- http://www.eca.cx Audio software for Linux!
This archive was generated by hypermail 2b28 : Sat May 05 2001 - 20:26:27 EEST