A

Anonymous

Answered

GPU render error, unable to preces frame

Forum|Forum|7 years ago
August 18, 2018
11 replies
64417 views

You cannot afford my lost time.

GPU Render Error

Unable to process frame.

Writing with exporter: H.264

Writing to file: \\?\M:\TheVanishing001mp4.mp4

Writing file type: H264

Around timecode: 00;30;00;06 - 00;30;00;13

Rendering effect: AE.ADBE Lumetri

Rendering at offset: 1799.970 seconds

Component: EffectFilter of type GPUVideoFilter

Selector: 9

Error code: -1609629695

I have turned OFF render at maximum quality... which alone seems like I am overpaying for software that doesn't work. I just lost all that time as I have a file that is worthless. This is completely random. Sometimes, no problem renders fine..other times I get the above error. Yes, I am on the latest nVidia drivers. They were clean installed and do not have issues. I am completely frustrated at this point!

[title edited by mod for better search]

Correct answer

Thanks for the suggestions fellas...but I have to ask... WHY?? I am doing nothing that I wasn't doing before this god awful bug. By the way, I have discovered, turning off the layers Opacity Keyframing fixes this problem. This is a bug..Adobe knows it. PR right now is crippled. I am paying full price for crippled software. I am most certainly not changing my workflow. I built this beast of a system so that my creative flow is not hindered by hardware or software and right now software is being a PITA!

A

angie29195561v0qx

Participant

I deleted the previews -- and then re-rendered in a new sequence. This seemed to do the trick.

A

Aiden Ross

Participant

RESOLVED - Turns out this error was caused by the AUTO CAPTIONS from Premiere

so the simple solution I did is upgrade the captions as graphics and VIOLA. You're welcome!

G

Girish2627683795wv

Participant

GPU Render Error

Error code: -1609629695

Please solve this problem

R Neil Haugen

Legend

Most GPU render issues need to be solved by changes on the local system. But as you haven't given any data whatsoever, I can't even begin to guess what needs doing.

Data please, that is always needed for troubleshooting. OS/CPU/RAM/GPU, the GPU driver, and the media and effects at a minimum for this.

Everyone's mileage always varies ...

J

Jill37545447eypt

Participant

AND IF NOTHING ELSE WORKS...

I tried everything. I work on a Macbook Pro M3 Max and was never able to get the "Mercury Playback Engine GPU" thing to not be grayed out. I looked at numerous YouTube videos on how to resolve this. The only thing that worked for me was to just delete the clips that weren't rendering, replace them with the same footage, apply my Warp effect again and then render each clip after I got done applying the filter (while holding my breath), and then it all worked.

H

heringji

Participating Frequently

Hey everyone, I watched this guy's solution video and the very first option worked: Simply close Premiere and then open it again. All the clips that weren't rendering before finally rendered. https://www.youtube.com/watch?v=bDU6XHcfBic

Had been trying for an hour to do all these other options in this thread, everything failing, and then found this video.

H

heringji

Participating Frequently

I should say: Simply "quit" Premiere and then reopen it. 🙂

R

RO2.0

Participant

I was wondering if you happened to find a fix. I'm getting the same error and it seems to always happen between Opacity Key Frames.

R Neil Haugen

Legend

Please file over on the UserVoice system that you're having this. I've created the bug report linking to this thread, but PLEASE! ... both of you (and any others!) ... go there and add your comments to my posting.

gpu render error "unable to process frames" linked to opacitiy keyframe being "on" – Adobe video & audio apps

That is the way in the Adobe system to get the data directly to the QC engineer's systems. If they don't see it, they don't know about it.

Neil

Everyone's mileage always varies ...

C

Carlos Ziade

Community Expert

To add to what Neil said, that which I agree 100%, you should have informed us

if you have tried our suggestions to delete the render files or video previews associated

to your project. When projects rendered on previous versions are rendered again on newer

versions, sometimes an abnormal overlapping of the video previews might occur especially

when you have effects like Lumetri, so, simply deleting the render files and then cleaning

