-
All replies
-
Helpful answers
-
-
Dec 15, 2015 4:28 AM in response to NtNextby Professor Denim,same. 12 core with D700 running Resolve. Glitches and artefacts on the picture while trying to export footage. Doesn't matter resolution, size or codec. Its been impossible to get a clean export out of resolve with this so called professional machine. Got my 2 D700 and Logic Board switched but the problem persists. Trying to control fan speed to avoid overheating does nothing....
-
Dec 22, 2015 5:44 AM in response to NtNextby BlackF1re83,After experiencing all kind of problems with Resolve 12 on Mac OS, i've tried several tests.
I tried with a MacPro 2013 6 core and 12 core, both equipped with 16GB RAM and dual D700.
Video footage is on a Fibre Channel array 8Gbit Raid 5, performing 700 MB/s in both read and write where the media files are placed.
Footage is in 3840x2160 P25 ProRes422
With MacOS 10.10.5 and 10.11.2, with Resolve 12.1, there's simply no way to work properly.
Everything is slow, especially in 4K. Very quickly the system is so hot i can cook eggs on it, until it simply shuts down for overheating.
Today, out of desperation, i've used BootCamp and installed Windows 8.1 Pro.
The default Crimson Driver 15.2 embedded with Bootcamp 6.0 recognise properly the cards as D700, and it's also possible to put them in CrossfireX
I've tried to upgrade them at the 15.3 version, but i get an error of "no compatible device present". Not an issue, the 15.2 is ok.
Installed Resolve 12.1 for Windows and...... BLAZING FAST.
Works in 4k like a charm. Even the 6 core D700 on windows is way faster than a 12 core on Mac. The stabiliser is one of the best way to test it.
Stabilising a clip of 1 minute in 4K on Mac takes 3 to 4 minutes.
The very same clip, on Windows Bootcamp takes 30 to 40 seconds.
And no overheat till now.
I still have to test exports and many other things, but i wanted to let you know the first results looking promising.
Honestly, i have no words.
There's something critically wrong in the video card driver management on Mac. Maybe a memory leak that cause an overheat.
-
Dec 22, 2015 7:44 AM in response to BlackF1re83by Grant Bennet-Alder,A Mac Pro late 2013 that does not have Hardware problems should NEVER overheat to the point of emergency power-Off.
Practically the entire reason that Mac exists in that form is to have two fast graphics card and to stay cool, no matter what you ask it to do. There is something terribly wrong with yours.
-
Dec 22, 2015 7:56 AM in response to Grant Bennet-Alderby BlackF1re83,Believe me, i've tested this with multiple MacPros, and i have several situations of sudden power down from extreme overheat with multiple customers (we sell and configure systems for Video Editing, so i have experience with several high end systems).
Multiple times i've sent the MacPros to replace video cards after these issues. Happens more frequently with a 12 core, but the point in common is the D700.
NEVER happened with a D500.
The Apple repair center here in Italy told me they had an incredible amount of return of MacPro 2013, and practically every single one was with D700 cards where they needed to replace it after overheating. Sometimes, after a replacement, the overheat event was happening again, and the card was in needed to be replaced again.
Those without an AppleCare spent a fortune for the repairs.
-
Dec 22, 2015 8:37 AM in response to BlackF1re83by Grant Bennet-Alder,Are you running the latest firmware, especially SMC firmware:
Mac Pro
Computer Identifier EFI Boot ROM version SMC version Mac Pro (Late 2013) MacPro6,1 MP61.0116.B16 (2015-002) 2.20f18 (SMC 2.0) -
Dec 22, 2015 8:40 AM in response to Grant Bennet-Alderby BlackF1re83,Both correspond to your screenshot
-
Jan 11, 2016 12:42 PM in response to NtNextby Chief Sneed,Did anyone ever find a solution to this problem? Same thing is happening to me. I started exporting via Premiere Pro/Media Encoder because Resolve couldn't cut it.
What I found was that Premiere Pro generally could export a 4K image with out errors. But when I would "punch in" or drop a 4K image on a 1080 timeline, I'd get only glitch errors on those.
Now I haven't mixed and matched render batches to see if it's specifically that problem but it is a little comforting to know it's definitely not DaVinci.
-
May 8, 2016 11:31 AM in response to NtNextby jegs2sherri,Unfortunately, running the new Mac Pro on Windows 10 via Boot Camp does not address the issues with the AMD card. I run Fallout 4 upstairs on my older Mac Pro with no issues at all, for hours at a time, on high graphics settings. Conversely, my wife's newer Mac Pro crashes to desktop, even on medium graphics settings, after less than an hour of play ... then attempts to restart the game yield terrible frame-rates.
Have downloaded and installed the latest Windows drivers from AMD ... no dice. Downloaded and installed the latest Boot Camp drivers from Apple ... no dice. Haven't yet tried setting the machine on top of a fan, as I saw someone do above.
This was an awfully big expense for a machine to be incapable of running a video game (on Windows 10) that my six-year old Mac Pro can run without effort.
Shameful.
-

