-
Premiere Pro CC 2014 & NVIDIA Quadro 4000 Mac Issues
Running the latest version of Premiere Pro CC 2014 (8.0.1) on OS X Mountain Lion (10.8.5), and have been experiencing all sorts of random playback/export issues with both software only processing and CUDA processing enabled. The previous version (Premiere Pro CC) worked like a charm without issue! Is anyone else having issues with a similar setup?
The latest was a complete system freeze during playback (CUDA enabled), and then scrambled images on the displays which could only be remedied by a forceful shutdown. Screenshot of the scrambled images attached!
-
6 Replies
-
What type of Mac Pro Specs?
Do you have SMC fan control installed? Check to see if the system is overheating while rendering. K4000 can make the internals run very hot.
Have you updated your Cuda drivers?
Andy
-
Hello Andy,
Specs below…
System:
MacPro5,1
OS X 10.8.5
2x 2.4 GHz Quad-Core Intel Xeon
16 GB 1066 MHz DDR3Graphics Card:
NVIDIA Quadro 4000 2048 MB
GPU Driver Version: 8.17.76 (313.01.04f01)
CUDA Driver Version: 6.5.14
NVIDIA Web Driver: 313.01.04f01Will look into the SMC fan control for monitoring temps as you mentioned. Yes, CUDA driver is up to date with the latest version.
-
Have you tried updating CUDA from the NVIDIA site? When I tried updating through the preference pane, it wouldn’t work. Here is a link to CUDA 6.5 https://www.nvidia.com/object/macosx-cuda-6.5.18-driver.html
-
Ryan, any updates? I am having the same problems. All sorts. Sometimes serious error pop up, shutting down PP. Sometimes computer restarts on its own after it locks up. And your above image is what I get as well. I do believe it has been determined that it is an OS and CUDA driver conflict. Here is one person’s solution…
https://forums.adobe.com/message/6949483?tstart=0#6949483
-
I have experienced this exact problem ever since Premiere added OpenCL support. The best solution has been to switch to OpenCL and no longer use CUDA.
OpenCL does not have these problems, and have not noticed any performance differences working in OpenCL vs CUDA (accept that the problem you describe ceases)
My guess is that, Adobe really worked hard to make the switch from CUDA/Nvidia only to the more widely used OpenCL, and in the process got slack or compromised in CUDA.
-
It’s a known problem. As of today, there’s no solution from Adobe and Nividia.
Here’s a long thread in Adobe forum.
https://forums.adobe.com/thread/1393885?start=0&tstart=0The work around as suggested by Adobe and Nividia is to disable CUDA and use OpenCL until they can find a solution. It’s been a while though, disappointing.
Reply to this Discussion! Login or Sign Up