Accidentally exposed Apple and Adobe, Thoughts?

[iPad Retina]

Hi Guys, So after having my speakers blown from Adobe's Premiere Pro, I tried to research into what could have caused it. But everyone I saw saw it as a software issue tillI came across the Adobe thread. After that I shared the tip to MacRumors and then it exploded from there. Do you think Apple will take responsibility or Adobe will?

 

[Ruskes]

Hi Guys, So after having my speakers blown from Adobe's Premiere Pro, I tried to research into what could have caused it. But everyone I saw saw it as a software issue tillI came across the Adobe thread. After that I shared the tip to MacRumors and then it exploded from there. Do you think Apple will take responsibility or Adobe will?

*****
what Adobe thread ?

 

[Shabs]

I think adobe will and where is that adobe thread share the link

 

[giffut]

Adobe may have triggered the error, but the underlying problem are the audio distortions the t2 processor is causing, besides many other severe misbehavings. It controls the audio engine and causes the severe sonic spikes which damage the speakers. Any reasonable designed audio ciruitry limits the maximum output to the speakers - the t2 apparently does not. It also crashes core audio a lot. This is the reason many audio interfaces, especially all usb ones no longer work reliable under mac os with current t2 based hardware.

 

[leman]

Software shouldn't be able to cause hardware malfunction, full stop. This one is on Apple, fully and unconditionally.

 

[Falhófnir]

I tend to agree this is more on Apple - If the CPUs were catching fire that would be Intel's fault for the firmware allowing it to happen (as they are the ones that provide it) not Apple's for their OS/ software pushing the chip to go beyond idle, right? Same logic applies here, Apple's firmware for the speakers shouldn't allow the software to push them to point they can damage themselves.