your media cache is something that should be done and become your habit as always this

is a necessary step not only with Premiere Pro. When you turned off 'Opacity' keyframing

and that I guess was done on the layer that has the Lumetri, that layer's render previews

were not being rendered again, no more of use. I guess if you deleted all the render files and

media cache and tried again even with those opacity keyframes on, your problem might have been solved.

A

Anonymous

This was a brand new project. And the media cache is generally dumped before I start anything new...and it was this time. So no, it wouldn't have worked. Thanks for the help, to others. All I know is that they better get it fixed. I am tired of public forced betas. That needs to be done on an non-production stream by volunteers. No where in my Adobe contract does it say that I agree to TEST software. Also, the salt tossed around by community "pros" here is appalling. Great image for the company.

Adam Cinelioglu

Participant

2 years late, but I agree with the last statement. Every time I check these forums for people having similar issues to myself, replies from the "pros" are almost never without an arsey, condescending, salty demeanour. Why cant people just leave that attitude at the door and actually HELP withOUT the snarky replies?

Its 2020 now and Premiere Pro has been doing the same thing to me on my last few projects.

Everything rudely suggested here I have tried, yet I too seem to have this recurring problem.

So it would seem 2 years on, Adobe still haven't bothered to address this issue.

Will probably move to Da Vinci at some point. As daunting as it is to learn a new software.

A

Anonymous

Correct answer

Thanks for the suggestions fellas...but I have to ask... WHY?? I am doing nothing that I wasn't doing before this god awful bug. By the way, I have discovered, turning off the layers Opacity Keyframing fixes this problem. This is a bug..Adobe knows it. PR right now is crippled. I am paying full price for crippled software. I am most certainly not changing my workflow. I built this beast of a system so that my creative flow is not hindered by hardware or software and right now software is being a PITA!

R Neil Haugen

Legend

First, by your comments, you don't understand a number of things about this app. Which is normal, how many do?

So ... Max Render Quality is only of use in certain limited situations, such as major resizing involving a lot of diagonal lines. Other than that, it's not of use. And can at times cause artifacts, so the better advice is that's off most of the time. Same for Max Depth, especially if you've got a dedicated decent GPU. 2-pass renders for exports mostly just take up extra time, without any appreciable improvement to the export. Except ... it can help in a very few sequences.

Not having them on is NOT 'missing' anything of use with the app. Period.

Apparently, you're one of the few that has the issue of opacity keyframing a clip or adjustment layer causes a problem? If so, yes, any software has some bugs ... some things that don't work right on some gear and media combinations, that sort of thing. I can't replicate, as it's working normally on my Win10 rig.

I do understand and appreciate the angst. Like most anyone using a complex hardware-demanding app like this for 5 years or so, I've been hammered at some point also. Around four months one time, requiring I stay with an earlier version until the appropriate bug fix had been released.

Also, if there's some glitch in the media cache files, you can have this sort of Lumetri fail message. I do get them but pretty rarely ... and always dump the media cache and check the timeline at the time-code spot. And am exporting in a couple minutes.

Neil

Everyone's mileage always varies ...

juanmario

Participating Frequently

In the project settings, change GPU acceleration to Solo Software.

P

patrycja34511991holf

Participant

worked for me, thanks!

C

Carlos Ziade

Community Expert

You have a problem in rendering Lumetri effects applied, try removing them,

or if you still want the Lumetri, try to delete the render files by going to sequence - delete render files

or manually delete the video previews from outside of Premiere. Then clean your Media Cache.

If after doing all of the above the problem persists, try nesting the clips on which you have Lumetri

after removing the Lumetri Effect, then reapply Lumetri to the nested. Check if that works as well ...

N

Nicole5EB9

Participant

Just wanted to pop on here over 3 years after you gave this suggestion and say I'm using Premiere for the first time to quickly put together a slide show of images for a funeral and was running into this issue. Your suggestion to delete the render files has seemed to solve my problem. Hat tip to you, sir.

C

Carlos Ziade

Community Expert

great! tx for letting us know!

Show more replies

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