Graphics problem after Yosemite upgrade

[Charlie Austin]

[Paul Jones] “I got the same graphics glitches, as I did with Quicktime X and iTunes.
So maybe it’s not an Adobe problem after all??”

Had you run Pr at all prior to opening 7? Also… do we all have Nvidia GPU’s? Maybe it’s something in the GPU driver in the system? (not the CUDA driver)

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Paul Jones]

I believe I did run Premiere before opening the other apps….and yes, my iMac and Macbook Pro both NVIDIA graphics

[Charlie Austin]

[Paul Jones] “I believe I did run Premiere before opening the other apps….and yes, my iMac and Macbook Pro both NVIDIA graphics”

If you can, maybe try rebooting your computer and then running FCP 7 without running Pr first. I’m not pointing fingers, but it seems like Pr, or something modified in the OS it’s trying to use, is the common denominator.

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Dennis Radeke]

[Andrew Johnstone] “”Don’t upgrade unless you really have to!””

Agreed. I’ve been of the opinion that the last few Apple OS’s haven’t really added a whole lot in the way of features, but that’s probably a ‘whole nuther’ forum’…

My STRONG recommendation is that users who are moving to a new OS, START FRESH and do a CLEAN INSTALL. Gone are the days when a casual upgrade would just work. There are millions of bits in an OS and the chance to mess a few of those up is probably pretty high.

Yes, it’s a pain and I know because I’ve done my own clean installs many times – from about 10.2 onward. It does make for a better, faster, more stable machine.

My 2 cents,
Dennis

[Douglas Morse]

Try these 4 options:

1. Upgrade your CUDA drivers

https://www.nvidia.com/object/mac-driver-archive.html

2. Upgrade to Nvidia web driver. This thread on Macrumors USUALLY has up to date information and instructions https://forums.macrumors.com/showthread.php?t=1748213&page=3 Often someone will post a link to a modded file that will skip the system compatibility check and allow you to use it. If not, you need to do it manually. Easy actually.

you need to download the driver here https://www.nvidia.com/download/driverResults.aspx/78853?ClickID=ayzyywk50wasw5osownsyayny5npwkvsysks

Copy the package to your desktop

Expand the .pkg From TERMINAL:

pkgutil –expand ~/Desktop/WebDriver-WebDriver-343.01.01f01 ~/Desktop/WebDriver
use text edit on ~/Desktop/WebDriver/Distribution
file on the line which contains the code

var found_hardware = 0
change to
var found_hardware = 1
(use the find command to find the line you need easily. Then save of course)

Delete old .pkg then run this command:

From Terminal
pkgutil –flatten ~/Desktop/WebDriver ~/Desktop/WebDriver-343.01.01f01.pkg

* If the web driver number changes to a newer version, you’ll need to change these references approriately.

Then of course double click on the file. It may not let you install it without another step. Open up system preferences security and there will be a box that says ‘install anyway’

3. Also install GFX Card status and keep you computer from switching graphics cards (you can also do this is the system control panel as well) https://gfx.io Go all nvidia dgpu when you are editing. Or if you are still experiencing problems, switch to integrated only until apple releases a fix.

4. SMC fan control is a nice little utility as well. Crank up the fans https://www.macupdate.com/app/mac/23049/smcfancontrol and get some sweet Sony 7510s https://www.bhphotovideo.com/c/product/758126-REG/Sony_MDR_7510_MDR_7510_Professional_Studio_Headphones.html

[Paul Jones]

I managed to upgrade the CUDA drivers but not the NVIDIA web drivers.
It said not valid for this system…I also tried via the terminal but it was having none of it.
Also there is a bit of an update on this.
Today I have been working on Premiere Pro all day, everything was fine until I opened Photoshop (see photo attached)
I closed Photoshop and carried on working in PP as normal.
TBC….

[Douglas Morse]

The web drivers need to be modified as outlined in the Macrumors forum thread. For every minor update of Mac OSX, there is a new web driver released. It’s actually quite easy once you get the hang of it. I’m running without graphics glitches so far (fingers crossed)

[Dax Roggio]

I have been experiencing the same problem with my MacBook Pro (Late 2013, NVIDIA GT 750M, OS X 10.10.1). I have the latest CUDA driver installed through the control panel. After trying many troubleshooting options, I have been unable to find a solution. However, I have discovered some patterns that may shed some light on the source of the problem.

The funky display craziness affects all apps, but it only occurs after I have been running Premiere (CC 2014.1) or while Premiere is running.

More specifically, the problem only occurs if I have been working on a project that has Renderer set to CUDA (Project Settings > General > Video Rendering and Playback).

If I use OpenCL, the problem never starts.

So one solution for me personally would be to stick with OpenCL, which used to work just fine. However, OpenCL rendering in Premiere has stopped working properly for me for clips that have motion stabilization applied. Rendered clips come out with big black blocks. This is true for preview files within Premiere or when exporting through AME with OpenCL enabled. I don’t know if that issue is related to the CUDA problem or not. It did seem to start around the time I upgraded to Yosemite.

So the solution to original problem was to switch to CUDA, but that has led me to the problem described in this thread.

In summary, the issue is clearly related to CUDA, and it seems that the problem began for most people after upgrading to Yosemite. Premiere is clearly a culprit, although it’s the only app I run that actually uses CUDA. So it’s difficult to say whether it’s a Premiere problem or CUDA in general.

Turning Automatic graphics switching on or off doesn’t seem to have any bearing on the problem.

Lastly, I only installed the CUDA driver in the first place to run DaVinci Resolve, which won’t launch without it, even though it can use OpenCL. I tried uninstalling CUDA, but the OpenCL rendering issue remained. So I had to re-install it.

At this point, I’m hoping to see an update to either the CUDA driver, OS X, or Premiere Pro that addresses the issue. It would be nice to know if any of them were working on a solution.

[Charlie Austin]

[Dax Roggio] “More specifically, the problem only occurs if I have been working on a project that has Renderer set to CUDA (Project Settings > General > Video Rendering and Playback).

If I use OpenCL, the problem never start”

I can confirm this as well. As PrCC isn’t my main axe, so to speak, I haven’t seen the stabilization rendering issues you note, but I’ll keep an eye out… 🙂

————————————————————-

~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~

[Gregory David]

These issues have been driving me crazy. Won’t bore with all the crap and just cut to the chase. I removed the CUDA driver: Cuda com.nvidia.cuda.launcher.plist (LaunchDaemons) and com.nvidia.CUDASoftwareUpdate (LaunchAgents) AND.. ISSUES GONE – both dropping of video, which was the worst one and all the graphics garbage. I have just done a successful export using OpenCL. I don’t know whats going on here or what to do to get reasonable performance back on my early 2013 macbook pro 2.7ghz with 16meg ram, but this clearly isolates the problem and gives me a way to work. Good luck to you!