From: Daniel Jacobowitz <drow@false.org>
To: alsa-devel@lists.sourceforge.net
Subject: Surround sound and volume control question
Date: Sun, 8 Oct 2006 18:27:26 -0400 [thread overview]
Message-ID: <20061008222726.GA23855@nevyn.them.org> (raw)
How is volume control supposed to work for surround sound codecs? Is there
typically a register which affects every channel, or do you have to adjust
them separately? I've been staring at the datasheets and prodding the
registers for mine (ICE1724, on a Shuttle SN25P). There's three pieces:
the vt1720, the vt1617a, and a wm8728. The vt1617a has ac97 volume control
registers, but the "master" volume doesn't affect the center/lfe or rear
surround channels. I am guessing that the wm8728 is just for the last two
channels (I've got jacks for 7.1 but the vt1617a only does 5.1).
I cobbled together patches that add a stereo mute switch to the softvol
plugin, and set that in front of the card. Then I can actually change
volume or mute the whole set. But for various reasons this is
unsatisfactory, e.g. because it's not called "Master Playback", and because
it doesn't show up as the first mixer element - every application needs a
bit of configuration to find the right volume control. And one of the
applications I wanted to configure, gnome-settings-daemon, is basically
unconfigurable. It just grabs whatever gstreamer sees at the front of the
list.
(The mute patches available on request, btw, one alsa-lib patch and one
kernel driver bugfix for user-created boolean controls.)
Before I go any further with this I want to know how it works elsewhere.
I would think that having a single mixer control that affected all the
surround speakers would be a pretty standard thing to want! Do other chips
have a single register for it? Or does this one, and I'm just not seeing
it?
If I have no other way to get this to work than with the softvol plugin,
I think this is the way to go:
- Rename the "Master" volume control/switch to "Front".
- In userspace, have softvol create a control/switch named "Master".
Potential problems:
- With a library older than kernel driver I think things would start
picking up the Headphone channel as the master volume control if
I made this change, yuck.
- The user-created controls don't exist right away, so saving and
restoring volume might not work.
All comments very welcome - I'm out of my depth here. There's a bit of
related discussion in bug 1407.
--
Daniel Jacobowitz
CodeSourcery
-------------------------------------------------------------------------
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
next reply other threads:[~2006-10-08 22:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 22:27 Daniel Jacobowitz [this message]
2006-10-09 13:37 ` Surround sound and volume control question Takashi Iwai
2006-10-09 13:45 ` Daniel Jacobowitz
2006-10-09 13:49 ` Takashi Iwai
2006-10-09 13:55 ` Lee Revell
2006-10-09 14:38 ` Daniel Jacobowitz
2006-10-09 14:42 ` Lee Revell
2006-10-09 14:50 ` Takashi Iwai
2006-10-09 17:04 ` Daniel Jacobowitz
2006-10-09 17:09 ` Takashi Iwai
2006-10-09 14:53 ` Daniel Jacobowitz
2006-10-10 1:54 ` Anders Johansson
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=20061008222726.GA23855@nevyn.them.org \
--to=drow@false.org \
--cc=alsa-devel@lists.sourceforge.net \
/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.