alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: jmal8295 <jmal8295@artax.karlin.mff.cuni.cz>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [alsa-cvslog] alsa-kernel: Official ALSA project GIT repository for Linux 2.6 branch, master now at v2.6.31-rc8-407-gfc9e4a3
Date: Wed, 07 Oct 2009 09:59:13 +0200	[thread overview]
Message-ID: <4ACC4A51.1010606@ladisch.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0910070840250.20794@artax.karlin.mff.cuni.cz>

jmal8295 wrote:
> > With the new controls, the only way to change them would be on the
> > command line:
> >   amixer cset iface=PCM,name="PCM Playback Volume",subdevice=x yy
> 
> Hmmm ... that is almost as cumbersome as it could be. Is it at least
> planed to add it to some other mixer, like alsamixer? Another view
> perhaps?

That would be useful (also for the same controls of the Emu10k1 and
DS-1 drivers).

> > BTW: How do you determine which of the four controls is associated with
> > a specific application?
> 
> Trial and error :-).

A mixer application/view that knows about these controls could show the
program name, but that would require that ALSA gives out information
about the process that has opened a substream.

> > In any case, the main purpose of the patch was to rename the controls to
> > prevent "alsactl restore" from restoring the old wrong volume setting,
> > so it would suffice to just change the controls' name in some way, such
> > as from "VIA DXS" to "DXS".
> 
> I would propose to use this oportunity to rename them to something more
> descriptive, but I have no idea what that could be (considering limited
> space in mixer programs).

"PCM Stream"?


Best regards,
Clemens

  reply	other threads:[~2009-10-07  7:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20091006063609.B06E110381F@alsa0.perex.cz>
2009-10-06  7:03 ` [alsa-cvslog] alsa-kernel: Official ALSA project GIT repository for Linux 2.6 branch, master now at v2.6.31-rc8-407-gfc9e4a3 Takashi Iwai
2009-10-06  7:41   ` Clemens Ladisch
2009-10-06  8:00     ` Takashi Iwai
2009-10-08 11:19       ` Clemens Ladisch
2009-10-08 12:15         ` Takashi Iwai
2009-10-08 12:37           ` Clemens Ladisch
2009-10-08 18:11             ` Takashi Iwai
2010-02-24  9:16             ` Clemens Ladisch
2010-02-25 11:22               ` Raymond Yau
2010-02-25 23:52               ` Raymond Yau
2009-10-06 18:11     ` jmal8295
2009-10-07  6:31       ` Clemens Ladisch
2009-10-07  7:07         ` jmal8295
2009-10-07  7:59           ` Clemens Ladisch [this message]
2009-10-06  7:42   ` Jaroslav Kysela
2009-10-06  7:53     ` Clemens Ladisch
2009-10-06  8:27       ` Jaroslav Kysela
2009-10-06  8:30         ` Clemens Ladisch
2009-10-06  8:39           ` Jaroslav Kysela
2009-10-06 13:10             ` Jaroslav Kysela
2009-10-06  8:04     ` Takashi Iwai
2009-10-06  9:31   ` Ozan Çağlayan
2009-10-06 10:11     ` Takashi Iwai

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=4ACC4A51.1010606@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=jmal8295@artax.karlin.mff.cuni.cz \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).