You sound like someone who's never seriously cut in Premiere. If you had, you would know it has lots of issues. Premiere's audio caused my whole system to crash, forcing me to rebuild everything.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Adobe Issues Premiere Pro Fix for Bug That Caused Blown-Out MacBook Pro Speakers
- Thread starter MacRumors
- Start date
- Sort by reaction score
You sound like someone who's never seriously cut in Premiere. If you had, you would know it has lots of issues. Premiere's audio caused my whole system to crash, forcing me to rebuild everything.
Regardless of who is at fault here, this is supposed to be good industrial design? Lay the blame for the cost at Johnny Ive's doorstep. That $600 cost is Apple telling you to buy a new machine because their products aren't designed to be repaired.
Are you saying Apple should charge everybody who had this issue a $600 repair fee since it wouldn't be covered by warranty since it isn't considered "normal use" to use Adobe's Creative Cloud suite in your opinion?
Adobe made this piece of software, therefore the responsibility to fix this bug is on them...which they did. There was no Engineering error because the Speakers did what they were told to. Software controls Hardware. There are hundreds of apps in the wild that can do things like blow speakers, turn fans on and off, etc. (VoodooHDA for example is a program I been using for years and has been known to easily blow out speakers on any Mac/Hackintosh when not used properly). It is also not limited to macOS either.
This is one of the caveats of having an 'open' OS. I don't think you guys want macOS to be handled in the same way as iOS
Last edited:
The simple answer is they won't be, after all part of the EULA on the software clearly states that Adobe is not responsible for any damage that may occur to your system as the result of using their software, which leaves Adobe off the hook and Apple can simply say it was Adobe's fault.
Does anyone remember when the 2016 MBPs launched and just installing Windows through Boot Camp permanently blew your speakers? Ahh, good times.
I don’t think you understand. You are talking about open source drivers which change the behaviour of hardware - that is not the same thing. If I installed some fan control software and disabled the fan, then of course I will happily expect heat issues.
The problem lies in Apple allowing software to be allowed to get the speaker to do something which would break it, which it should have no business to do. Adobe products are not hijacking Apple hardware drivers.
If a game bug resulted in the MacBook frying itself, that is on Apple’s head imo.
I should note, this wasn’t the only thing breaking Apple’s speakers, many people reported blown out speakers so clearly something is wrong on the hardware or driver level.
I have to agree with this. It may have been an Adobe bug, but clearly Apple is responsible for allowing such bugs to be damaging to the hardware. I agree that both companies are responsible and should each equally chock up the $$ to cover hardware repairs.
[doublepost=1550860385][/doublepost]
Yup, I agree with this, too. I feel Apple should definitely cover part of the cost in replacing the speakers due to their engineering decisions. Owners should not have to pay for Apple's decisions.
Will probably need another ' class action lawsuit ' for the resolution.
However, till that time, the funds Apple will need disperse towards re-reimbursing or fixing the speakers will have already multiplied X times, so ultimately the cost to Apple will even more negligible.
"Apple has to replace the entire top case assembly containing the speakers, keyboard, trackpad, and battery."
More POS engineering from Apple. As if the defect allowing the speakers to blow out weren't bad enough; once again we have Jony Ive's degraded and degrading design costing customers money.
[doublepost=1550865245][/doublepost]
No, they're NOT working correctly. Apple controls 100% of the audio pipeline in this computer, and their circuitry delivered excessive voltage to the speakers. Nobody else can do that EXCEPT Apple, so it is absolutely their fault. Think it through.
More POS engineering from Apple. As if the defect allowing the speakers to blow out weren't bad enough; once again we have Jony Ive's degraded and degrading design costing customers money.
[doublepost=1550865245][/doublepost]
No, they're NOT working correctly. Apple controls 100% of the audio pipeline in this computer, and their circuitry delivered excessive voltage to the speakers. Nobody else can do that EXCEPT Apple, so it is absolutely their fault. Think it through.
No, that is not how it works. The software does not control the hardware, the operating system does. The software can only do what the operating system allows it to do, using the functionality provided to it by the operating system. Something like blowing out the speakers should be something the operating system explicitly prevents.
I'm not going to get into advanced possibilities, but with legitimate software (which doesn't make use of kernel extensions/modules), this is how it works. If you disagree, then please explain to me what a kernel header is first. Seems like a decent litmus test.
Last edited:
Haha, I am with you, although I do write macOS, I think it should be Mac OS too, the way it has been before.
What if you start a sentence with it, can't be macOS can it!
About the issue
Adobe should be banned, it's a virus like App, places files all over the place, why can't they have all the support files in the .App folder as others do, nono, crap everywhere.
And phoning home is another one.
TIL there's still people who have Flash on their machines?
So, you are saying your post had nothing to do with the thread topic? How was anyone to know that your posts are random, and not related to the thread?
better not allow apples own software either then - before adobe, apple blew up speakers by their own audio drivers for bootcamp and then they hurry to fix the drivers before it hit headlines. and it happened already in 2016 so apple has known a long time that there is a serious problem in macos allowing hardware to blow up... and now two years later - nothing has fixed apparently!
An app should never be able to physically damage hardware. 100% Apple's fault. There should be a hardware control that regulates at a safe level the amount of signal sent through the speaker.
I had an audio driver from Metric Halo that contained a bug that would cause a full volume audio output to my speakers when triggered. Fortunately it didn’t blow the speakers in my studio. But easily could have if I hadn’t almost immediately pressed stop.
I’d hardly expect hardware to have a built in “don’t play loud music” setting permanently engaged.
I’d hardly expect hardware to have a built in “don’t play loud music” setting permanently engaged.
Actually it should if it cant handle playing loud music without frying itself. I don’t know what kind of products you have, but I’ve never in my life suffered from a speaker blow out due to playing loud music. At the end, the hardware controls max volume output, if you have a speaker which you are limiting sound to not fry the speakers but allow a software bug to somehow pass this limit, that is a hardware design flaw.
What Adobe has actually done is fix Apple’s bug, their design flaw means they had to rework part of their code.
I write code and I can’t even imagine how I could be responsible for a hardware failure
There is no ****ing way userland software should be able to blow out your speakers in an integrated system. If you'd added your own DAC or amplifier then I could understand it, but that's not the case. This is an error in Apple's integration of the speakers.
Aren't these the same speakers that blew out when you installed an audio driver on Windows all the way back in 2016?
These speakers appear to be another piece of garbage in a generally piece of garbage laptop.
Bring on that revised 2019 MBP please. Time to get rid of this piece of junk. Hope Apple learned their lessons from repaining all those topcases when they fused a terrible keyboard and speaker into the topcase.
Aren't these the same speakers that blew out when you installed an audio driver on Windows all the way back in 2016?
These speakers appear to be another piece of garbage in a generally piece of garbage laptop.
Bring on that revised 2019 MBP please. Time to get rid of this piece of junk. Hope Apple learned their lessons from repaining all those topcases when they fused a terrible keyboard and speaker into the topcase.
Last edited:
I could understand the microphone would somehow be linked audio issue
Choice? What the industry users is different than what Apple customers use..
Choice? What the industry users is different than what Apple customers use..
I want to add, no software should have the ability to override the volume of any device. I am not a software or hardware engineer so I would not know who would be at fault. As for who is going to pay for the repair of the blown speaker, I would say it would have to be Apple.
In the old Amiga days there was a bug that would move the Floppy to Track "-1" and unable to recover.
That was in the 80s, and I cannot recall the details.