-
Anyone seen this (gfx corruption)
Upgraded to Yosemite and now, when I run PrCC at some point this starts to happen:
even after quitting Pr it persists to some extent on the desktop, other apps, etc. a reboot makes it go away. Doesn’t happen in other NLE’s/apps (unless I run Pr first),but it always happens when I run Pr CC. All hardware checks out fine using hardware test. Any ideas?
late 2012 iMac
32GB RAM
GTX 680MXThanks!
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
7 Replies
-
Hi Charlie,
I have hit this once but I could not come up with a reproducible case. Do you have CUDA installed as well? Does this happen every time Premiere is open or are there any particular steps to make it happen?
Peter Garaway
Adobe
Premiere Pro -
[Peter Garaway] “Does this happen every time Premiere is open or are there any particular steps to make it happen?”
Hey Peter.. I do have Cuda installed and up to date. There doesn’t seem to be anything in particular that triggers it, but it does happen pretty regularly. Sometimes just hitting play clears it up for a while, but once it spreads beyond the source/record windows (to desktop, other apps etc.) a reboot is all that fixes it. Never saw it before installing Yosemite. Nothing unusual shows up in the logs anywhere and, as i said, hardware tests all check out fine. It only happens when I run Pr. Any ideas where i might look for clues? I’ll keep trying to figure out what’s up. Thanks!
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Exactly the same thing happening to me on my MBPr after upgrading to Yosemite. The machine usually crashes shortly after i start seeing it though. Hoping the next OSX update fixes it.
-
[Dan Pearce] “Exactly the same thing happening to me on my MBPr after upgrading to Yosemite. The machine usually crashes shortly after i start seeing it though. Hoping the next OSX update fixes it.”
… Or a Pr update. As I said, I’m running PrCC, FCP X, FCP 7, MC 8, and Resolve 11 on the same machine and so far, only Pr seems to set it off. They’re all affected by it, (as is the whole UI) once it appears. Something’s not happy. 😉
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
I am seeing this too intermittently on a Macbook Pro. Usually happens when I’m running video apps (PPro, AE or Speedgrade) on multiple desktops. Never seen it with PS, AI or any other graphics or Office program open. 2 or more video-centric apps going and I expect to see it. Wasn’t sure if it was the multiple desktop thing or not, but it’s definitely a new feature of Yosemite.
I do not see it on the iMac.
-
[Paul Neumann] “Wasn’t sure if it was the multiple desktop thing or not, but it’s definitely a new feature of Yosemite. “
FWIW, I’m running a late ’12 iMac, NVIDIA GTX 680MX, 32GB, 3TB Fusion, 2 monitors, the built in and an LG 34UM95.
It’s definitely new with Yosemite. And Pr (or something Pr is interacting with) seems to be the only thing that causes it. (so far) I wish there was something that “set it off” and I could sample the process or something to track it down, but it just seems to randomly appear…
————————————————————-
~ My FCPX Babbling blog ~
~”It is a poor craftsman who blames his tools.”~
~”The function you just attempted is not yet implemented”~ -
Same here. In After Effects and Cinema4D. Unexpected glitches in video. Stripe patterns, chunks of screen that do not refresh. Strange things. I think OpenGL is not compatible with Yosemite?
I use a Nvidia Quadro 4000 with the latest (CUDA) drivers, Yosemite, C4d16, AEcc2014.
Reply to this Discussion! Login or Sign Up