From alsa-devel-owner@alsa.jcu.cz  Sun Oct  4 22:34:41 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 WAA15324;
	Sun, 4 Oct 1998 22:34:19 +0200
Date: Sun, 4 Oct 1998 22:34:16 +0200 (CEST)
From: Jaroslav Kysela <perex@jcu.cz>
To: Stephen Webb <spidey@dodds.net>
cc: alsa-devel@jcu.cz, ericmit@ix.netcom.com
Subject: Re: PCM mixing draft v0.2
In-Reply-To: <Pine.LNX.4.00.9810041254140.15043-100000@viper.dodds.net>
Message-ID: <Pine.LNX.3.96.981004205308.4361J-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 Sun, 4 Oct 1998, Stephen Webb wrote:

> Two things about this. The mixing needs to be done in user space. The
> second have you guys seen how EsounD is coming along! It has alot of
> things you guys have been talking about. Maybe you can integrate it or
> just some of its ideas! 

OK. I must still ask why we cannot mix data in kernel space? EsounD mixing
daemon _CAN_ use this ALSA PCM mixing interface described in draft. This
interface is designed mainly for most efficient way to deliver one stream
to soundcard with minimum delay when data comes to playback.

Current EsounD daemon reads data from streams over net and it is doing
mixing, effect adding and output to exclusive device.

EsounD daemon with ALSA PCM mixing interface should do same function, but
it should use for mixing ALSA driver which can use for mixing hardware (if
possible).

But if author of EsounD have some other meaning we can talk about this...

						Jaroslav

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





