Adobe Premiere Pro CC Glitches Screen & Crashes Computer

[hearlyfilms]

I have been experiencing this problem for about three weeks now. I am editing on a MacBook Pro with 2.4 GHz i7, 16GB RAM, 250SSD, Thunderbolt to 3TB drive, and a thunderbolt-DVI adapter to Apple Cinema Display. I am editing 4K RED EPIC footage and my computer is wigging out on me.

I have been editing high quality footage on this machine with these drives and settings for a while. I originally thought this was a CUDA issue or graphics card issue. I switched to OpenCL and edited for a while and had the same issue again. I even took my machine to Apple and they put a new logic board and graphics chipset in it because we thought that would solve the issue. Again, same problems. I originally thought this might be just a Premiere Pro issue, however today I was exporting a 10 minute 4K, downgrade to 1080p video in AME and had the same glitch issue. This is what happens when a crash occurs:

1. Slowed perfomance of timeline and video responsiveness
2. Program window goes either Black, White, or Gray (when this happens, I know it's game over... Thank you Auto-Save)
3. Clicking, Moving Mouse, Typing, ANYTHING from there gives me a completely glitching out display for around 1 minute
4. Whole screen goes black, seconds later...
5. Log in screen

The attached pictures give you an idea of what the screen is looking like when the glitch occurs.

Anyone experience this issue? Everything I have is up to date including CUDA, the Apps themselves, everything.

THANKS!

[cmgallego]

I have the same config and same problems!!!

[wilddog_uk]

I need a solution to this problem fast.

I have had to rescue my edit by reverting to FCP7, but this is not ideal and much slower than working in Premiere Pro these days. I have done everything I can think of to try and eliminate the issue, but nothing has worked. I don't graphics issues (ie screen distortion, jumping, blocky lines of video clips) from any other app on my system so it has to be more than just a NVIDIA Geoforce  graphics card issue. It must also be to do with how Premiere interacts with the graphics card. What is strange is how the problem develop and seems to deteriorate. My glitching was on intermittent and now it seems to be on pretty much every sequence I try to cut or grade.

What are the solutions? Jumping ship to FCPX or Lightworks perhaps? Not really an option as I have invested in a whole suite of software from Adobe for a reason!

[LMC vision]

Hi wilddog_uk, if you have this kind of problem from my experience, and Kevin from Adobe can confirm this, I can suggest you to disable the CUDA acceleration Engine on premiere, and use only OpenCL,

BUT for me it was necessary to disable and uninstall the CUDA driver to to prevent the appearance of Glitch on System OS during editing especially in the use of contemporary more tan one adobe cc app, es. premiere with photoshop, or after effect.

after you uninstall the CUDA Driver you have to reboot.

With OpenCL It is not that bad , but not as fast as when the CUDA works

We All Hope in a fix SOON

[wilddog_uk]

I am running Premiere CS6 and OSX 10.8.5 Mountain Lion. from what I can see the drivers are built into the OS and I see no way of disabling them.

Andy

[wilddog_uk]

OK.  Speaking to an After Effects specialist colleague about this issue, who pointed out to me that GPU acceleration only works with over 1mb of VRAM on the graphics card. My card a Geoforce 650M only has 512mb of Ram, so the  problems I am having cannot there for be CUDA related. There must be another issue.

The most likely issue I think it that all of these problems I have had with PP have come since I started to grade my film. The only thing I can think of is that with large projects, everything has to be sorted on a RAID 0 thunderbolt drive. Odd, since I have just upgraded my system from a FIREWIRE/USB3 combination to 2 x thunderbolt drives.

Anyway, the problem is still not resolved and I have since re-cut & graded the film on Final Cut Pro 7. Nice to know that my old workhorse still works...but quite where this leaves my plans to use Premiere Pro as my NLE of choice remains to be seen.

[Nobilis_Bellator]

To my knowledge these issues have not impacted and have not caused any issues when working in AE. At least I can confirm that on my end of things. Glitches and crashes only happen when using PremIere Pro and once again i will add for those who have not read all the comments. These glitches and crashes can disappear completly if you disable the CUDA driver in your PP project and if you do not encode using CUDA but only use Mercury Playback Engine Software only.

Hope this helps.

[wilddog_uk]

OK, I am going to bow out of this discussion.

I have finally nailed the problem that has been causing all the issues on my Premiere Pro time line. I bought a plugin to fix a problem with some strobing/flickering footage and this is the source of the grief. The plugin demands too much horse power from my system and causes the flickering images and blocky play back/rendering issue that I have seen. When in combination with other effects added to the time line (simple colour grades from the 'Fast Colour Corrector" built into PP), this plugin causes all the havoc.

I have notified the plugin producer and I am now hoping for a refund.

from what I can see, PP requires a significant amount of system resources to render effects in real time and clearly my system is not up to it. I will need to find someone with a much more powerful set up for colour grading in PP. I would recommend that anyone else that is having issues with image playback/rendering in PP checks to see if the following steps will fix their issue:

1) duplicate the project (as a precaution)

2) in the duplicated project 'unlink' the video and audio time lines

