From alsa-devel-owner@alsa.jcu.cz  Wed Jan 27 22:23:32 1999
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 WAA18156;
	Wed, 27 Jan 1999 22:23:08 +0100
Date: Wed, 27 Jan 1999 22:23:07 +0100 (CET)
From: Jaroslav Kysela <perex@jcu.cz>
To: Harald Kirsch <kir@iitb.fhg.de>
cc: alsa-devel@alsa.jcu.cz
Subject: Re: alsa driver forgets settings between close and open
In-Reply-To: <19990127162928.A7121@neptun.iitb.fhg.de>
Message-ID: <Pine.LNX.3.96.990127221747.4304A-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, 27 Jan 1999, Harald Kirsch wrote:

> Hi there,
> 
> currently I am starting to work with alsa. In contrast to many other
> my main purpose is not to play/record music for fun, but I want to
> perform some signal processing and analysis tasks. 
> 
> Having implemented device drivers for A/D-converters myself, I wonder
> why alsa (as well as other sound modules for Linux) always forget (or
> reset) settings like frequency after the device is closed. That way 
> 
>  !!! every program interacting with the device must do its own setup !!!
> 
> On the other hand, if setting would be persistent after a close and a
> subsequent open by another program, it would be possible to have just
> one single program to set driver settings. After they are set as
> necessary, playback as well as recording could proceed with just cat, dd 
> or, in my own program, with a simple sequence of open/read,write/close.
> 
> Do you think it will be possible in the future to have pesistent
> settings in alsa?

No, I don't see any improvement of driver with this way.
Any comments from others?

							Jaroslav

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


