All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Ricard Wanderlof <ricard.wanderlof@axis.com>
To: "Nikita N." <nikitan@operamail.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Maarten de Boer <maarten@resorama.com>
Subject: Re: bug
Date: Tue, 31 Mar 2015 13:44:45 +0200	[thread overview]
Message-ID: <alpine.DEB.2.02.1503311334370.13892@lnxricardw1.se.axis.com> (raw)
In-Reply-To: <1427798995.588863.247475933.12C0B9B0@webmail.messagingengine.com>


Sorry, I just can't keep silent on this... though I fear this will go 
nowhere ... :-(

On Tue, 31 Mar 2015, Nikita N. wrote:

> [ ... ] software is verified can damage the speakers, if not used 
> somehow correctly.
> ...
> We were hoping in some form of amend from yourself, about the dangerous
> software you produced and distributed to public.
> ...
> We were hoping at least in a simple warning popping up from your tool,
> when user sets any "hazardous" levels.

There is nothing wrong with the software. As MAarten points out, it does 
the same as any other mixer software. There is a problem with the 
hardware. It is akin to turning up the volume control on your stereo 
system and burning out the speakers in your room. If that happens, you 
have a hardware combination that is incorrectly a designed (i.e. your 
amplifier is too powerful for your speakers), it's not your hand with 
which you turned up the volume that is is 'dangerous'.

I appreciate that users might be upset when that happens, and rightly so, 
however, they should be upset with the hardware design, i.e. in this case 
the PC manufacturer.

In essence, a PC that behaves this way is broken, and if it starts 
emitting smoke when this happens it might even be dangerous and should be 
returned to the manufacturer for replacement. Period.

The same thing would apply if the power supply catches fire while playing 
a CPU- and graphic intensive game, because the large amount of power 
needed. Faulty hardware. Replace it, or buy a reputable brand next time.

That said, with some proper input we might be able to minimize the problem 
in software, given the proper help about which levels are considered 
"dangerous". That is something that must be determined for each specific 
hardware, there is no "dangerous" level from a software point of view.

> We were hoping at least-least in a warning popping up from your tool at
> runtime, something like "Warning: improper settings for this level, this
> level and this might result in damages to your audio devices".

There is no such level that the software can know about. Setting the 
output levels to maximum is not necessarily bad, wrong or dangerous. It 
depends on the hardware, and very likely hardware which the software can 
not know about (such as the exact type of speakers).

/Ricard
-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  parent reply	other threads:[~2015-03-31 11:44 UTC|newest]

Thread overview: 92+ 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             ` 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                   ` Ricard Wanderlof [this message]
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 --
2020-11-04 16:10 BUG Alex Marginean
2020-11-04 17:02 ` BUG Randall S. Becker
2020-11-04 17:54 ` BUG Randall S. Becker
2020-06-26 21:11 bug Luke Knoble
2019-09-02  3:52 bug liebrecht
2016-11-02 15:04 Bug H-P.Teufel
2016-09-13 17:18 Bug Mike Hawes
2016-09-13 17:26 ` Bug Santiago Torres
2016-09-14 22:14 ` Bug Dennis Kaarsemaker
2016-08-19 20:44 Bug Leonard Bocock
2016-08-23 10:41 ` Bug Luiz Augusto von Dentz
2016-08-24  8:15   ` Bug Leonard Bocock
2013-11-29 11:28 Bug Otártics András
2013-11-29 11:56 ` Bug Gleb Natapov
2013-10-18 18:53 bug squadrato
2013-08-29  2:34 bug lilofile
2013-08-29  2:43 ` bug Liu Bo
2013-08-29 12:25 ` bug David Sterba
     [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
2013-06-11 15:11 BUG Mark Murawski
2013-06-12  8:38 ` BUG Duncan
2011-12-19 18:02 Bug Володимир Остап
2011-09-10 13:13 Bug Guido Telscher
2009-11-30 20:39 BUG Plamen Vasilev
2009-07-24 20:28 Bug Steven Pratt
2009-07-24 20:29 ` Bug Chris Mason
2008-08-16  8:36 Bug Artjom
     [not found] <E1JF7vM-0000k1-Mc@linuxtogo.org>
2008-01-17 11:18 ` [oe-commits] org.oe.dev apm: turn off wifi cards before suspend so they are fully reloaded upon resume. closes 3664 Paul Sokolovsky
2008-01-17 11:57   ` Bug ohviey1
2006-01-12 15:23 bug Philippe Delodder
2006-01-14  1:01 ` bug Adrian Bunk
2005-05-19  6:24 bug Victor G. Marimon
2005-05-19  6:24 ` bug Jean Delvare
2005-05-19  6:24 ` bug Jean Delvare
2005-05-19  6:24 ` bug Victor G. Marimon
2005-05-19  6:24 ` bug Jean Delvare
2005-05-19  6:24 ` bug Victor G. Marimon
2005-03-23 10:41 bug Jan Boros
2005-03-23 10:54 ` bug Kay Sievers
2004-01-10 19:54 Bug Tyler Harmor
2004-01-10 21:07 ` Bug Ryan Underwood
2002-03-19 21:20 bug Виталий
2001-09-07 18:42 BUG Attila A Odry
2001-01-31 22:50 BUG Grzegorz Sojka
2001-01-31 23:18 ` BUG James Sutherland
2001-02-01 11:04   ` BUG Maciej W. Rozycki
2001-02-01 11:49 ` BUG Zdenek Kabelac
1998-09-04 18:51 Bug Ulf Carlsson
1998-09-04 21:25 ` Bug ralf
1998-04-03 22:11 fwd: Andreessen Sees Mozilla-Linux Upset Of Windows ralf
1998-04-04 16:30 ` bug Ulf Carlsson
1998-04-04 15:59   ` bug ralf

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=alpine.DEB.2.02.1503311334370.13892@lnxricardw1.se.axis.com \
    --to=ricard.wanderlof@axis.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=maarten@resorama.com \
    --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.