From: Eliot Blennerhassett <eliot@blennerhassett.gen.nz>
To: "Nikita N." <nikitan@operamail.com>, alsa-devel@alsa-project.org
Cc: Clemens Ladisch <clemens@ladisch.de>
Subject: Re: potential speaker burnout
Date: Tue, 31 Mar 2015 21:41:05 +1300 [thread overview]
Message-ID: <551A5DA1.2070603@blennerhassett.gen.nz> (raw)
In-Reply-To: <1427789953.2143209.247430925.7143290B@webmail.messagingengine.com>
On 31/03/15 21:19, Nikita N. wrote:
>> And in my opinion, you are blaming the wrong party here.
> we are not blaming anybody.
You talk about finding the person who is "guilty"
>> (Yes I can confirm that happens on my laptop with mic gain set to 20dB below maximum).
> Thank you very much for your confirmation, so in the meantime we start
> as blacklisting that tool from our repos.
I agree it would be upsetting to have your laptop speakers go up in smoke.
But I reiterate, it is not the alsamixergui tool. ANY tool that is
capable of adjusting the underlying controls of the soundcard is capable
of reproducing the effect. I.e. commandline "amixer", terminal
"alsamixer', possibly others...
You would be better to blacklist the problematic laptop hardware, not
these control apps.
The one thing maybe worth thinking about is whether there is any useful
purpose for the control that enables direct feed from microphone to
speakers? This is something that is provided by the underlying sound
driver, and would need to be "fixed" there.
I.e. your distro would have to patch drivers before building the kernel.
next prev parent reply other threads:[~2015-03-31 8:41 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 14:03 bug Nikita N.
2015-03-30 7:19 ` bug Clemens Ladisch
2015-03-30 10:27 ` bug Nikita N.
2015-03-30 11:13 ` bug Clemens Ladisch
2015-03-30 14:37 ` bug Nikita N.
2015-03-31 7:18 ` bug Eliot Blennerhassett
2015-03-31 8:19 ` bug Nikita N.
2015-03-31 8:38 ` bug Clemens Ladisch
2015-03-31 9:05 ` bug Nikita N.
2015-03-31 12:42 ` bug Clemens Ladisch
2015-03-31 8:41 ` Eliot Blennerhassett [this message]
2015-03-31 8:24 ` bug Ricard Wanderlof
2015-03-31 8:56 ` bug Nikita N.
2015-03-31 9:14 ` bug Ricard Wanderlof
2015-03-31 10:26 ` bug Maarten de Boer
2015-03-31 10:49 ` bug Nikita N.
2015-03-31 11:05 ` bug Maarten de Boer
2015-03-31 11:44 ` bug Ricard Wanderlof
2015-03-31 8:54 ` bug Eliot Blennerhassett
2015-03-31 9:34 ` Speaker burnout David Henningsson
2015-03-31 10:06 ` Nikita N.
2015-03-31 10:43 ` David Henningsson
2015-03-31 10:57 ` Alexander E. Patrakov
2015-03-31 11:23 ` Nikolay Dimitrov
2015-03-31 11:31 ` Ricard Wanderlof
2015-03-31 11:45 ` David Henningsson
2015-03-31 13:47 ` Torsten Schenk
2015-03-31 19:14 ` Nikita N.
2015-04-05 16:36 ` Takashi Iwai
2015-04-05 16:11 ` Takashi Iwai
2015-04-07 5:30 ` Eliot Blennerhassett
2015-04-07 7:09 ` David Henningsson
2015-04-07 7:26 ` Clemens Ladisch
2015-04-07 7:49 ` Eliot Blennerhassett
2015-04-07 10:55 ` David Henningsson
2015-04-07 11:29 ` Ricard Wanderlof
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=551A5DA1.2070603@blennerhassett.gen.nz \
--to=eliot@blennerhassett.gen.nz \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=nikitan@operamail.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.