From: Clemens Ladisch <clemens@ladisch.de>
To: "Nikita N." <nikitan@operamail.com>
Cc: alsa-devel@alsa-project.org,
Eliot Blennerhassett <eliot@blennerhassett.gen.nz>
Subject: Re: bug
Date: Tue, 31 Mar 2015 14:42:08 +0200 [thread overview]
Message-ID: <551A9620.6090308@ladisch.de> (raw)
In-Reply-To: <1427792714.2152814.247446829.32E51ED1@webmail.messagingengine.com>
Nikita N. wrote:
>> http://www.iua.upf.es/~mdeboer/projects/alsamixergui/
>
> this link is broken, please provide a correct one
This is the last known link.
>> Please note that _every_ mixer application on _every_ OS might be able
>> to set the controls to those dangerous values.
>
> is it "might" or it is?
I was not able to test all of them. But I would be surprised if there
is any mixer that knows about this broken hardware and somehow restricts
the mixer ranges.
> Is also your alsamixer textual version tool, capable of speakers
> burnout?
As I already wrote above, on that hardware, I estimate that _every_
mixer tool is capable of that.
Regards,
Clemens
next prev parent reply other threads:[~2015-03-31 12:42 UTC|newest]
Thread overview: 44+ 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 ` Clemens Ladisch [this message]
2015-03-31 8:41 ` potential speaker burnout Eliot Blennerhassett
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
-- strict thread matches above, loose matches on Subject: below --
2019-09-02 3:52 bug liebrecht
[not found] <520268D8.3000807@gmail.com>
2013-08-07 17:14 ` bug Mattia Bertoni
2013-08-08 8:44 ` bug Mattia Bertoni
2013-08-08 9:00 ` bug Takashi Iwai
2013-08-08 9:55 ` bug Mattia Bertoni
2013-08-08 10:12 ` bug Takashi Iwai
2013-08-08 10:44 ` bug Mattia Bertoni
2013-08-08 10:49 ` bug Takashi Iwai
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=551A9620.6090308@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=eliot@blennerhassett.gen.nz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox