From alsa-devel-owner@alsa.jcu.cz  Thu Jan 28 20:25:18 1999
Received: from dark.x.dtu.dk (IDENT:qmailr@dark.x.dtu.dk [130.225.92.246])
	by marvin.jcu.cz (8.9.1a/8.9.1) with SMTP id UAA20867
	for <alsa-devel@alsa.jcu.cz>; Thu, 28 Jan 1999 20:25:06 +0100
Received: (qmail 32300 invoked by uid 506); 28 Jan 1999 19:25:04 -0000
Date: Thu, 28 Jan 1999 20:25:04 +0100
From: Magnus Norddahl <mbn@dark.x.dtu.dk>
To: alsa-devel@alsa.jcu.cz
Subject: Re: alsa driver forgets settings between close and open
Message-ID: <19990128202504.B32076@dark.x.dtu.dk>
References: <19990128011914.C12308@dark.x.dtu.dk> <Pine.LNX.3.96.990128160649.4780U-100000@entry.jcu.cz>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
In-Reply-To: <Pine.LNX.3.96.990128160649.4780U-100000@entry.jcu.cz>; from Jaroslav Kysela on Thu, Jan 28, 1999 at 04:13:09PM +0100
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list

Quoting Jaroslav Kysela (perex@jcu.cz):

> You are speaking about OSS emulation then this feature will break
> compatibility with OSS. If we are speaking about ALSA native PCM
> interface, I don't see any reason why implement this. I think that there
> isn't any problem create some simple program which sets specific playback
> or record parameters and write or read some data from or to stream.

I agree as long it only applies to simple things such as frequency, sample
format and stereo. But I just think it will make it easier to produce buggy
applications, if more advanced settings such as fragment sizes and such
would also be remembered.

-- 
Magnus Norddahl
ClanSoft

