Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751730AbWADLfc (ORCPT ); Wed, 4 Jan 2006 06:35:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751732AbWADLfc (ORCPT ); Wed, 4 Jan 2006 06:35:32 -0500 Received: from gate.perex.cz ([85.132.177.35]:16802 "EHLO gate.perex.cz") by vger.kernel.org with ESMTP id S1751729AbWADLfb (ORCPT ); Wed, 4 Jan 2006 06:35:31 -0500 Date: Wed, 4 Jan 2006 12:35:25 +0100 (CET) From: Jaroslav Kysela X-X-Sender: perex@tm8103.perex-int.cz To: Pete Zaitcev Cc: Alistair John Strachan , kloczek@rudy.mif.pg.gda.pl, Adrian Bunk , Olivier Galibert , Tomasz Torcz , Jan Engelhardt , Andi Kleen , alsa-devel@alsa-project.org, James@superbug.demon.co.uk, sailer@ife.ee.ethz.ch, linux-sound@vger.kernel.org, zab@zabbo.net, kyle@parisc-linux.org, parisc-linux@lists.parisc-linux.org, jgarzik@pobox.com, Thorsten Knabe , zwane@commfireservices.com, linux-kernel@vger.kernel.org Subject: Re: [OT] ALSA userspace API complexity In-Reply-To: <20060104030034.6b780485.zaitcev@redhat.com> Message-ID: References: <20050726150837.GT3160@stusta.de> <20060103193736.GG3831@stusta.de> <20060104030034.6b780485.zaitcev@redhat.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1647 Lines: 40 On Wed, 4 Jan 2006, Pete Zaitcev wrote: > On Wed, 4 Jan 2006 09:37:55 +0000, Alistair John Strachan wrote: > > > > 2) ALSA API is to complicated: most applications opens single sound > > > stream. > > > > FUD and nonsense. [] > > http://devzero.co.uk/~alistair/alsa/ > > That's the kicker, isn't it? Once you get used to it, it's a workable > API, if kinky and verbose. I have a real life example, too: > http://people.redhat.com/zaitcev/linux/mpg123-0.59r-p3.diff > But arriving on the solution costed a lot of torn hair. Look at this > bald head here! And who is going to pay my medical bills when ALSA > causes me ulcers, Jaroslav? Well, the ALSA primary goal is to be the complete HAL not hidding the extra hardware capabilities to applications. So API might look a bit complicated for the first glance, but the ALSA interface code for simple applications is not so big, isn't? Also, note that app developers are not forced to use ALSA directly - there is a lot of "portable" sound API libraries having an ALSA backend doing this job quite effectively. We can add a simple (like OSS) API layer into alsa-lib, but I'm not sure, if it's worth to do it. Perhaps, adding some support functions for the easy PCM device initialization might be a good idea. Jaroslav ----- Jaroslav Kysela Linux Kernel Sound Maintainer ALSA Project, SUSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/