3) select the video track and select "Remove Effects".

If your film plays back with not glitches/hitches after following these steps, then like me, you system just lacks the juice to work with all of PP's built in features.

Interestingly though I do not have similar issues in FCP7. My colour grade has worked fine through the entire timeline in FCP7.

[carylee2002]

I too am running mtn lion 10.8.5 and CS6…no problems and can edit 4k footage at 1/2 proxy with ease. Maybe you all should go back to mtn lion. I found Mavericks and Yosemite buggy and now went back to mtn lion and no more headaches.

[Halycon Design]

I have been struggling with the same problems as listed above since installing the GTX680 Mac Edition a few months ago. And yes, the simple answer would be to shift to another graphics card but there is not a lot of choice for something that works this well (when it is not crashing or glitching)...when the GTX is working it works fast.

It is also hard to nail who the real culprit here however. It is obviously a problem with the combination of Adobe Premiere Pro, Yosemite and Nvidia but it seems to me that Apple are not making things easy (never have when it comes to Adobe). Just the same I am hoping that the new version of Premiere about to be released will resolve a lot of these issues. Here's hoping!

[paulejonesy]

Afternoon.

I think it's important to stress that this problem (as described by the OP) is solved by not just disabling CUDA in the project preferences, but by completely removing it from the system. I found concrete information hard to find when reading these 10+ pages.

Delete these files and re-boot. Premiere will render using OpenCL

/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

This solved the problem for me. This was after 2 logic board replacements from Apple, and hours of searching and troubleshooting. (not to mention hours of wasted time dealing with the aftermath of hard system crashes and the resultant unsaved projects.)

It seems to me that the M class NVIDIA GPU, CUDA and Premiere (and for that matter Resolve) just don't play well together. Using OpenCL I have had no problems.

I hope I don't have to write a retraction post tomorrow when it all goes t*ts up. 🙂

My system is a MacBookPro10,1, (early 2013) with a 650M GPU, 16GB RAM and a 2.7GHz CPU. 10.10.3, PPCC 2014 (8.1) 2880x1800 Built-in display.

[RacerX2oo3]

NVIDIA is aware of the issues some of you have been experiencing with GPUs, Mac OS X Yosemite and Premiere Pro CC.  We’ve been doing extensive work internally and with Adobe to determine the source of the problem. We know the CUDA performance advantage you get with Premiere Pro CC on Mac is important for video pros, so finding a solution is a top priority.  It’s not yet clear that the issue is directly related to CUDA, but we’re looking at all options.  NVIDIA GPUs support both CUDA and OpenCL, so the temporary solution we suggest is to run Premiere Pro CC using OpenCL.  You can select this from within the Project Settings menu.  Choose “Mercury Playback Engine GPU Acceleration (OpenCL)”.  This setting appears to reduce the occurrence of the problem.  As soon as we identify a fix that lets you return to fast CUDA acceleration, we’ll provide an update here.

[Kevin-Monahan]

Hi Sean,

NVIDIA is aware of the issues some of you have been experiencing with GPUs, Mac OS X Yosemite and Premiere Pro CC.  We’ve been doing extensive work internally and with Adobe to determine the source of the problem. We know the CUDA performance advantage you get with Premiere Pro CC on Mac is important for video pros, so finding a solution is a top priority.  It’s not yet clear that the issue is directly related to CUDA, but we’re looking at all options.  NVIDIA GPUs support both CUDA and OpenCL, so the temporary solution we suggest is to run Premiere Pro CC using OpenCL.  You can select this from within the Project Settings menu.  Choose “Mercury Playback Engine GPU Acceleration (OpenCL)”.  This setting appears to reduce the occurrence of the problem.  As soon as we identify a fix that lets you return to fast CUDA acceleration, we’ll provide an update here.

Thanks so much for responding.

Regards,
Kevin

[Nobilis_Bellator]

Thank you for taking the time to tell us what you just did....;-)

[eric10001]

It's great to hear from a NVIDIA rep - thanks Sean/RacerX.  Can you give us a time range when we might see a fix?  Are we talking weeks, months...or more?  Unfortunately, some of us here may choose to or HAVE to move on a different graphics solution.  And of course those with NVIDIA solutions on Macbooks and iMacs are in an ever tougher spot. 

