Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro NVIDIA Card with Yosemite and Premiere causing major graphics failure

  • Andrew Johnstone

    May 8, 2015 at 1:55 pm

    And it is worth pointing out that while FCP7 is much slower than PP for all the various 32 v. 63 bit architecture reasons (and everything else) FCP& is completely stable and I have no video playback issues what so ever.

    So is my problem essentially not a graphics card/driver problem but actually an issue with PP itself?

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

  • Jason Guerra

    May 8, 2015 at 3:24 pm

    The problem is with Nvidia’s CUDA drivers. FCP does not leverage CUDA. FCP 7 does not use any GPU acceleration (one of the many reasons it’s slower), and FCP X uses OpenCL to power its GPU acceleration, so neither version will have this issue.

    Premiere Pro can use either OpenCL or CUDA. CUDA is generally faster, but with this bug it’s obviously not the best tool right now. Unfortunately simply choosing OpenCL from PP’s Mercy Playback drop down in project settings does not resolve the issue. Several people, myself included, have restorted to completely removing the CUDA drivers and have found that resolves the issue. Kevin from Adobe posted a list of directories you need to delete in order to completely remove CUDA, earlier in this thread. All of these need to be removed, or a left over piece of the driver may still cause issues.

  • Andrew Johnstone

    May 8, 2015 at 4:34 pm

    Yes of course, but I am not convinced disabling my work station just for PP is worth all that hoo haa. The bottom line is that I simply do not have time to fiddle about testing settings etc. This is the job for the programme developers. As an end user I just need to be able to boot up and work. We pay good money to Adobe for this software and they owe us all a fix clearly! I am sure they are doing what they can and I confess I never had that sort of confidence in Apple when things went wrong with FCP.

    The fact remains that FCP7 is still a very good work horse and although it is slower, I have had no issues with my edit at all today. It is a shame as I enjoy Premiere Pro.

    I have done all I can to eliminate issues. I have re-plumbed all my drives. I have cut still file sizes. I have cleaned out my render cash/scratch disk, but nothing seems to improve the performance and playback. Very frustrating.

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

  • Brian Cooney

    May 8, 2015 at 10:30 pm

    Anyone having solid success with Current CC2014 and Mavericks? Thinking I need to go back. Having terrible issues lately.

    Head of Post Production, Coca-Cola Studios Atlanta, GA. Telly Award Winning Editor and Motion Gfx Artist.

  • David Roth weiss

    May 8, 2015 at 10:42 pm

    Yes! Running on an older 2008 Mac Pro under Mavericks, with a GTX 680 Mac Edition and Cuda.

    David Roth Weiss
    Director/Editor/Colorist
    David Weiss Productions

    David is a Creative COW contributing editor and a forum host of the Apple Final Cut Pro forum.

  • Andrew Kimery

    May 8, 2015 at 11:35 pm

    [Brian Cooney] “Anyone having solid success with Current CC2014 and Mavericks? Thinking I need to go back. Having terrible issues lately.”

    I’ve got a 2009 MP with Mav and an Nvidia 660ti and I can use OpenCL but if I switch to CUDA things get wonky.

  • Brian Cooney

    May 8, 2015 at 11:48 pm

    Thanks guys. I’m running….

    iMac (27-inch, Late 2012)
    3.4 GHz Intel Core i7
    32 GB 1600 MHz DDR3
    NVIDIA GeForce GTX 680MX 2048 MB

    Just did the latest apple proapps updates (i also have FCPX installed) and safari update the other day and PPro is barely running..

    Head of Post Production, Coca-Cola Studios Atlanta, GA. Telly Award Winning Editor and Motion Gfx Artist.

  • Andrew Johnstone

    May 9, 2015 at 7:29 am

    [Peter Garaway] ” To uninstall the driver move each of the following items to the Trash, then reboot:

    /Library/Frameworks/CUDA.framework
    /Library/LaunchAgents/com.nvidia.CUDASoftwareUpdate.plist
    /Library/PreferencePanes/CUDA Preferences.prefPane
    /System/Library/Extensions/CUDA
    /System/Library/StartupItems/CUDA
    /usr/local/cuda/lib/libcuda.dylib

    Best,

    Peter Garaway”

    At the top of this thread somewhere, Peter suggested removing the drivers. So I thought I would have a go at this and then see if PP would start behaving. But I cannot find any of these files listed on my system !

    I have read that the CUDA drivers are built in to Mountain Lion 10.8.5 Is this so? Are they not accessible?

    Maybe I don;t have a CUDA issue at all? Maybe this is some other PP glitch? Whatever it is I am running out of patience for this!

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

  • Jason Guerra

    May 9, 2015 at 7:36 am

    No, CUDA is not built into the system. Any Mac with an Nvidia card will, of course, have drivers for that card, but that is not the same thing as CUDA, which you have to manually download and install from Nvidia’s site.

    In System Preferences, do you see an option for CUDA? If not, and you don’t have the folders you listed, Then CUDA is not installed on your system. If you see the CUDA preference pane, make sure you are looking in the right Library folder. There is a user Library folder in your home folder, and a system Library folder at the root of you Macintosh HD. The CUDA folders are in the root Library folder.

    I hope that helps.

  • Rob Davis

    May 9, 2015 at 4:26 pm

    I too have been having this issue with my late 2014 Macbook Pro and posted it here: https://forums.creativecow.net/thread/3/964588

    I’m under the impression this is an issue with the CUDA drivers. Can’t decide whether to uninstall and run off the CPU or just live with it for now. It’s even worse when using an external thunderbolt display. Why has this not been fixed?!

Page 16 of 27

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy