How are multiple capture sources confusing alsamixer?

How are multiple capture sources confusing alsamixer?

[Jonathan Woithe]

Hi all

I've noticed the following comment in a variety of drivers:

  /* The multiple "Capture Source" controls confuse alsamixer
   * So call somewhat different..
   * FIXME: the controls appear in the "playback" view!
   */
  /* .name = "Capture Source", */

I've been working on adding the second capture source to the ALC260 Fujitsu
configuration and have not really seen any major problems with alsamixer's
interpretation when two capture sources are declared.  What seems to happen
for me is that each potential source gets two capture switches; one switches
to the first capture source and the other switches to the second capture
source.  Furthermore, all this appears to work fine.

So, in what way(s) does the presence of multiple capture sources confuse
alsamixer and give rise to the source-code comment quoted above?

Regards
  jonathan


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: How are multiple capture sources confusing alsamixer?

[Lee Revell]

On Mon, 2006-01-16 at 11:51 +1030, Jonathan Woithe wrote:
> Hi all
> 
> I've noticed the following comment in a variety of drivers:
> 
>   /* The multiple "Capture Source" controls confuse alsamixer
>    * So call somewhat different..
>    * FIXME: the controls appear in the "playback" view!
>    */
>   /* .name = "Capture Source", */
> 
> I've been working on adding the second capture source to the ALC260 Fujitsu
> configuration and have not really seen any major problems with alsamixer's
> interpretation when two capture sources are declared.  What seems to happen
> for me is that each potential source gets two capture switches; one switches
> to the first capture source and the other switches to the second capture
> source.  Furthermore, all this appears to work fine.
> 
> So, in what way(s) does the presence of multiple capture sources confuse
> alsamixer and give rise to the source-code comment quoted above?

I think the only issue is that alsamixer has a flat namespace for
controls so you can't have two mixer elements called "Capture Source" in
the same driver.  But, I could be wrong.

Lee



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click

Re: How are multiple capture sources confusing alsamixer?

[Takashi Iwai]

At Sun, 15 Jan 2006 20:32:40 -0500,
Lee Revell wrote:
> 
> On Mon, 2006-01-16 at 11:51 +1030, Jonathan Woithe wrote:
> > Hi all
> > 
> > I've noticed the following comment in a variety of drivers:
> > 
> >   /* The multiple "Capture Source" controls confuse alsamixer
> >    * So call somewhat different..
> >    * FIXME: the controls appear in the "playback" view!
> >    */
> >   /* .name = "Capture Source", */
> > 
> > I've been working on adding the second capture source to the ALC260 Fujitsu
> > configuration and have not really seen any major problems with alsamixer's
> > interpretation when two capture sources are declared.  What seems to happen
> > for me is that each potential source gets two capture switches; one switches
> > to the first capture source and the other switches to the second capture
> > source.  Furthermore, all this appears to work fine.
> > 
> > So, in what way(s) does the presence of multiple capture sources confuse
> > alsamixer and give rise to the source-code comment quoted above?
> 
> I think the only issue is that alsamixer has a flat namespace for
> controls so you can't have two mixer elements called "Capture Source" in
> the same driver.  But, I could be wrong.

That's basically correct.  When you start alsamixer with other cards,
you likely see the capture switch appear on each "Line", "Mic", etc.
This comes from "Capture Source" enum, but the mixer abstraction layer
splits this enum item as if each is a capture "switch".  And, when you
have the secondary "Capture Source" enum, this brings confusion.

For me, the enum style is more intuitive than capthre switch with
hidden mutuality, but it's a matter of taste.  Perhaps would be nice
to have a plugin to change this behavior per configuration...


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642