If a fix is truly something like 3+ months off, I think most of us would prefer to know now rather than living in false hope and venting with snarky messages on the Adobe forums, Creative Cow, etc.

Thanks,

-Eric

[dunbar2222]

I agree with eric0001 about waiting having false hope.  I've been having these issues since early this year.  And I can't deal with it anymore.

And going back to the early posts of this thread is even more depressing.

Seeing things like..

There's a fix coming!! 2 months later.... It's coming, we promise...here's our transcript/correspondence with the nvidia people.  2 months later the same promises.

I loved the CC package and was super excited to use it with my suped up iMac.  I know it's not Kevin's fault,  he's been on this for months and months now. 

But c'mon y'all are killing me on these deadlines that I'm trying to hit for clients.

Unfortunately.  You're about to lose me forever as I'm switching to Avid or back to Final cut.

This isn't a threat because I know Adobe has all the money in the world and it won't make a difference.

It's just disappointing considering how great premiere should be.  And all these little glitchy things make me want to toss my computer in the garbage bin.

-Nick

[RacerX2oo3]

Nick,

I wish that I could give an estimate or a timeline, however at this point with the existing variables corruntly being worked through, I don't think I can give an estimate or timeline at this time.  I understand the frustration when hardware and software don't work as expected, and it's our goal to provide the best expereince possile for our customers, as such resolving this issue continues to be a priority for us.  At the moment, my recommendation is to utilize OpenCL for Mercury Plackback Acceleration which appears to be the best option at the moment.

Sean  

[Judge Wolf]

FWIW/FYI ... I took my rMBP in to Apple and complained about this, and other power related issues.

In-store diagnostics showed everything was fine.

I insisted that my battery life was bad, and my machine would often simply halt (freeze) for no apparent reason, forcing me to force reboot.

So they sent it in to the 'repair center', and ended up replacing my logic board & battery.

Since then, I've been using full-on CUDA – with no problems ... and it's been nearly a week.

I don't know how this affects the presiding "it's a software only issue" theory...

[Nobilis_Bellator]

They replaced my mother board twice since June of last year all because we did not know at that time what was causing the issue. Next month I will be celebrating one full year of nightmares for more than six months and peace and quite and slow work but stable for about six months since I disabled CUDA....;-)

Let's  have a party in June...;-)

[And1]

Hey guys

I had a same problem like yours.

MacBook Pro 15 Retina Mid 2014.

I have REMOVED the CUDA DRIVER (CTRL+Click on CUDA icon in system system preferences)!

And the problem is gone))

NVIDIA please  do something...!

[ZachRosing]

Some new updates that may or may not be useful. When I switched to an iMac from a much older Mac Pro, H.264 editing got a decent amount laggy-er, and when having to do 4 streams of it in HD I finally gave up and started transcoding to the DNxHD MXF format to use proxy files. I've been using them for a huge two and a half hour long project, and the glitching on my system is *significantly* better. About the only thing I'm experiencing is occasional jittering frames in the multicam window (when it's paused it'll bounce back and forth between two frames--I have to switch out of multicam and back in to make it stop). But basically no screen glitching or garbage on my desktop.

I dont know if this really means anything in terms of tracking down the problem, but those who it's seriously affecting your workflow, you might try using proxy files.

[mike-pettyt]

Any update on this?  I've worked around the issue for a while now and resorted to removing CUDA and using OpenCL which does appear to have fixed the screen glitch problem but it would be great to have full GPU acceleration again!  I went for the top MacBook Pro with GT 750M towards the end of last year so I could edit 4K smoothly in Premiere Pro but I'm having to compromise which doesn't feel great after dropping the best part of £2000 on a laptop plus my monthly Adobe CC subscription...  (I'm willing to test beta CUDA drivers if anyone from Nvidia is out there?).  Also with the impending CC 2015 updates around the corner is there any sign of this problem for users on the pre-release program?  (if indeed you can divulge such details)

[Eric A Weiner]

Despair is starting to set in...

[Kevin-Monahan]

Hi Eric,

Despair is starting to set in...

Is switching to OpenCL mode not working for you?

Thanks,

Kevin

[Eric A Weiner]

Kind of.  I still get the problem in open GL, but not all the time, just sometimes.  Mostly when we made the move over to Premere not having to render everything was the biggest advantage, but the computer can't keep up in Open Gl mode so I'm back to rendering everything.  (My work involved lots and lots of alpha graphics in timeline.)

[Kevin-Monahan]

Sorry to hear that. I'm working quite well in OpenCL mode. What kind of GPU is it? Do you use a lot of GPU intensive effects?

Thanks,

Kevin