From: Randy Cushman <rcushman_linux@earthlink.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Inexplicable mixer control creation
Date: Fri, 16 Mar 2007 13:45:08 -0400 [thread overview]
Message-ID: <45FAD7A4.4040408@earthlink.net> (raw)
In-Reply-To: <s5hslc5us22.wl%tiwai@suse.de>
[-- Attachment #1.1: Type: text/plain, Size: 2145 bytes --]
Takashi Iwai wrote:
> At Tue, 13 Mar 2007 20:21:08 -0400,
> Randy Cushman wrote:
>
>> In attempting to implement my proposed mixer control name changes (see
>> "[Alsa-devel] RFC: Enhance AD AC '97 mixer control names") I have
>> encountered behavior that makes no sense to me: If module
>> snd_ac97_codec does not create a control with the name 'PCM Playback
>> Volume' then something else creates a control with that name. Not
>> surprisingly, this phantom control serves no useful purpose in my
>> environment, as it has no affect on AC '97 control registers.
>>
>
> This is done by softvol plugin used in the default configuration for
> many onboard chip drivers. See alsa-lib/src/conf/cards/*.conf.
>
>
I haven't spent much time in alsa-lib. I'll take a look.
This may be a good time to mention that I am unable to access the
Mercurial repository. If I try to access
http://hg-mirror.alsa-project.org in a web browser or use the "hg clone"
command, I get "HTTP Error 403: Forbidden". Curiously, I can "hg diff"
repositories I cloned previously. (I opened bugtrack ticket #2956 this
morning.)
In the mean time, I'll look at alsa-lib-1.0.14rc3.
> That's actually a point that I missed. Many apps assume either
> "Master" or "PCM" mixer exists. Thus, removing PCM isn't nice for
> them.
>
>
> Now I'm considering whether changing the volume names in the driver
> level is actually a better choice. It's basically simpler, and I
> prefer a simpler solution. OTOH, it may bring other messes because of
> the name incompatibility like above. So, the cleanest solution would
> be some mangling in the user-space, i.e. inside alsa-lib. But, it's
> a bit harder way.
>
>
I was planning to change the names by calling snd_ac97_rename_vol_ctl()
from functions patch_ad1986_specific(), etc. in ac97_patch.c. I'll
explore the alsa-lib approach.
> So, before doing this -- we have to *seriously* consider to get
> consensus what control names should be used as standard and how they
> behave. Maybe better to start another thread for discussing this...
>
>
I can start another thread.
> Takashi
>
>
>
[-- Attachment #1.2: Type: text/html, Size: 2920 bytes --]
[-- Attachment #2: Type: text/plain, Size: 345 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 161 bytes --]
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
prev parent reply other threads:[~2007-03-16 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-09 15:53 RFC: Enhance AD AC '97 mixer control names Randy Cushman
2007-03-12 12:27 ` Takashi Iwai
2007-03-14 0:21 ` Inexplicable mixer control creation Randy Cushman
2007-03-16 15:27 ` Takashi Iwai
2007-03-16 17:45 ` Randy Cushman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=45FAD7A4.4040408@earthlink.net \
--to=rcushman_linux@earthlink.net \
--cc=alsa-devel@alsa-project.org \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.