Graphics problem after Yosemite upgrade

[Paul Neumann]

I’ve seen this too. Also seen it with multiple desktops open. Have not seen it when only PPro is running.

[Charlie Austin]

No help, but you’re not alone… https://forums.creativecow.net/readpost/3/960245

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

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

[Buddy Brett ramker]

I have seen some of these issues. After first upgrading, GPU offload via CUDA was not available and my CUDA panel said it was up to date. After digging a bit, I discovered that the CUDA did need an update and I did it manually. All that being said, I noticed some of the same issues with Mavericks. Usually when switching in and out of Premiere.

Hope this helps,

Brett

[Paul Jones]

I also did the manual CUDA update on iMac and Macbook Pro and no difference.

[Andrew Johnstone]

OK so this is not helpful…but my rule of thumb, having been caught out a few times with Apple OS upgrades is…”Don’t upgrade unless you really have to!”

I lost Photoshop for years when I did one system upgrade and PS3 was no longer supported. I am now using Adobe CS 6 and still using FCP7 (for BBC jobs) and both run fine on my current system. So even thought I am now two steps behind Yosemite…(I think I am on Snow Leopard still) I am not going to upgrade any time soon.

I have a plan to get a new MacBook Pro (to replace my steam driven machine that is now 8 years old – hey it still works geezers!) and I will test any software on that before blindly upgrading to the next OS.

The bottom line is if your OS is good enough for you to be able to deliver content to your clients’ don;t mess with it. These people (Apple, Adobe & Chums) are just after your money and they do not care one bit about your workflow or your business. The truth is that the OS and the software have actually been good enough for years!

Andy Johnstone
Wild Dog Limited
film & multimedia production
http://www.wilddogworld.com

[Paul Neumann]

OK. So I’m getting some of this in Power Point this morning as I’m fixing them to drop into an edit. Premiere Pro (nor any other Adobe app) is not open.

Let’s start pointing our efforts to Apple and Nvidia.

[Charlie Austin]

[Paul Neumann] “OK. So I’m getting some of this in Power Point this morning as I’m fixing them to drop into an edit. Premiere Pro (nor any other Adobe app) is not open.

Let’s start pointing our efforts to Apple and Nvidia.
“

Interesting, I wonder if Pr and PP use any frameworks/drivers/etc. in common? All I know is that this does not happen at all when I run any other other NLE or video app. It pretty much always occurs after running Pr. Which sucks as I’m working in it now….

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

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

[Gregory David]

I have the same issue. Worse, I lose video in the program monitor and often in the source monitor. The only thing that fixes it is to switch from Cuda to software only and back again, or a restart. Of course you loose your renders if you do this.

I am on a macbook pro early 2013 16gg ram – 11 given to Pr. I have just done a clean install to try to clear it up. The cuda driver is the most recent and privileges are correct.

I am unfortunately on Yosemite, but I was having very similar issues on the previous OS.

I think the issue is with the Cuda driver and the way Pr reads from the previews. Needless to say I am not a happy camper.

[Paul Neumann]

I’m thinking I started seeing this with the last update of Mavericks (10.9.5?). I know that update broke the Keychain in some instances and sent my CPU to new heights until I unbound my network status.

Also on Early 2013 MBP/16gig.

[Paul Jones]

I have more developments on this problem.
Today I had to fire up Final Cut Pro 7 to recut an old job (which surprisingly seemed to work perfectly with Yosemite)
I got the same graphics glitches, as I did with Quicktime X and iTunes.
So maybe it’s not an Adobe problem after all??