The list of hardware problems with Apple products is miles long. Something has affected every single product they've ever sold since 1976. I don't know where people are getting these rose colored glasses from.
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.
Apple Updates Boot Camp Drivers to Fix Major Issue Causing Blown Speakers on New MacBook Pros [Updated]
- Thread starter MacRumors
- Start date
- Sort by reaction score
The list of hardware problems with Apple products is miles long. Something has affected every single product they've ever sold since 1976. I don't know where people are getting these rose colored glasses from.
Disagree. Its a system integration - driver issue as reported. For good response you need an amplifier with high peak power relative to the capacity of the speakers. It is preferable in a digital device to engineer the drivers rather than bulky analog pass/no pass filters.
Its like no one on this forum has ever seen a "bug" in a new product. They made a mistake. They are making good. Walk into any Apple store. Deal directly with a human. Pick up the warrantied product when repaired. That's a rare thing these days.
Do you know for a fact that the driver wasn't WHQL certified?
If it was certified by Microsoft's own Windows Hardware Quality Labs (and all the Boot Camp drivers on my Late 2015 iMac are WHQL certified), then yes, it sure as hell is, at least in some part, also on Microsoft.
Just connect a cable from your headphone jack to the aux input of your stereo, problem solved.
I don't understand what you're trying to say. Non of what you ask matters. If Apple sold 10 new Macbook Pros and 2 have had this happen, then that's the problem. Doesn't matter if the people using Windows on their Mac were doing it for work or not. When the speakers blow, they won't work correctly in either operating system. Nowhere do I see in the original story that this problem happens because the user had their speakers set to a high volume.
Me personally, I'm a recording engineer. I use Mac Pros for work. Occasionally, I will use my 2012 Macbook Pro for work but it's mostly my personal computer. I do also boot into Windows for a few programs I use that are not available on OSX. I'm not a gamer but I'm sure there are people that use Windows to run games.
Or simply: to run a hypervisor inside Windows, which you might need if you are, for example, a Visual Studio + Android developer.
[doublepost=1480630615][/doublepost]
How so.
WHQL is about compatibility with Windows, i.e. not crashing the OS.
If the actual hardware acts funny it's beyond WHQL.
I say "actual hardware" because usually the amplifier is dimensioned in such a way that it's exceedingly difficult to blow out a speaker via software.
Yeah, that would probably be the best route to take for people who really need to use Windows. Either that or wait until next year for Apple to come to their senses by lowering the price by $200-300 and fix any more teething problems.
You don't need your jack #COURAGE
You don't need your speakers #COURAGE
You don't need USB3 #COURAGE
You don't need an iMac #COURAGE
You don't need a Mac Mini #COURAGE
You don't need a Mac Pro #COURAGE
You don't need Mac anymore soon. #WEMISSYOUSTEVEJOBS
Sorry, I am just kinda tired of waiting for my new iMac. And have no interest in a pile of courage.
You don't need your speakers #COURAGE
You don't need USB3 #COURAGE
You don't need an iMac #COURAGE
You don't need a Mac Mini #COURAGE
You don't need a Mac Pro #COURAGE
You don't need Mac anymore soon. #WEMISSYOUSTEVEJOBS
Sorry, I am just kinda tired of waiting for my new iMac. And have no interest in a pile of courage.
Doesn't matter. Apple should have tested this before release.
Absolutely, resoundingly: no.
You can play back the spikes yourself from Mac OS if you like.
The point is, the amplifier stage should be dimensioned so as not to physically blow out the speaker with any signal received.
That's how humanity has done it for the past 90 years, at least.
This is exactly why never buy the 1st generation model of a redesign...
At some point people are just going to get tired of working there and leave, which'll be a good thing for the rest of the valley.
Who is making these non-decisions, the design group? Are people just so fed up with them that they're letting the design team hang themselves?
Who is making these non-decisions, the design group? Are people just so fed up with them that they're letting the design team hang themselves?
Because drivers are software that drive hardware, and in this case (regardless of whatever may be usual), a driver has been causing hardware to act funny (where by "act funny" we mean, in this case, "physically break").
That's why Apple have addressed the problem by updating the driver.
Microsoft say their WHQL program certifies drivers specifically to help create high-quality, end-to-end hardware experiences.
If a WHQL-certified driver broke hardware, then yes, Apple must bear the lion's share of the responsibility for shipping the hardware with that driver (and they are doing so, replacing affected MacBook Pros at their own cost). But if Microsoft gave the driver their seal of approval, then they are surely not entirely blameless.
Outsourced directly to end users.
Pros:
-saving money (don't have to pay for their tests, the pay for testing)
-real life scenarios instead of artificial environments in labs
-larger number of units tested
-plenty of time to fix things rushed out badly
-shiny marketing image (they even fix issues limited to a small number of customers and release them for all the great Apple family members)
My question is, how hard is it to have a small over-current protection circuit in the output stage of the amp? Is it really that big, difficult or power hungry? Doesn't Apple have this sort of thing in other parts of the computer and power supply anyway?
I'm on the side of thinking this shouldn't have been possible. It should not be possible to damage the hardware at maximum output volume unless there's a design flaw in the voltage regulation. I never heard of this happening with the 2012-2015 rMBPs or any other Mac for that matter.
I'm on the side of thinking this shouldn't have been possible. It should not be possible to damage the hardware at maximum output volume unless there's a design flaw in the voltage regulation. I never heard of this happening with the 2012-2015 rMBPs or any other Mac for that matter.
Last edited:
Apple's Logic program running on Mac Pros used to produce random blasts of white noise; really bad as it could blow some very expensive studio monitors and headphones not to mention permanent hearing loss. I think Apple may have fixed it in later versions but not sure.
No this is what you get when Apple messes up. Say it. It won't hurt that bad. I promise.
[doublepost=1480642547][/doublepost]
You paid a lot of money for an Apple product that has an issue. Remember, Apple allows the use of Windows.
[doublepost=1480642985][/doublepost]
So that makes it ok.
Did you read the question I was answering? The guy said we'd be safe by using the drivers that come from Windows Update. This shows an extreme example of how he was wrong - though of course it is not the only case.
Intentional says... who? You? Because as far as Microsoft is concerned it doesn't sound like. Maybe you didn't read the ending of the article, in which Microsoft said:
Yesterday FTDI removed two driver versions from Windows Update. Our engineering team is engaging with FTDI to prevent these problems with their future driver updates via Windows Update.
Doesn't sound intentional to me!
You are welcome to welcome whatever you want to welcome. That doesn't meant that arbitrarily bricking customer's hardware is OK, even more if you stop to look at the problems of counterfeits in the electronics industry.