Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Apple probably should've issued "we are investigating the issue" earlier, but I am very pleasantly surprised by the update.

Like within the first 30 minutes of the video hitting YouTube? LOL, zero patience. I'd like to see a PC company find and fix one of their many bugs 2-3 days after some YouTuber complains about it. This is about as good as service gets in this industry.
 
Seriously? They had to do zero testing not to catch that.

Very hard to believe Apple could not detect it given the workflow that exposes it (very normal video exporting). Its good its fixed supposedly, but Apple does not look good here. If they actually performed "extensive testing" and failed to use Adobe Premier Export... thats not a good look.

Well we know Apple's teams are working with users of software optimized for Macs, which Adobe Premiere certainly is not. So those users they are working with may not use Premiere or use it as hard as the folks experiencing the issue the most severe do.

That being said, I believe folks reported throttling with Final Cut Pro, so...
 
I tried telling people this was a software issue 50 pages before that thread blew up.

Doesn’t pay to overreact.
 
I’ll await revised benchmarks and tests before praising the heavens. I refuse to believe thermal throttling can be significantly resolved through software - it’s basic physics! I hope they’ve sorted it but I’ll be surprised.
 
I’m sure Apple certainly new, like many of us, that it could be fixed in software, but I agree with others that they perhaps should have commented on it earlier. Purely because it might have reduced the fact that a lot of reviews of this significant upgraded MacBook were tainted by the throttling situation. But to be honest it doesn’t really matter, they fixed the issue quicker than expected which was a good move. Now people can complain about the real main issue, the pricing.
 
i9 only or 6 core i7 as well?
Please read carefully next time.

Cut from the original post:
Apple says the bug affected performance on not only the high-end 15-inch MacBook Pro configured with a six-core Intel Core i9 processor, which has faced the most extreme throttling in tests, but also quad-core Core i7 and Core i5 configurations, extending to the latest 13-inch MacBook Pro with Touch Bar models.
 
I definitely don't buy that this is an isolated bug, given the amount of users who experienced it. The official fix is probably the same one discovered by @winterny, which is to limit the power draw.
I was going to say “someone should check register 0x610 to see if the value was changed with the update.” because of @winterny ’s thread.
 
  • Like
Reactions: Stux
is everyone done bitching now? The smart people said it was a firmware or bug fix, which it was, but bangwagoners wanna jump on apple for everything :/

Nope, already subtle bitchin' or side-complaints baked into the praise.

Of course not. "No fix can solve Jony Ive obsession with thinness" posts incoming.

Anyway, it's good Apple is listening to what people have to say. Constructive criticism is good. And the new MBPs seem even better now.

Are you guys not paying attention or just view Apple with such rose-tinted glasses that you cannot see what just happened??
--->>> Bitching was heard by Apple and achieved results --->>> everyones new macbook just go improved.

If the complainers had listened to ye and stopped bitching this would not have happened.
 
I'm in the east coast, has anyone gotten the update? I have the i7 2.6
I'm seeing it available in California. I have the 13" 2.3 i5.

Screen Shot 2018-07-24 at 10.19.31 AM.png
 
  • Like
Reactions: BigMcGuire
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.