From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: generic mixer control? Date: Mon, 16 Sep 2002 12:36:12 +0200 Sender: alsa-devel-admin@lists.sourceforge.net Message-ID: References: <200209131319.g8DDJCk13884@op.net> Mime-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from Cantor.suse.de (ns.suse.de [213.95.15.193]) by alsa.alsa-project.org (8.9.3/8.9.3/SuSE Linux 8.9.3-0.1) with ESMTP id MAA11150 for ; Mon, 16 Sep 2002 12:36:14 +0200 In-Reply-To: Errors-To: alsa-devel-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Unsubscribe: , List-Archive: To: Jaroslav Kysela Cc: Paul Davis , "alsa-devel@alsa-project.org" List-Id: alsa-devel@alsa-project.org At Fri, 13 Sep 2002 17:30:55 +0200 (CEST), Jaroslav wrote: > > On Fri, 13 Sep 2002, Paul Davis wrote: > > > i don't enough about ALSA's handling of consumer mixers to know if > > this is possible, but ... i was wondering if there is anyway to write > > a generic chunk of code for JACK that manipulates a consumer-oriented > > card's mixer to provide hardware mixing. the basic process would be to > > turn up the "capture gain" volume so that you get to hear whatever > > is being recorded. you might have to turn down something else as well, > > but thats probably secondary. > > > > its not clear to me whether or not many mixers come with a single > > control that can do this, and/or whether there is any standard way to > > do this that ALSA "exports" to the world. > > > > any comments? i'd like to provide "hardware monitoring" for users of > > consumer oriented cards to supplement the hammerfall and ice1712 stuff > > that we already have ... > > Although the task is easy, the implementation is not. We definitely need > to define some abstract controls like this in mixer and describe the > complicated consumer mixers in configuration files like abstract PCM > devices. yes, this is what i've longed for. this will make it possible to create a "reasonable" mixer program, too. but for this we need an extra database. and the problem is that the mixer topology depends not only on the sound chip but on codecs connected, too. perhaps exporting pci subdevice id and checking it will give a workaround for special cards even without changing the driver code itself. Takashi ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf