Subject: Re: [linux-audio-dev] Client/Server audio system
From: David Olofson (david_AT_gardena.net)
Date: Wed Mar 15 2000 - 23:36:07 EST
On Mon, 13 Mar 2000, Maurizio DE CECCO wrote:
> Stephane Letz wrote:
>
> > We are currently trying to develop a client/server audio system using the
> > approach used in MidiShare.
>
> [ ... ]
>
> > Any comments?
>
> What about latency ? A timestamped approach seems ok in a context
> where everything is generated internally (like playing back dtd audio
> and MIDI at the same time), and would hide most of the latency.
>
> But if you are processing a external audio stream, would the latency
> introduced by this approach reasonable ? (context switch, call backs,
> etc )
This depends on how the events are passed. The MuCoS idea is that
events are a structured form of data rather than either real time
function calls or arrays of data. That is, multiple events can be
sent on every port over a single context switch - resulting in a very
flexible interface with no more context switch overhead than the "good
old" plain-buffers-of-fixed-size approach.
Now, I'm not sure how the "Audio MidiShare" system is going to handle
it, but from what I can remember from the MidiShare docs I've seen,
it's not all that different from what the MuCoS client/server API
will look like.
//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 : Thu Mar 16 2000 - 06:52:44 EST