Some Users Report Adobe Premiere Pro Issue Causing Blown Out MacBook Pro Speakers

[Ramchi]

Apparently, this issue affects MacBooks which have T2 chip (OMG - Suriji) in it and earlier Mac Books do not have this issue. I am not sure if this is the case.....this can potentially lead to dissatisfaction since replacing them with $600 service call will not solve the issue.

 

[LordVic]

This should be interesting. Who foots the bill? Apple? Adobe?

The way I see it:

if the speakers are designed right and operating within normal operating perameters, but Adobe has a bug that sends out of parameter signal. Adobe is responsible.


if the speakers have a design flaw that fries themselves on something that is considered in paameter. it's Apple's responsibility


but we all know how this will wind up. The consumer fits the bill.

 

[AndyMacAndMic]

The way I see it:

if the speakers are designed right and operating within normal operating perameters, but Adobe has a bug that sends out of parameter signal. Adobe is responsible.


if the speakers have a design flaw that fries themselves on something that is considered in paameter. it's Apple's responsibility


but we all know how this will wind up. The consumer fits the bill.

Apple provides the API (application programmers interface) to interface with the OS. There is also a 'sound API'. This API provides functions to play sound through the OS on the device.

Simplified: The sound api provides functions for volume, play, pause etc. If Adobe has a bug in it's program it could be that some sound signal is sent through the api on maximum volume. Apple should design the interface (api) and the hardware in such a way that no speakers can be blown out if the api is used. Even if the bug in Adobe software would try to send a much higher volume through the API then allowed, the API should not accept that signal if it is not within parameters.

If it is possible to damage hardware through the provided API's there is something wrong with the API's or the hardware. There is no way that software can break hardware under normal circumstances unless (as already said) there is something wrong with the interface (API) or the hardware.

So, in my humble opinion, you see it wrong

 

[LordVic]

Apple provides the API (application programmers interface) to interface with the OS. There is also a 'sound API'. This API provides functions to play sound through the OS on the device.

Simplified: The sound api provides functions for volume, play, pause etc. If Adobe has a bug in it's program it could be that some sound signal is sent through the api on maximum volume. Apple should design the interface (api) and the hardware in such a way that no speakers can be blown out if the api is used.

If it is possible to damage hardware through the provided API's there is something wrong with the API's or the hardware. There is no way that software can break hardware under normal circumstances unless (as already said) there is something wrong with the interface (API) or the hardware.

So, in my humble opinion, you see it wrong.

I will accept that as a possibility (knowing alreay about API's and the like.)

Still drinking my coffee this morning Afternoon.

So now we move on to the next question. what exactly is happening here. After reading more of the thread, many reports of identical issues from people who are NOT using adobe.

this definitely ties back to it being an Apple design issue if it's also reportedly happening outside of Adobe software.


The more I look back on my decision to purchase a different laptop this year, the more I feel relieved.

 

[mrex]

oh well.. nothing new. last time it was Boot Camp.

https://support.apple.com/en-us/HT207410

 

[ericwn]

This is a new low for Apple. Speakers that destroys themselves and then a 600$ quote for a repair. Bad design and bad customer support, simply put. I hope Apple changes.

A new low sounds a bit over the top in the face of FaceTime security issues that just happened. Also, when combining software a and hardware component b and that results in a hardware damage it seems weird to determine that the hardware self destructs. It’s the combination of the two that causes the issue. Still, bad enough. Software should not be capable of destroying hardware components.

 

[ericwn]

Why not go into Apple and declare that the speakers are blown, causes unknown? Will the Genius clowns know why?

Not sure why you need that tone towards Apple staff. I have had a lot of good experiences in Apple stores.

 

[wbrat]

Our tipster Shen took his MacBook Pro to the Genius Bar at an Apple Store in Canada and was provided with an over $600 repair quote for his 2018 15-inch MacBook Pro. The price is so high because Apple replaces the entire top case assembly containing the speakers, keyboard, trackpad, and battery.

This is ridiculous. When will they realize that things like that make people less likely to buy their stuff in the future?
Btw., I assume that after the replacement I receive all old components back??

 

[glendt]

It's not just Adobe Premiere Pro. I had the same issue occur with my 2018 Macbook Pro with Apple's own Garage band software, while trying out various audio effects. Fortunately the Apple Store employees confirmed that the speakers were blown and they repaired it free of charge because it was still under warranty. I am now hesitant to use to built in speakers whenever I'm using audio software.

 

[TRDGT4Writer]

Also use Final Cut Pro. It’s better anyway.

(Drinks more Apple Kool-Aid)

Or you use Media Composer and/or Davinci Resolve Studio ($300)