Is anyone with 15″ MbPro w/ discrete GFX NOT getting the Cuda issues?

[Jason Guerra]

I have had this same issue with both a first gen 2011 Retina MacBook Pro, and the 2014 model. The 2011 was a GT 650M and the 2014 is the GT 750M. All that is to say, it doesn’t seem to be hardware specific. It’s actually fairly random when it occurs for me. Though it has seemed to get batter recently, and I am not sure if that is related to the newest CUDA updates, the OS X 10.10.2 public beta build I am running or the fact that I have recently started using my machine with an external monitor. it still occurs once or twice a day, but it used to be every time I open Premiere, without fail.

[Kevin Monahan]

Hi Justin,
I have a slightly earlier MBP with a NVIDIA 650M. No issues, but I’m running OS X 10.8.5 and holding fast. My observation is that the issue is caused by a conflict with NVIDIA drivers and OS X 10.10 Yosemite. If you could downgrade to OS X 10.9.5, you would no longer have this issue.

Thanks,
Kevin

Kevin Monahan
Support Product Manager—DVA
Adobe After Effects
Adobe Premiere Pro
Adobe
Follow Me on Twitter!

[Peter Garaway]

Hi Guys,

This is a known issues that we’re working on along with our partners. Until we get it resolved you can try:

1. Uninstall the CUDA driver and use OpenCL or Software only
2. Roll back your OS as Kevin mentioned

Sorry for the inconvenience.

Peter Garaway
Adobe
Premiere Pro

[Robert Withers]

I’m also using a 2012 pre-retina book running 10.8.5 with an NVIDIA GeForce GT 650M. No problems. I’m going to stick to this combo as long as I can. I’m also using CC 2013? 7.2? Good luck.

Robert Withers

Independent/personal/avant-garde cinema, New York City

[Tero Ahlfors]

I have a Late 2012 iMac with a 675MX and this also happens on the latest Yosemite. Also Resolve will absolutely wreck itself if I even try to look at 4K stuff. Like hard lock and reset. There has to be some conflict with OS X and CUDA.

[Justin Crowell]

Peter, thank you so much for responding to this! Adobe has been the only one (that I can tell, anyway) who has actually been present in forums and showing concern. It seems totally possible that it’s not even an Adobe problem, but NVIDIA and Apple have been completely mum. Which is frustrating.

Anyway, things seem slightly more stable right now, as of the second of the two CUDA updates yesterday (really bizarre, right? and both with no release notes…). I also have the NVIDIA web driver installed currently, which seemed to offer some decent results. A rollback would be problematic for me–I’m in the middle of a large job, working off of a brand new machine (as in, one week old).

Thanks again!
-Justin

Editor, Motion Graphics Designer, Director
JustinCrowell.com

[Michal Sulima]

Hi, I’m new to the forum and started using it due to great premiere pro coverage and very useful insight by other users, firstly – a big thank you for countless helpful threads.

I have the exact same issue described in the thread, I have a late 2013 macbook pro, maxed specs with gt 650m and I’m a CC subscriber and I’d had adobe chats and specialists like Abishnek Kapoor on the case for a long time to no avail – it’s been over a year now.

For me the graphical glitches and crashes caused exclusively by Cuda rendering were there from the beginning, while still on Mavericks.
As a matter of fact they seemed more severe then and despite of clean installs of os, cuda, adobe software etc, didn’t go away for a moment at any stage from purchase until now.

Adobe would you please advice, this is a very serious issue that’s been going on for a year and a half in my case, hardly justifying a £2500 top spec computer with apparently cuda supported graphic card and an expensive CC subscription.

I really hope to hear from you soon, working with software or open gl while having all that expensive horsepower kind of defeats the purpose and I’d noticed that I’d never actually heard or seen nvidia comment on it. I suppose it’s the arrangements between Adobe and them.

best wishes,
Michal Sulima

[Michal Sulima]

Hello Kevin,

just to give some insight, I’d send my first and longer reply to this thread a moment ago, pending approval, but just to say, I have a late 2013 macbook pro that started with mavericks and the issue was there for me just the same as with yosemite, as a matter of fact I may have experienced more crashing then. I’d tried all the tricks the internet has and can only say for sure that it’s specifically cuda, but unfortunately not specifically yosemite.
It also has nothing to do with graphic card heat as some suggested in other places – the graphical glitches can start as early as a minute after opening premiere.

An interesting observation I’d made though is that they seem to be getting worse and more severe the longer premiere with cuda runs,
and after closing the program (usually ending in a crash and error report if worked for longer with more intense workflow) they seem to be gradually getting less and less intense and going away over time.

best,
Michal

[Kevin Monahan]

Hi Michal,
My personal advice is if you have problems with OS X 10.9, as well, roll back to OS X 10.8.5. That’s the configuration my personal MacBook Pro is using flawlessly and I have the exact machine you do. I’m the kind of editor that moves very slowly when OS X updates are released and see no burning reason to update OS X. I haven’t been a fan of the last two versions of OS X, so I’m holding fast.

Thanks,
Kevin

Kevin Monahan
Support Product Manager—DVA
Adobe After Effects
Adobe Premiere Pro
Adobe
Follow Me on Twitter!

[Kevin Monahan]

Hi Robert,

[Robert Withers] “I’m also using a 2012 pre-retina book running 10.8.5 with an NVIDIA GeForce GT 650M. No problems. I’m going to stick to this combo as long as I can.”

My rig is a 2013 retina MBP with OS X 10.8.5. I’m also sticking with this combo for as long as possible for my personal laptop. I am running CC 2014.2 (8.2) with no issues.

Cheers,
Kevin

Kevin Monahan
Support Product Manager—DVA
Adobe After Effects
Adobe Premiere Pro
Adobe
Follow Me on Twitter!