From mboxrd@z Thu Jan 1 00:00:00 1970 From: Takashi Iwai Subject: Re: How to display mixer controls to the user? was:Re: [PATCH/RFC] emu10k1 multichannel PCM Date: Wed, 17 Nov 2004 12:54:54 +0100 Message-ID: References: <1100300857.19038.14.camel@krustophenia.net> <1100405924.16103.23.camel@krustophenia.net> <4197433E.80008@superbug.co.uk> Mime-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Return-path: In-Reply-To: <4197433E.80008@superbug.co.uk> Sender: alsa-devel-admin@lists.sourceforge.net Errors-To: alsa-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: James Courtier-Dutton Cc: Lee Revell , alsa-devel List-Id: alsa-devel@alsa-project.org At Sun, 14 Nov 2004 11:36:30 +0000, James Courtier-Dutton wrote: > > Lee Revell wrote: > > On Fri, 2004-11-12 at 18:07 -0500, Lee Revell wrote: > > > >>This patch is still missing a few things, like dynamic voice allocation > >>and correctly setting the send routing, but it does work with JACK, and > >>should not interfere with the operation of the other devices. I tested > >>it like so: > > > > > > Here is a patch that adds the mixer controls for this device. This > > includes the previous patches (add multichannel support and add register > > dump to /proc) Unfortunately this adds 16 x 3 mixer controls... people > > complain enough about the emu10k1 mixer already, so this might not be > > well received in some circles. I am not sure what to do about this. > > The kX mixer probably has hundreds of controls, but they are arranged in > > a tree structure. > > > > I have similar problems with the mixer controls. If I add > p16v(24bit/96khz etc.) support to the emu10k1 driver, it will add a load > more controls. For example, the volume controls for the 96khz channel > are separate from the volume controls for emu10k1 48khz channels. > Maybe we need to start discussing ways to separate out mixer controls > better. > E.g. > Global controls. > Controls specific to a pcm device. > Controls specific to a particular section of DSP code. They can be specified via different iface values. For example, the above cases can be distinct with IFACE_MIXER, IFACE_PCM and IFACE_CARD (or HWDEP), respectively. IMO, the emu10k1 routing should go to IFACE_PCM instead of IFACE_MIXER. (Who wants to change it on the mixer?) Well, we have to be still careful about the compatibility, though... Takashi ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8