From alsa-devel-owner@alsa.jcu.cz  Wed Nov 25 19:54:39 1998
Received: from entry.jcu.cz (IDENT:perex@entry.jcu.cz [160.217.1.111])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id TAA23866;
	Wed, 25 Nov 1998 19:53:06 +0100
Date: Wed, 25 Nov 1998 19:53:06 +0100 (CET)
From: Jaroslav Kysela <perex@jcu.cz>
To: "P.J.Leonard" <P.J.Leonard@bath.ac.uk>
cc: alsa-devel@jcu.cz
Subject: Re: Virtual array of audio devices. Filters etc. ?
In-Reply-To: <365C3AFD.2C67@bath.ac.uk>
Message-ID: <Pine.LNX.3.96.981125194624.3161B-100000@entry.jcu.cz>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

On Wed, 25 Nov 1998, P.J.Leonard wrote:

> Hello,
> 
>  Is there any plans to implement a driver that appears appears
> to the application as several device drivers ? This device should
> allow control over the mixing of the inputs. It would also be
> cool if filters (other devices ?) could be chained for each
> channel of the driver. Could a filter use a dynamic linked 
> library to implement it's effect ? This would allow a user to
> implement a new type of filter without having to learn all that
> tricky kernel coding.

We have big discussion about this, but seems that user space is more
reasonable for these things:

PCM stream ---> Audio Server -> conversion -> filters -\
PCM stream ---> Audio Server -> conversion -> filters ---> Kernel driver
PCM stream ---> Audio Server -> conversion -> filters -/

Kernel driver = one exclusive PCM device

EsounD is way for example...

Any other ideas? Comments?

							Jaroslav

-----
Jaroslav Kysela <perex@jcu.cz>
Academic Computer Centre, University of South Bohemia
Branisovska 31, C. Budejovice, CZ-370 05 Czech Republic


