-
The new Mac Book pro
-
We just have to accept that we now live in a Ready – Fire – Aim universe.
What matters most is being first. First to uncover the flaw. First to stake out the ground for your position.
The reward is clicks and clicks need to be accumulated when the VERY first eyeballs show up – because only then can you TREND. And TREND is everything.
Time to contemplate and try to understand the actual nature of the issue and whether or not the issue is going to be meaningful over any substantial period of time? That’s for losers! The book reader is just too damn slow! We need the gamer who can sally forth into Fortnight and slay HORDS by fast twitch precision in the opening seconds of the salvo.
Join the chorus NOW or risk being irrelevant to the meleé.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
[Bill Davis] “We just have to accept that we now live in a Ready – Fire – Aim universe.”
And that’s a good thing. When we’re talking about products as expensive as the Apple line the buying public has a right to know about flaws or defects.
It sounds like Apple is dealing with the throttling issue quickly so perhaps the transparency of review info has aided in getting Apple to come up with a fix strategy.
Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync -
[Bill Davis] “We just have to accept that we now live in a Ready – Fire – Aim universe.”
Oh geez! Look at the facts! The primary problem with these machines was the “thermal throttling” issue. When you potentially drop $7K on a machine, you’d like to have it work correctly. Every product reviewer worth their salt will push performance hardware to the max. The fact that it’s now on the net, instead of TV or print simply means both good and bad news gets out there faster.
This thermal issue was relatively easy to reproduce and was found by a vlogger, who then worked with Apple to find a solution. The fact that multiple users could reproduce the issue makes it surprising that it was missed by engineering QA before release in the first place.
As someone who suffers at times daily through render issues on a 2013 Mac Pro, I can tell you first hand that Apple doesn’t have a great track record when it comes to thermal design. Considering that Apple very quickly found it was a design mistake that was fixable through a software update in short order, points to the fact that this was a very real problem. And they also acknowledged that all 2018 13″ and 15″ MBPs were affected, even though the problem primarily cropped up in the i9 machines.
The data port issue that Louis brings up is a separate matter and probably not easily rectified.
– Oliver
Oliver Peters – oliverpeters.com
-
[Bill Davis] “What matters most is being first. First to uncover the flaw. First to stake out the ground for your position.”
First? This isn’t a cable news story where reporters and anchors RUSH to get the news story on the air and get facts wrong…or report issues that are in flux and constantly changing. No…I guy found a flaw in the processor, it was being throttled. Several others found the same issue…Apple acknowledged the issue, and a fix was released. There’s no “fake news” here…no wrong facts due to reporting this issue quickly. An issue was found, but someone who pushes hardware to the limits every day, it was acknowledged…and fixed. True nature of why all this was happening came to light, and it wasn’t wrong. The design of the MBP isn’t optimal for the cooling needs of the processor. The push for THIN and SLEEK isn’t ideal for high end needs…needs even FCPX would have.
So I fail to see what your point is. Are you somehow not liking that a flaw in an Apple product was brought to light by at least three bloggers/vloggers? That Apple admitted wrong doing…and a fix was issued?
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Bill Davis] “We just have to accept that we now live in a Ready – Fire – Aim universe.”
???
A reviewer found a flaw in a product, shared the flaw with the public, product’s maker acknowledged the problem, and released an update to address it.
The reviewer didn’t get it wrong, he just happened to get it right so fast that many people assumed he had to have gotten it wrong. The knee-jerk reaction to the reviewer is where Ready – Fire – Aim took place.
-
I mean…back at the start of the digital filming revolution, I was working with P2 footage and encountered an import issue…and blogged about it. Apple then contacted me directly and offered to work with me to find the solution, which I did the following day. Two days later an update to FCP was released. Not meaning to toot my own horn here, but it is another example of this “squeaky wheel gets the grease.” In this case it wasn’t a design flaw, or intentional slowdown…but an actual small bug when it came to dealing with footage shot with a specific setting.
Shane
Little Frog Post
Read my blog, Little Frog in High Def -
[Rich Rubasch] “….now if only Adobe’s software would.”
Are you a member on the “Moving to Premiere Pro Forum” on facebook? I ask because there’s Adobe employees that sometimes respond to queries there.
Windows 10 Pro | i7-5820k CPU | 64 gigs RAM | NvidiaGeForceGTX970 | Blackmagic Decklink 4k Mini Monitor |
Adobe CC 2018 |Renders/cache: Samsung SSD 950 Pro x2 in Raid 0 | Media: Samsung SSD 960 PRO PCIe NVMe M.2 2280 | Media: OWC Thunderbay 4 x 2 Raid 0 mirrored with FreeFileSync -
[greg janza] “When we’re talking about products as expensive as the Apple line the buying public has a right to know about flaws or defects.”
Expensive?
Please.
$2600 (in 1990s dollars!) was the Betacam TAPE budget for a medium sized corporate shoot when I was learning the craft.
That you can spend the same amount in 2018 dollars and get a high powered computer in a 1″ slab of aluminum — iincluding a killer monitor and SSD storage — that can handle 4k footage with aplomb — is damn near MIRACULOUS.
We’re just stupidly spoiled in this era.
Todays default for far too many people is that it’s NEVER good enough, fast enough, cheap enough, or works well enough.And if it is — then that’s it’s even worse – because then EVERYBODY can buy it and push all the rates down.
THIS is a digital video GOLDEN AGE in nearly EVERY historical aspect – and yet all we can do is bitch, bitch, bitch that it’s still not golden or shiny ENOUGH.
It’s kinda embarrassing, really.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
[Oliver Peters] “doesn’t have a great track record when it comes to thermal design.”
Yeah, but from what I read, THAT was not the problem here.
After the patch that simply changes some embedded power unit code — the DESIGN of the unit appears to work precisely as it should.
So the problem wasn’t “thermal DESIGN” (as most people would understand that concept) at all. It was a small bug that temporarily prevented the computers to operate to spec – but one that was pretty easy to correct.
If it had been an ACTUAL design problem – the fix would have been to change the design.
But that’s not what happened here. They pushed a pure software fix – and the exact same hardware design works exactly as promised.
That’s a very different thing.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery. -
[Shane Ross] “No…I guy found a flaw in the processor, it was being throttled.”
NO. That is NOT why throttling was occurring, as I understand it from my reading.
There wasn’t a “flaw in the processor” at all. It was an unsigned snippet of code in a Power Management Unit totally separate from the processor.
As I understand it, the computer was NEVER overheating and running the fans to cool down an actually overheating issue. The fans and throttle state were being triggered due to a glitch in the self assessment feedback.NOT because dangerous overheating was ever actually occurring.
It’s like your care engine Overheat light is coming on. So you take it in, but it turns out the LIGHT was shorting. NOT that the car was actually overheating.
They change the light bulb – or fix the computer – and it stops signaling that there’s a problem where their actually isn’t. Because the flashing light is not the actual issue – engine danger is. And there wasn’t ever any actual engine danger in this case – at least as far as I can tell.
Your i9 is NOT going to overheat and fail prematurely (at least not anymore than ANY other similarly configured computer with the same components from ANY manufacturer might) because APPLE screwed up their design.
From what I’ve read, the slim new Apple MacBook Pro runs within EXACTLY the same thermal parameters that also arise from thicker and even RUGGED laptops from many other manufacturers sporting the same level of performance. It get no hotter, cools no less efficiently, and should fail and NOT fail at exactly the same rate as any of it’s competitors.
The observed throttling was a temporary symptom of a tiny code glitch – NOT bad computer thermal design.
That’s the nothing burger this particular “gate” turned out to be.
At least as I read things.
Creator of XinTwo – https://www.xintwo.com
The shortest path to FCP X mastery.
Reply to this Discussion! Login or Sign Up