From: Clemens Ladisch <clemens@ladisch.de>
To: David Henningsson <david.henningsson@canonical.com>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, "Nikita N." <nikitan@operamail.com>,
Eliot Blennerhassett <eliot@blennerhassett.gen.nz>
Subject: Re: Speaker burnout
Date: Tue, 07 Apr 2015 09:26:02 +0200 [thread overview]
Message-ID: <5523868A.3020502@ladisch.de> (raw)
In-Reply-To: <5523828C.8060301@canonical.com>
David Henningsson wrote:
> On 2015-04-07 07:30, Eliot Blennerhassett wrote:
>> The signal when recorded is 1325Hz rail to rail square wave.
>> [...]
>
> If it is possible to burn your speakers out by having the speakers
> outputting some tone caused by feedback, would it not be possible to
> also burn your speakers out by simply having a wave file with the same
> tone and playing it back?
Of course. The problem is the speakers, not the feedback itself.
When connecting some random speaker to some random amp, it is quite
possible to burn it out:
<https://www.google.com/search?q=tweeter+burn-out>
However, this should not happen inside a closed system where amp and
speakers were designed for each other.
> Or is there something that causes the feedback tone to be of a larger
> amplitude than could ever be produced by the wave file?
In theory, it would be possible to do the mixing in the analog domain.
But there is no way to find out what the HDA codec actually does except
trying it out.
Regards,
Clemens
next prev parent reply other threads:[~2015-04-07 7:26 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 ` 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 [this message]
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=5523868A.3020502@ladisch.de \
--to=clemens@ladisch.de \
--cc=alsa-devel@alsa-project.org \
--cc=david.henningsson@canonical.com \
--cc=eliot@blennerhassett.gen.nz \
--cc=nikitan@operamail.com \
--cc=tiwai@suse.de \
/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.