Activity › Forums › Creative Community Conversations › wwdc
-
Mitch Ives replied 9 years, 10 months ago 15 Members · 86 Replies
-
Andrew Kimery
June 16, 2016 at 6:49 am[David Mathis] “I wish Apple would do that. I would rather build a custom desktop then wait for another expensive trash can model.”
Why would Apple license out its OS to another hardware maker that would most likely undercut Apple on price? That doesn’t sound like it would sell more Apple hardware and selling Apple hardware is why keeps the lights on up in Cupertino.
-
Oliver Peters
June 16, 2016 at 11:58 amI don’t doubt that the Deadpool team heavily stressed those machines because of the large frame sizes they were pushing through. By comparison, the Hail, Caeser! editors had not problems. OTOH, Vashi went with a beefy PC set-up on the current film he’s cutting.
AMD implied to me that it was a heat issue due to poor airflow design for the top GPU chips. I have no idea, however, at NAB the custom enclosure folks (who stick a trash can into a box) place an additional fan in front of the intake of the trash can.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Walter Soyka
June 16, 2016 at 1:37 pm[Jeremy Garchow] “Sounds like the problem has been identified and fixed?”
Well… there are still apparently ongoing heat issues with D700 that cause glitchy Resolve renders:
https://forum.blackmagicdesign.com/viewtopic.php?f=3&t=47918We have had 3 service calls on our 4 nMPs of varying vintage.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Jeremy Garchow
June 16, 2016 at 3:18 pmI have no doubts that Apple hardware isn’t perfect. What hardware does not have a mtbf, especially ones that generate considerable heat?
In the examples cited, GPUs manufactured in a certain 2 month timeframe (nearly two years after the initial release) had problems that seem to be addressed by Apple.
And the glitchy Resolve renders were from a beta version of resolve, and a few things fixed it including upgrading to the latest OS and software?
I am certainly not absolving Apple of doing weird things. 10 blown out MacPros in a production would be enough to switch to a beefy PC, but the sky is not falling quite yet.
The more interesting part of the Deadpool articles is the reliance of third parties to fix workflow holes, something that Apple gets tremendous sh*t for, for whatever reason. Adobe gets celebrated for having, nay, needing third party workflow helpers.
-
Oliver Peters
June 16, 2016 at 3:28 pm[Jeremy Garchow] “The more interesting part of the Deadppol articles is the reliance of third parties to fix workflow holes,”
In an advanced post operation, you will always have third party products involved. NO ONE will ever place all of their eggs in one company’s basket. Not to mention user preferences.
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Walter Soyka
June 16, 2016 at 3:39 pm[Jeremy Garchow] “And the glitchy Resolve renders were from a beta version of resolve, and a few things fixed it including upgrading to the latest OS and software?”
That is but one thread of many, going back to January 2014. These render glitches have affected every single version of Resolve since the nMP launched, mostly with D700s, mostly under high load. Lots of those threads suggest that updating software, either OS or the app itself, has “fixed” the problem (and made Safari “snappier!”), yet the next week there will be another post with the same problem on the new version.
The fact that these glitches can be mitigated in some cases by running a third-party app that runs the fan at full tilt says something about the thermal engineering. Obviously that hasn’t stopped us from buying these computers when they’re the right tool for the job, but it seems Oliver is right to say they melt. Thinner/smaller/quieter is the enemy of cooler, and thus of performance.
[Jeremy Garchow] “The more interesting part of the Deadppol articles is the reliance of third parties to fix workflow holes, something that Apple gets tremendous sh*t for, for whatever reason. Adobe gets celebrated for having, nay, needing third party workflow helpers.”
Double standards are twice as good as single ones?
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn] -
Jeremy Garchow
June 16, 2016 at 3:50 pm[Oliver Peters] “In an advanced post operation, you will always have third party products involved. “
I don’t think your post operation needs to be that “advanced” in order to need third party products. Funny enough, a lot of the workflow holes centered around interchange.
-
Oliver Peters
June 16, 2016 at 4:03 pm[Jeremy Garchow] “Funny enough, a lot of the workflow holes centered around interchange”
They always do. But was there something in particular that jumped out at you?
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Jeremy Garchow
June 16, 2016 at 4:27 pm[Walter Soyka] “That is but one thread of many, going back to January 2014. These render glitches have affected every single version of Resolve since the nMP launched, mostly with D700s, mostly under high load. Lots of those threads suggest that updating software, either OS or the app itself, has “fixed” the problem (and made Safari “snappier!”), yet the next week there will be another post with the same problem on the new version.
“I have a Blackmagic box that crashes FCPX multiple times a day, but does not crash Resolve. Plugin an AJA box, and everything works very well in FCPX, but does not work in Resolve. It must be the Apple hardware causing all the issues?
Again, I am not denying Apple hardware is not perfect, clearly there are imperfections. Clearly, the new MacPro could look like the old MacPro. I’d be livid if 10 MacPros melted down during my giant VFX spectacular. I’d be even more livid if it melted down during one of my piddly ‘VFX’ shots that I render daily.
-
Walter Soyka
June 16, 2016 at 4:50 pm[Jeremy Garchow] “I have a Blackmagic box that crashes FCPX multiple times a day, but does not crash Resolve. Plugin an AJA box, and everything works very well in FCPX, but does not work in Resolve. It must be the Apple hardware causing all the issues?”
In your cases and in mine, I’d consistently blame the hardware/drivers. In your cases, BMD makes the hardware and writes the drivers. In mine, Apple does.
I’m not looking for a gotcha here. The nMP is still a pretty nice machine for its size. But isn’t it weird that the Resolve problem is so prevalent on nMP D700 configurations, and so rare with all others?
https://forums.creativecow.net/thread/335/88655 for more.
Walter Soyka
Designer & Mad Scientist at Keen Live [link]
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
@keenlive | RenderBreak [blog] | Profile [LinkedIn]
Reply to this Discussion! Login or Sign Up