Forum Replies Created

Page 1 of 2
  • Jason, I read somewhere recently that Al Mooney of Adobe strongly advised Premiere Pro users NOT to move to El Capitan yet. He recommended keeping Yosemite upgraded but not the switch to El Capitan. Maybe that has changed. Have you heard any definitive statement from Adobe recommending the OS upgrade?
    It’s great to hear your positive results. I hope you will continue to update us on El Capitan and Premiere.
    It’s been a year now since the problems listed in this thread have been with us. I remember, barely, what a pleasure it was to edit with Premiere and my Quadro 4000 CUDA setup before the problems began with Yosemite. The latest version of Yosemite 10.10.5 does seem to perform better, but the problems have not gone away.
    thanks,
    Brian

  • Peter,
    Do you have any inside information about the upcoming release of Apple’s El Capitan OS and how it will impact Premiere’s performance? It is being touted as the savior for all our Adobe woes. If in fact it does address our issues it might explain the lack of quick fixes over the last year or so.

  • THANK YOU for your response with a very specific recommendation for the CUDA. Version. I will verify my version.
    I have a suggestion for Adobe to help alleviate some of the frustration in general.
    The current model of users gathering in forum to figure out problems from each other can be helpful at times, but doesn’t it make more sense if the techs and designers at Adobe provide this service to it’s users with a site where official updates, recommendations, best practices and even troubleshooting procedures could be found, a sort of continuous, ongoing support website for it’s users?
    Please pass this idea along at Adobe.

  • This thread started on Dec 23, 2014.

    WHERE IS ADOBE SUPPORT?
    Speculation is all we can do.
    Do we dump Yosemite?
    Do we go back to Mavericks?
    WHERE IS ADOBE SUPPORT?
    Everday my “normal” workflow includes multiple crashes, time lost, and frustration.
    I can remember when it was a joy to edit. That memory has almost faded completely.
    WHERE IS ADOBE SUPPORT?
    Do we really have to hit the 1 year anniversary of this thread with no solution to this problem.
    WHERE IS ADOBE SUPPORT?

    HELP US!

  • I’ve now switched to Open CL, completly bypassing CUDA , and having less problems, a few graphic glitches but no crashes so far.
    When will Adobe address this problem? I’ve invested in 2 Quadro 4000 cards for my Mac Pros. Adobe couldn’t have touted how great CUDA was more than they have in the last year. and it was great, WHEN IT WORKED. Now it is dead in the water.
    Is anyone from Adobe reading this?
    Please respond

  • I went back 2 versions and after doing a uninstall of Ver 7.0.29 driver for MAC, and reinstalled Ver 6.5.45
    Why did I do that? Well, on the Nvidia site where you download the driver, if you go to the information tab you see this message:

    “Note: this driver does not support the older generation GPUs with SM1.x. Please download CUDA driver 6.5.45 which supports SM1.x.”

    What the heck is SM1.x. ?

    After checking out the System Report on both my Mac Pros (4,1 and 5,1) , the GPU numbers for each are SMC V 1,39f5 and SMC V 1.39F11, Assuming that this is what the Nvidia note is referring to, that means that version 6.5.45 is the last version compatible with my Mac Pros.

    Going on this assumption, I uninstalled the latest drivers on both Mac Pros and reinstalled V 6.5.45

    So far so good performance wise, BUT I haven’t had a really long editing session yet and am not ready to claim success yet.

    If anyone can verify my logic in the steps I took, that would be greatly appreciated. In the meantime I will let you all know if I encounter the problem again.
    Fingers crossed.

  • I installed the latest CUDA driver Version: 7.0.29 and initially I thought it solved the problem , but alas, the graphic artifacts reappeared and I’ve had several crashes. To be fair I am working on a graphic intensive sequence with up to 8 layers, some nested, but I’ve done that in the past, BY (before Yosemite).
    I really am thinking about going back to Mavericks, Any thoughts?

  • You’re right, I should have made it clear that I was talking about a Mac Pro (5,1) with a Quadro 4000

  • I just downloaded and installed a new version (new to me anyway) of the GPU driver, Ver 10.3.1 (343.02.02f01) This is in addition to having previously installed the latest CUDA driver Ver 6.5.46

    I was never alerted to this new GPU driver in my CUDA preferences (inside my system Prefs)

    I found this over at an Adobe forum:

    136. Re: Adobe Premiere Pro CC Glitches Screen & Crashes Computer
    thomasdavis79 Community Member thomasdavis79 Jan 29, 2015 7:26 AM (in response to Dennzus)
    Dennzus (and et al.), what GPU driver are you using? You must use 10.1.43 (343.02.01f01) when using Yosemite. Found under CUDA preferences.

    If you have Yosemite 10.10.1:
    NVIDIA DRIVERS Quadro & GeForce Mac OS X Driver Release 343.02.01

    If you have 10.10.2:
    NVIDIA DRIVERS Quadro & GeForce Mac OS X Driver Release 343.02.02

    I installed it and everything seems to be working great. SO FAR. After I get back to work in tomorrow’s editing session I will see if the graphics are back to normal.

  • I 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.46

    Also 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.

Page 1 of 2

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