[alsa-devel] Speaker burnout

[Torsten Schenk]

Hi everyone,

I also followed the discussion.
First of all I have to agree to Maarten that I dont' like your,
Nikita's, tone here on the list. First of all, why are you complaining?
As you can see, many people now are trying to figure out what to do to
fix this. But instead you keep blaming, accusing and offending
Maarten. He is right that a mixer application just allows controlling
those parameters the hardware tells to be manipulatable. So the tool
CANNOT be held responsible. Popping up warnings will be annoying for all
the users that NEED to set the volume to a high level and would be
overkill if just very few devices are to be addressed.

Regarding the technical side of this: Since it interested me if this
happened to other people, I found this post:

http://marcin.juszkiewicz.com.pl/2012/12/10/how-to-fry-speakers-in-your-chromebook/

and the previous post on this site.
So it seems that on a Samsung Chromebook you can definitively burn your
speakers. One comment inside these post I found noticeable:

> I’m guessing that a path was set up from MIC1 (wired to DMIC in) to
> the left speaker output. Playing the digital mic input as analog at
> full volume seems like something that might cause speaker failure, and
> wouldn’t necessarily be audible while it is happening.

So this would indicate that not the volume level causes the damage but
a bad audio routing.

Regards,
Torsten