From: Lennart Poettering <mznyfn@0pointer.de>
To: ALSA Development Mailing List <alsa-devel@alsa-project.org>
Subject: Master vs. Front/Rear/LFE/... elements
Date: Wed, 6 May 2009 19:58:24 +0200 [thread overview]
Message-ID: <20090506175824.GA30355@tango.0pointer.de> (raw)
Heya!
Some cards expose 'Master' volume sliders. Others expose seperate
(stereo) sliders for 'Front', 'Rear' and so on. I have trouble dealing
with them properly in PulseAudio:
First of all, on some cards 'Master' seems not to have any effect on
the actual analog output, only 'Front' and friends do. Is this a bug
or intended behaviour? Can I assume that 'Master' and 'Front' are
always independant?
Secondly, I have trouble supporting the
'Front'/'Rear'/'Side'/... elements properly, since they split up the
surround channels into seperate elements. Now, this is confusing in
many ways, even for "amixer" which will then show channels such as
"Rear Front Left" and so on, which obviously make no
sense. snd_mixer_selem_has_playback_channel() just returns bogus data
for these cases. Why are those elements seperate anyway? Why aren't
they combined into a single multi-channel event? Looking at the APIs I
get the idea that the problem appears to be that elements can only
control all channels the same are all independantly which doesn't
really match 1:1 on my multichannel sound cards. However, wouldn't it
be possible to use the 'index' value of a selem_id for this? I.e. have
a series of controls by the same name but different indexes which
would then implement snd_mixer_selem_has_playback_channel() correctly?
i.e. foo,0 would do front-left/right, foo,1 would do rear, foo,2 would
do lfe, and so? I have no clue how this implemented internally, so not
sure how feasible this might be.
Lennart
--
Lennart Poettering Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/ GnuPG 0x1A015CC4
next reply other threads:[~2009-05-06 17:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 17:58 Lennart Poettering [this message]
2009-05-07 8:49 ` Master vs. Front/Rear/LFE/... elements Takashi Iwai
2009-05-07 10:09 ` Mark Brown
2009-05-07 10:30 ` Takashi Iwai
2009-05-07 10:53 ` Mark Brown
2009-05-07 12:56 ` Lennart Poettering
2009-05-07 13:10 ` Mark Brown
2009-05-07 13:12 ` Pavel Hofman
2009-05-08 6:36 ` Eliot Blennerhassett
2009-05-07 12:46 ` Lennart Poettering
2009-05-07 13:18 ` Takashi Iwai
2009-05-09 22:11 ` Lennart Poettering
2009-05-11 9:26 ` Takashi Iwai
2009-05-12 7:47 ` James Courtier-Dutton
2009-05-12 8:02 ` Jaroslav Kysela
2009-05-12 9:21 ` Mark Brown
2009-05-12 13:15 ` Lennart Poettering
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=20090506175824.GA30355@tango.0pointer.de \
--to=mznyfn@0pointer.de \
--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 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.