alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Raymond Yau <superquad.vortex2@gmail.com>
To: 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: Fri, 26 Feb 2010 07:52:09 +0800	[thread overview]
Message-ID: <4f3252891002251552v17057febg83e039a8e9159175@mail.gmail.com> (raw)
In-Reply-To: <4B84EE72.4060707@ladisch.de>

2010/2/24 Clemens Ladisch <clemens@ladisch.de>

> I wrote:
> > > > jmal8295 wrote:
> > > > > And I _will_ be regarding it as regression if I lose possibility to
> > > > > change volume of the four streams independently.
> >
> > Okay, I'll see if I can extend alsamixer ...
>
> Well, those controls are quite hardware-specific, and I always wanted to
> try out the Python wrappers, so I wrote a separate application.
>
> Honza, if you have a new kernel and the latest released alsa-lib and
> alsa-python packages, please try downloading the latest alsa-tools
> snapshot from <http://www.alsa-project.org/snapshot/> and check the
> hwmixvolume tool.
>
>
> Regards,
> Clemens
>

The characteristic of the VXS Volume controls are changed after the type of
the controls are changed from IFACE_MIXER to IFACE_PCM

extend alsamixer seem break the definition of those  IFACE_PCM PCM Playback
Volume control since the driver should reset IFACE_PCM PCM playback volume
to 0dB whenever the subdevice is opened since most of the alsa applications
don't check whether the sound card support hardware mixing

  parent reply	other threads:[~2010-02-25 23:52 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 [this message]
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
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=4f3252891002251552v17057febg83e039a8e9159175@mail.gmail.com \
    --to=superquad.vortex2@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    /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).