Subject: Re: [alsa-devel] Re: [linux-audio-dev] Re: Toward a modularizationof audio component
From: Jim Peters (jim_AT_aguazul.demon.co.uk)
Date: Sat May 05 2001 - 16:26:42 EEST
Abramo Bagnara wrote:
> I think there is some misunderstanding, the solution I proposed for
> single thread audio engine is the following:
>
>
> audio_producer1 ----\
>
> audio_producer2 -----\ /-- audio_consumer1
> > engine <
> audio_producer3 -----/ \-- audio_consumerN
>
> audio_producerN ----/
I can't make sense of this, because for me the server engine is BIG,
enclosing all the producers and consumers, which talk amongst
themselves inside it:
(GUI for a plugin) (ALSA pcm_shm interface to
|| || some other process)
+--------------------------||------------------||----------------+
| ENGINE, containing: (more plugins) |
| | |
| [HW input via ALSA] -> [plugin] -> [plugin] -> (whatever) |
| | | |
| [plugin] <- [plugin] -> [plugin] |
| | |
| (whatever) -> [HW output via ALSA] |
| |
+-----||------------------------||-------------------------------+
|| ||
(GUI for a plugin) (GUI for a plugin)
I think it may be useful to think of this server as a special
environment for running parts of applications that need special
conditions - particularly low latency. It's not too far off the kind
of environment within a dedicated DSP card - it's a bit like emulating
the environment and beneficial features of a DSP card on standard
hardware. You'd never run your GUI on your DSP card - you'd just use
the DSP card for the critical stuff, and have the GUI outside talking
to it. It is the same here.
Also, the rules that apply in the rest of your OS don't apply within
your DSP card because the conditions are so different and so highly
tuned for the particular application.
Jim
--
Jim Peters / __ | \ Aguazul
/ /| /| )| /| / )|| \
jim_AT_aguazul. \ (_|(_|(_|(_| )(_|I / www.aguazul.
demon.co.uk \ ._) _/ / demon.co.uk
This archive was generated by hypermail 2b28 : Sat May 05 2001 - 19:02:38 EEST