Corrupt renders nMP with D500s

[Andy Edwards]

Oliver,

It’s a know issue with the MP GPU’s… not only with the D700’s, but also the D500’s. Get Apple to replace graphics card A & B on your clients MP under their recall program.

FCPX will not show the same render glitches or lines. Watch the Activity monitor CPU menus peak out when Premiere or AME are exporting, then run the same test with FCPX. FCPX does not tax the CPU’s / GPU’s as bad and over heat the MP introducing the glitches. I’ve even had AME exporting, loaded up Compressor and exported at the same time. You’d think taxing the MP with both programs exporting it would fail on both. Compressor or FCPX don’t show the lines and glitches, but AME will. It’s not always consistent when you reboot to cool things down, but a lot of the times during my testing, Premiere & AME will fail on 4K exports where FCPX or Compressor will not.

Software only as you stated seems to be the only saving grace to get something exported out of Premiere or AME with a MP with these issues.

Andy Edwards

[Oliver Peters]

Thanks. That’s what I was afraid of.

Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Eric Santiago]

Have you tried older versions?

Ive had a slew of C500s and C300/100 clips in all NLEs the last year and no issues in CC2013.

I finally upgraded but data has been removed from my studio.

[Oliver Peters]

[Eric Santiago] “Have you tried older versions?”

No, this is a new machine. That’s all that’s installed.

– Oliver

Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com

[Eric Santiago]

[Oliver Peters] “No, this is a new machine. That’s all that’s installed.
“

Sucks yea I have a nMPs that Im not allowed to downgrade at day job.

I still use a 5, 1 just in case.

At home Im running both CC2015/2017.

[Andy Edwards]

[Eric Santiago] “Ive had a slew of C500s and C300/100 clips in all NLEs the last year and no issues in CC2013.”

Are you talking about Canon C500 / C300/100 media vs. the Mac Pro D500 GPU’s?

Andy

[Olivier Aubut]

Hey

The apple store wouldn’t take my nMP d700 because they couldn’t replicate the errors with their tests.

I found this workaround that has been working for a couple of months now.

The glitches happen when the cards overheat. So I installed iStat menus (other similar softwares are available) and crank the fan speed to max.

Found this workaround on DaVinci Resolve forums.

Olivier

[Will Duncan]

We have this issue with D500 and D700 GPU’s on the nMP.

Adobe Premiere and DaVinci Resolve both cause the GPU to overheat. One of our 5 machines doesn’t have the problem, at least not often enough to notice. The downside is that on large exports, even with the fan speed pegged, we’ll have to go through massive projects frame by frame looking for the glitches. Sometimes they only appear once or twice.

During TV productions this season, we spent a lot of time reexporting. We saw a ton of glitches. They’re drastically less common with 1080 footage and exports, but when we switch gears to 4k or above, I know we’re going to have some long nights ahead of us on those projects.

iStat Menu and bumping up the fan speed solves the problem for smaller projects in Premiere which is an $18 fix. There are free fan speed controllers but you get a lot of nice tools with iStats, so I recommend it.

Resolve we had less luck with. Bumping the fan speed up solved 98% of the problems, but on a feature length 4k production there were still a lot of problems. We exported the color project as an image sequence (it’s massive in file size) and then brought it back in an converted it to ProRes 444. This solution added roughly 5-7 hours of computing time.

We haven’t exported the final product yet. But the image sequence and conversion to ProRes has been a solid workaround. I just don’t want my editors and production teams to think that’s some kind of fix. Adding a half day of computing time to your workflow is a nightmare.