[alsa-devel] CMI8788/AV200/Oxygen Volume Controls in alsamixer (oxygen_mixer.c:dac_volume_get())
John.Utz at dmx.com
Fri Jan 23 20:21:57 CET 2009
From: Clemens Ladisch [mailto:clemens at ladisch.de]
Sent: Fri 1/23/2009 6:13 AM
To: Takashi Iwai
Cc: ALSA Developers; John Utz
Subject: Re: [alsa-devel] CMI8788/AV200/Oxygen Volume Controls in alsamixer (oxygen_mixer.c:dac_volume_get())
Takashi Iwai wrote:
> Clemens Ladisch wrote:
> > Alsamixer chooses to display an eight-channel control this way. This
> > can be considered a bug in alsamixer.
> The current ALSA mixer abstraction splits the multi-channels into
> separate paired channels. But alsamixer can't show the channel name
> due to its UI design.
The its UI design should be changed.
JU It's *not* the UI, amixer shows the same thing
> A solution would be make individual control like "Front", and create a
> virtual master control.
I am *not* going to change the driver just to accommodate to alsamixer.
JU nobody is asking you to, if my employer decides that we will use the card (not entirely clear, it's expensive and IMHO the sound quality isnt worth the money) then i will be tasked with making this work.
JU i will figure out a functional solution that allows the CMI8788 to appear to our app as a 'ALSA traditional' mixer api, be it compiled code or alsa card config fu.
I am going to change alsamixer to display the channel names (which it
JU I am thinking that this perspective is not likely to lead to a successful outcome.
JU Do keep in mind that your current implementation *works* for *humans*, they can figure out which is the right slider to move.
JU *Programs* are hosed tho, because they depend on unique control identification.
JU I will save my rant about how misguided it was to put english strings in a driver for another day. :-(
JU We are stuck with it. The only way that will change will be if a new sound project where to be invented, just like ALSA replaced OSS.
More information about the Alsa-devel