Can *YOU* blow a PC speaker using only a Linux kernel driver?
nakedsecurity.sophos.com
nakedsecurity.sophos.com
I tried that because I was curious, since everything is a file, then surely cpu processing things to become a sound right ? :)
(if you try this please make sure to get that into a pcm/wav file, and reduce the amplitude of that file _first_)
https://www.extremetech.com/computing/240309-apples-bootcamp... https://forums.macrumors.com/threads/15-2016-mbp-speaker-cra... https://www.reddit.com/r/apple/comments/5e1g37/warning_bootc...
When using the speaker, for some purposes you want absolutely max volume - that involves getting the physical parts of the speaker moving fast and far. Yet move them slightly too fast or too far or do that too often and it'll physically break. Odd effects like resonance mean two very similar looking signals can have widely different physical effects.
The ideal threshold might depend on numerous factors, like temperature and pressure, the age of the speaker, etc. Easy to do in software, impossible in hardware.
So why not just have more margin and make the line between 'loud enough' and 'breaking apart' wider? Well to do that your speaker would need to be physically larger, and space is very much in a premium in many devices.
(Of course, you could feed always feed such an absurd amount of power that it would break even the protective circuits, but that ultimate vulnerability is just inherent in the nature of electronics).
On the other hand, very high-power, short-lived 'transients' are necessary to give proper clarity and realism to the music. Most amplifiers, even very-high power ones usully idle along at about one or two watts or less, but the extra couple of hundred watts available allow lots of 'head-room' for those high-power transients so that they don't get clipped and distorted.
A high-power amp doesn't necessarily sound very much 'louder', but it sounds very much 'cleaner'.
It's speakers inside a phone or something that are very size-performance limited and are vulnerable to this. Those same devices tend to have advanced processing of audio headed to the speakers to make it sound better and not blow up the speaker.
An old Motorola I had had over 15,000 knobs to tweak in the audio section of the service app...
https://news.ycombinator.com/item?id=7205875
I agree with them that when using the official API for whatever-X, you can't be blamed when X fails. Whatever X is, it should be built to cover all uses of its official interface.
In the case of VLC, that X is the Dell sound hardware, which can't handle certain uses because of a power incompatibility between the Dell sound card and the Dell speakers.
Reminds me of a case long ago where a GUI program took blame because it sometimes caused the X11 server to crash. That was clearly a bug on the X11 server side, too. A server should be built such that it's impossible for a client to crash it.
I have ~2kW of RMS amplification available to my floorstanding loudspeakers and subwoofer. There is a lot of DSP/EQ protection in between my HTPC and the mechanical drivers in the speakers.
Despite all of this, I have had incidents where the software glitches out and plays the un-decoded DTS/DD stream. If you have your volume set at or near reference when something like this happens, it can cause physical damage (to both your speakers and your ears).
(Audio) Engineering is all about balancing many complex factors. Mistakes happen and you can't address all of the edge cases without ruining the overall user experience. To say its the fault of the speaker is a little bit accusatory in my opinion. Can you ruin your car by taking certain actions? Certainly. Is this the car's fault? No.
Not sure X11 itself was to blame for most crashes. GPU drivers tended to be hit or miss in the past and if I remember correctly even Microsoft had enough of that mess at some point and started to isolate them from its otherwise monolithic kernel, just so it could at least recover the session instead of blue screening.
Then I wrote a small asm that moved the FDD heads way past the last track and it stoped working (couldn't move the head back to regular position anymore). And, despite all arguments, I kept my opinion.
Then Stuxnet came and now this discussion is over.
https://hardware.slashdot.org/story/14/02/09/1828229/custome...
Also https://news.ycombinator.com/item?id=7205759
In short, Dell sold laptops a few years ago where the included speakers weren't specc-ed out right.
So, Dell was blaming VLC and other applications for destroying the speakers, when it was just Dell's bad choice of shitty components.
In other words, whether the current going through the speaker is sufficient to either overheat the voice-coil, or to drive the speaker-cone beyond its physical limits.
These are qualities pertaining to the speaker itself, not the PC's output. The easy answer to the question is "It depends".
At least if wearing it out in the fastest manner possible counts as "blowing" it, that could work...
Easily one of the more unpleasant experiences of my life (and I’ve broken bones). Something about the sound triggered a very specific Synesthesia. I smelled a burning smell for half a day.
So… in addition to blowing speakers, you can also blow minds.
Run it at that frequency for too long and the pizeoelectric coating delaminates from the metal disc of the speaker, leading to failure.
So, yes, you can probably blow them from software if you're willing to have it turned on for a few days continuously.