From: Raymond Yau <superquad.vortex2@gmail.com>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Re: Handling of the DXS controls in the via82xx driver
Date: Mon, 29 Mar 2010 09:24:33 +0800 [thread overview]
Message-ID: <4f3252891003281824r4544d4bfv811f9c4e4d98381@mail.gmail.com> (raw)
In-Reply-To: <4BAE8EF7.20204@gmx.de>
2010/3/28 Soeren D. Schulze <soeren.d.schulze@gmx.de>
> Hi everyone,
>
> before my latest upgrade to Linux 2.6.32 (yes, sorry, it's Debian), I
> had four levers in my alsamixer: VIA DXS, VIA DXS 1, VIA DXS 2 and VIA
> DXS 3. They controlled the hardware mixing when accessing the sound
> device multiple times.
>
> Now they have disappeared. I think I can pretty certainly trace this
> down to commit 2fb930b53f513cbc4c102d415d2923a8a7091337 to Linux
> [
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commit;h=2fb930b53f513cbc4c102d415d2923a8a7091337
> ],
> which "move[s] DXS volume controls to PCM interface".
>
> As I'm not an ALSA developer, I don't realize the intended effect of
> this change, but the actual effect is that I cannot change the DXS
> volumes any more. mplayer still controls the global PCM volume. Well,
> in fact, there is one way. While an mplayer is running, I can do:
>
> amixer cset numid=47,iface=PCM,name='PCM Playback Volume' 24,24
>
> When restarting mplayer, the volume is reset to 31,31 (maximum). Commit
> 3d00941371a765779c4e3509214c7e5793cce1fe
> [
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.33.y.git;a=commit;h=3d00941371a765779c4e3509214c7e5793cce1fe
> ]
> seems to be responsible for this.
>
> The bad thing about it is that 31,31 is a really bad setting for my
> poorly engineered sound card. It distorts a lot.
>
> I suspect that the real *bug* is that mplayer does not use the
> per-channel DXS controls even though it's supposed to (which seems to be
> why the DXS controls are called "PCM Playback Volume").
>
> Personally, rather than fixing this bug, I would just revert to the
> former state. I was always happy with all the DXS levers set to 75%.
>
>
> Thank you
>
> Sören
>
Those are per voice volume control , they can be used for the hardware
acclearation in wine if wine implmenet the real hardware acceleration
After this change , they are not used by the mixer any more , only those
application which open those subdevices can find the corresponding control
by the subdevice number
next prev parent reply other threads:[~2010-03-29 1:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-27 23:04 Handling of the DXS controls in the via82xx driver Soeren D. Schulze
2010-03-29 1:24 ` Raymond Yau [this message]
2010-03-29 1:39 ` Raymond Yau
2010-03-29 12:56 ` Clemens Ladisch
2010-03-29 13:21 ` Soeren D. Schulze
2010-03-31 23:00 ` Raymond Yau
2010-03-31 1:39 ` Raymond Yau
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=4f3252891003281824r4544d4bfv811f9c4e4d98381@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).