Inspiring

Question

PPro CC 2015-3 - GPU Render Error with nVidia GTX970

Forum|Forum|9 years ago
June 23, 2016
7 replies
11208 views

Having upgraded to cc 2015-3, my rig now is unable to render an upconverted set of sequences from the prior version. I consistently am getting an "Error compiling movie -- unable to process frame" dialog box. Something about the AE.ADBE Opacity effect, and I am using AfterEffects for an editable text titling motion graphic, which I have gone back to with the dynamic link manager and checked in AE, but it runs (RAM preview) fine. This was not ever a problem before the cc upgrade. My rig is a Win 10 64 machine with 32 GB DRAM and an 8 core Intel i7-5960, which has been plenty before. The nVidia driver is the latest. I can't afford to drop out of hardware acceleration mode, since this movie in software acceleration mode can take over 20 hours to render. I have repeatedly cleaned the media cache, as well as gone into the media cache on my scratch SSD and hand-deleted the two sets of cache files, as well as all preview files. Not a joyful experience. Any way to check the logs to find out what's going on and how to resolve the problem? Anyone else having this problem?

premiere_pro_2015_3

This topic has been closed for replies.

gavner25

Participating Frequently

Hi guys,

I actually have a solution for this for now (PC only). See link to my other post in a similar thread. Let me know how you get on. Click the link

Re: GPU Render Error | Nvidia GTX 1080 | Premiere Pro CC (2017)

M

Mike Atnip

Participating Frequently

Having very similar issue with nVidia Q2200. Can only edit the upconverted files if the GPU acceleration is turned off. If anyone has found a solution to this, please let me know. Render took 22 hours instead of 30 minutes, besides having to deal with not being able to preview and use the "program" panel. Without GPU acceleration I can only use 1/8 frames for 4k video.

I have a couple more older files that need edited, so would really like a solution. This started on two releases back, and now my older files are "locked" into using non acceleration. :-(

Windows 10 PremierePro 2017.0.1

Error log is (when acceleration is turned on):

Export Error

Error compiling movie.

GPU Render Error

Unable to process frame.

Writing with exporter: H.264

Writing to file: \\?\E:\Lancaster Heritage Center\Matt Raber\C0009_2.mp4

Writing file type: H264

Around timecode: 00;00;00;02

Rendering effect: AE.ADBE Lumetri

Rendering at offset: 0.000 seconds

Component: EffectFilter of type GPUVideoFilter

Selector: 9

Error code: -1609629695

Kevin J. Monahan Jr.

Legend

Hi mikeatnip,

You might try uninstalling and reinstalling GPU drivers. My Quadro card needed new drivers with the current version. Please try it and report back.

Thank you,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

M

Mike Atnip

Participating Frequently

Hi, thanks for the reply. I already tried that. Even installed a brand new card just to make sure it wasnt bad. I was reading (after posting) on another thread that Lumetri effects seem to be the culprit after the 2015.3 build. Not sure why some of my older files will open and convert to CC 2017 fine and others will not allow me to use GPU.

K

krluck

Inspiring

Just got this GPU Render Error. Unable to process frame.

Rendering effect: AE.ADBE Lumetri

In my case I'm also running a Win10 64bit machine with 32 GB RAM but using Intel i7-5820 and an nVidia Quadro M4000 GPU.

Running CC Premiere Pro / Media Encoder 2015.4 release

Is this problem likely to be solved by upgrading the nVidia driver?

Cheers, Kevin

B

BArticolAuthor

Inspiring

It appears that the Good Buddy patch, v10.4, which I tested on August 5, 2016, has resolved this problem.

Kevin J. Monahan Jr.

Legend

Tried this FAQ? FAQ: Why is my GPU not available for Mercury Playback Engine GPU acceleration?

Thanks,

Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

Zulkifar2

Participating Frequently

Hi everybody. I have a similar issue here on my machine. I have a AMD FirePro D700 6144 MB though.

I've done a bunch of Lower Third templates in AE and I'm trying to use them in Premiere.

They are expression driven and automatically adjust in height and width.

In After Effects they work like a charm, but in Premiere they are flickering in size (changing from the right size to a wrong one back and forth).

If I render from AE they look fine (Lossless with Alpha).

If I render from Premiere they don't.

Look forward to knowing why.

Bill Gehrke

Inspiring

BArticol wrote:
The nVidia driver is the latest.

If you have a driver 368.xx there is a problem with some media, I do not know if it will cure your problem but try to fall back to an earlier non-368 version.

B

BArticolAuthor

Inspiring

Thanks, but it didn't work. I dropped back from 368.39 to 365.19 (released in March 2016), cleared all cache files and previews, then tried to re-render. Same outcome. I may try reverting to cc2015-2 while Adobe gets the kinks out of this release.

Kevin J. Monahan Jr.

Legend

Hi BArtcol,

Sorry about this.

Thanks, but it didn't work. I dropped back from 368.39 to 365.19 (released in March 2016), cleared all cache files and previews, then tried to re-render. Same outcome.

Yes, you should be running 365.x drivers with that GPU so Bill had some pretty good advice there. Thanks, Bill.

The only thing I can suggest is to remove that Live Text Template. If it has expressions in it, it has been known to have major conflicts with this release. Roll back to the Premiere Pro CC 2015.2 (9.2) if you really need that text template.

Please let us know if removing the Live Text Template resolved your issue.

Thanks,
Kevin

Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded