Activity › Forums › Adobe Premiere Pro › NVIDIA Card with Yosemite and Premiere causing major graphics failure
-
NVIDIA Card with Yosemite and Premiere causing major graphics failure
John Vargo replied 8 years, 9 months ago 60 Members · 268 Replies
-
Ze’ev Gilad
February 21, 2015 at 11:26 pmActually, from what I’ve gathered, speaking with nvidia, as well as watching my GPU usage monitor (iStat Menus),
OpenCL *does* use the GPU, but less efficiently.Do a test of OpenCL vs Software-Only and see what you get. It should be considerably faster.
-
Kevin Balling
February 21, 2015 at 11:40 pmI don’t use CUDA, only Open CL and I get the problem with Premiere. I use Mountain Lion and I am on a late 2012 iMAC.
3.4 GHz Intel Core i7
Memory 16 GB 1600 MHz DDR3
NVIDIA GeForce GTX 675MX 1024 MBKevin Balling
Tin Roof Video
http://www.tinroofvideo.com -
Brian Vawter
February 22, 2015 at 6:56 pmI too have been having this Graphics Nightmare since installing Yosemite.
Currently running Yosemite 10.10.2, on a Mac Pro 4,1 (early 2009), with a Quadro 4000 and the latest CUDA
Driver Version 6.5.46Also someone mentioned crashing issues while using PPro. I have been using my Utility Monitor to keep an eye on RAM usage and find that I can avoid the crashing by restarting when I’ve used up about 13 of my 16 GBs of RAM… pain in the ass, but I can keep working.
All the “should have backed upped” type comments are beside the point.
NVIDIA and Adobe need to get together and figure this out pronto, or the wisdom of paying that monthly fee to Creative Cloud is going to be seriously questioned.
-
Brian Cooney
February 22, 2015 at 8:33 pmI agree. I have encountered nothing but issues with CC from the installation of CC and CC2014 on 2014 MacPros as well as iMacs. Adobe seems to have corrected many of the issues along the way, but they seem to be quite behind the curve. I’m hoping someone comes up with something soon, otherwise why not go PC? – which to me would be the most devastating blow since the unprecedented sudden and abrupt yanking of FCP7.
Head of Post Production, Coca-Cola Studios Atlanta, GA. Telly Award Winning Editor and Motion Gfx Artist.
-
Ze’ev Gilad
February 24, 2015 at 11:24 pmLatest from nvidia:
Response Via Email (Gareth) 02/24/2015 03:22 PM
Hi,There is an active investigation into these reports ongoing in conjunction with Apple and Adobe, but I don’t have any specifics on the root cause or when a fix might arrive.
Regards,
Gareth
Nvidia Customer Care
-
Justin Crowell
February 25, 2015 at 2:18 amJust want to add my two cents. I’ve been dealing with this problem on a Late 2013 15″ MbPro (with the 750M GPU). I’ve been actively (and angrily, sometimes too rudely, sorry Peter!) posting about this on a really long forum at Adobe:
https://forums.adobe.com/message/7222460#7222460Important notes:
– The repair program that is being touted as a solution is most likely unrelated to our problem. The repair appears to be for a hardware failure that has been around since 2011. Apple is seemingly only posting it now because of a recent class-action lawsuit.
– I have yet to see a single person for whom a hardware repair has provided the solution.
– To the contrary, it appears that the bugs are made more severe in 10.9 and 10.10, indicating a driver/software issue.
– Adobe’s techs seem to be struggling to replicate the bug. I’ve offered (and continue to offer) to communicate directly with them to help.
– This is not a keystroke or order-of-launching type bug. It can’t be simplified in that fashion.I’d go down to the Apple store and shout, telling them I’ve bought a $3000 paperweight that I’m embarrassed to use in front of clients. But it won’t do any good. And that’s the reason why my next machine won’t be an Apple.
Editor, Motion Graphics Designer, Director
JustinCrowell.com -
Brian Cooney
February 25, 2015 at 2:46 amGood news. thanks Gareth!
Head of Post Production, Coca-Cola Studios Atlanta, GA. Telly Award Winning Editor and Motion Gfx Artist.
-
John Vargo
February 25, 2015 at 9:58 pm -
Brian Cooney
February 25, 2015 at 10:12 pmI am not using CUDA but it started happening again today with OpenCL. Which I heard it wasn’t supposed to. Actually worked without issue for a few days. However, I opened a project from another editor who uses CUDA. I wonder if that had anything to do with it? But I don’t know how that is possible. Project was set to Open CL per my default. I deleted render files but didn’t fix it.
Head of Post Production, Coca-Cola Studios Atlanta, GA. Telly Award Winning Editor and Motion Gfx Artist.
-
Justin Crowell
February 25, 2015 at 10:34 pm“I am not using CUDA but it started happening again today with OpenCL. Which I heard it wasn’t supposed to. ”
I know that for me (and from what I can tell, most other people), it happens when either GPU option is enabled as long as the CUDA drivers are installed.
Editor, Motion Graphics Designer, Director
JustinCrowell.com
Reply to this Discussion! Login or Sign Up
