From: Stas Sergeev <stsp@aknet.ru>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: ALSA devel <alsa-devel@alsa-project.org>
Subject: Re: how to mandate the use of PCM plugin?
Date: Mon, 27 Sep 2010 10:53:49 +0400 [thread overview]
Message-ID: <4CA03F7D.8040602@aknet.ru> (raw)
In-Reply-To: <20100927055438.GA13129@opensource.wolfsonmicro.com>
27.09.2010 09:54, Mark Brown wrote:
> > What I am trying to solve, is the problem
> > that people have with my snd-pcsp driver.
> > Pulseaudio uses "hw" to bypass some pcm
> > plugins, and then people are left with the
> > non-functional softvol control, and they blame
> > my driver.
> > I am looking for the way to mandate the
> > softvol plugin even for the "hw" device.
> Why not work on fixing the actual problem if it's not already been
> fixed?
I am not sure what's the actual fix would
look like. I wasn't followed the alsa development
for a long time. Is there a way to consistently
replace the softvol controls? If so, then there is
a bug somewhere. Also, the snd-pcsp is configured
to use the "asym" plugin - I wonder if it is safe to
replace also that.
So the question is: can _all_ the plugins be safely
replaced by the software that opens "hw", or,
maybe, some are not, and then, they should be
somehow mandated?
>> Is this possible?
> No, and it would still be unhelpful since it would leave you with two
> soft volume controls in operation.
>
But this is not a real problem, this is the same
as if you have the volume control in the hardware.
You then also have 2 volume controls, or more.
And pulseaudio can just check whether or not
the volume control is present, and then simply not
to add its own. I dont think this is a real problem.
The real problem is when the mixer bar doesn't
work at all. :)
So what the real fix do you think of?
next prev parent reply other threads:[~2010-09-27 6:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-26 15:17 how to mandate the use of PCM plugin? Stas Sergeev
2010-09-27 0:58 ` Mark Brown
2010-09-27 4:48 ` Stas Sergeev
2010-09-27 5:54 ` Mark Brown
2010-09-27 6:53 ` Stas Sergeev [this message]
2010-09-27 22:00 ` Mark Brown
2010-09-28 5:38 ` Stas Sergeev
2010-09-28 9:36 ` Raymond Yau
2010-09-27 14:40 ` Stas Sergeev
2010-09-27 17:57 ` Colin Guthrie
2010-09-28 1:01 ` Raymond Yau
2010-09-28 4:07 ` Raymond Yau
2010-09-29 9:28 ` David Henningsson
2010-10-02 2:11 ` Raymond Yau
2010-10-04 7:51 ` Alsamixertest (was: how to mandate the use of PCM plugin?) David Henningsson
2010-10-04 12:01 ` Alsamixertest Clemens Ladisch
2010-10-04 12:25 ` Alsamixertest David Henningsson
2010-10-04 12:34 ` Alsamixertest Clemens Ladisch
2010-10-06 4:08 ` Alsamixertest Raymond Yau
2010-10-05 1:50 ` Alsamixertest Raymond Yau
2010-10-12 14:33 ` Alsamixertest Raymond Yau
2010-10-21 4:36 ` Alsamixertest Raymond Yau
2010-10-21 7:50 ` Alsamixertest David Henningsson
2010-10-22 1:53 ` Alsamixertest 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=4CA03F7D.8040602@aknet.ru \
--to=stsp@aknet.ru \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
/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.