Skip to main content
Participating Frequently
June 19, 2017
Question

GPU/Lumetri Render Export Error

  • June 19, 2017
  • 16 replies
  • 11123 views

So this is somewhat of a discussion and a question. Recently I was having the issue of getting the Lumetri error upon export. I viewed tons of videos and looked in forums and people were having similar issues. I gave up after not being able to fix the issue and called in for help. I was advised that it was an update version issue and that I would have to reapply all the settings. That somewhat made sense to me until I asked my partner if they had updated their CC version. (We were sharing an external hard drive) Everything was updated. I read in one of the other Adobe discussions that someone was told as well to reapply all the settings, and I agreed with them that it was a pain in the butt to do and there had to be another way. I tried a new project, new sequences, copy and paste, encoder, updated graphics card, checked and changed suggested settings, and other things, nothing worked! Needless to say, I did just that and reapplied everything. TIME CON-SUM-ING. 

Here's where I want to know if others have experienced this. After reapplying everything on a new sequence, it exported just fine. A couple of days later, I went to unplug the drive and use it elsewhere. BAM, when I come back to my computer and plugged it in to start working again the same damn export error evolves.

Now everything was saved correctly, worked when I reopened the application, no issues until I unplugged and re-plugged in the drive (into the same port).

I'm glad I exported like crazy before and had my back ups as I was not going to redo that whole process again. My partner suggested I post this, so here I am.

Does anyone know if this is truly an update issue on Adobe's behalf or something that I don't know I shouldn't be doing? (I use Avid as well and never had an issue like this, I'm also getting reacquainted with premiere pro)

This topic has been closed for replies.

16 replies

Participant
June 20, 2020

HERE I AM, 2020 WITH THE SAMEEE PROBLEMM, my notebook is really good, my premiere is the latest version, and this problem happen with the luma effect and lumetric, buuuut in other projects i worked with this effects and was succefull. I cant understand why it happens. please someone HELP ME

R Neil Haugen
Legend
June 20, 2020

This type of issue can be a number of things, including drive access read/write permissions from the OS. Both Mac and PC OS have been doing fun things to reset program/user access to different folders and files recently. So that's one thing to check.

 

Neil

Everyone's mileage always varies ...
Participant
June 20, 2020

its not this, I checked, its something with the GPU and the  filters, cause a I used the mercuriy to render the preview and worked, but appear the message "this effect need gpu" in the frames, after that I exported using the preview(do you know?!) but the message was exported together, and when I try to export the video whitout them preview using the CUDA or Mercury it dont work

Participant
July 22, 2018

I had this same problem and just fixed it. My whole project had already been color corrected and graded with Lumetri, and I shot on program settings so it wasn't an option to just turn that off and lose all color in my frames.

Only a few clips had Lumetri rendering errors for me. Turns out, I had accidentally turned on the LUT under the "basic correction" tab instead of the "creative" tab in Lumetri. As soon as I fixed that, vwa-lah! It exported just fine.

Participant
March 6, 2018

EDIT: I thought a fresh windows install to version 1703 has this issue licked but it has intermittently reared it ugly head again and is still crashing with Lumetri effects. Adobe what is the solution here?

So I have been having this render error like the reset of you for a while now.

Asus Z97-A motherboard

Intel(R) Core(TM) i7-4770K CPU @ 3.50GHz, 3501 Mhz, 4 Core(s), 8 Logical Processor(s)

32GB of ram

Nvidia 1060 GPU

Multiple ssd's for OS and scratch and raid for storage.

The render errors are random on the timeline and it may render almost all the way then crashes. If I remove certain effects it still crashes

I have tested almost every Nvidia driver, same issues

Created a new project and imported the sequence, same issues.

I have created a new sequence and pasted the clips in that one, same issues.

I have taken the Windows 10 Fall Creators update so reinstalled Windows 10 fresh to version 1703 with the windows Nvidia drivers of 388.13 and it works with the exact same project. I think that the newest windows 10 version 1709 with my combination of mother board and GPU was causing me these issues. I have rendered this 6 minute project out 10 times without modifying anything on the timeline and it just works. Now to find out how to stop Microsoft from pushing 1709 into my machine....

Thanks

Known Participant
October 22, 2017

This is the only way I fix this issue for sure.

I put all the effects, cuts, etc on my footage on the timeline that I need, leaving Color-correcting/grade for last

I render to an uncompressed (or HQ) codec, like [DNxHR/DNxHD MXF OP1a, DNX HQ 1080p... preset] or  [Quicktime] and select the Video Codec [NxHR/DNxHD] with a resolution of [DNxHR HQ 8-bit or 10-bit] and seelect Uncompressed (this is to avoid Lossy compression as much as possible)

I import that rendered file into my project, drop Lumetri on it. After adjusting as needed, it renders with no problem.

The reason I like to do Quicktime instead of the straight DNxHR/DNxHD MXF OP1a is I've found when I want to do tracking in After Effects, Moca won't recognize that or many other files rendered with other codecs.

Painful workflow, I know, but it gets the job done.

Known Participant
October 22, 2017

Also, I find this problem happens to me when I use Ultra Key AND Lumetri.

I don't recall having this problem with just Lumetri nor with just Ultra Key individually.

Also, I notice it happens to fail the render on a cut... not always the first one.

R Neil Haugen
Legend
October 22, 2017

Great information there, thanks for posting!

Neil

Everyone's mileage always varies ...
gavner25
Participating Frequently
September 10, 2017

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)

dutchy_on_a_bike
Known Participant
August 23, 2017

As I mentioned a week or 2 ago, I was having all sorts of Lumetri/CUDA problems. I have now replaced my GTX 680 with a GTX 980 4GB from MacVidCards. ALL the errors have stopped. My old 2012 MacPro 5,1 can now handle 4k with Lumetri with only a few dropped frames and no crashes. It is like a new computer. I have a feeling the GTX 680 just did not have enough power for Lumetri with either HD or 4k vision. Mark

Legend
July 30, 2017

I experienced this problem long ago, mostly on dated hardware... but once 9 months ago on not-so-old-hardware, not since. I don't have any magic answers except the general things I've performed to get around this.

Your issue seems to relate to a deterministic export failure, meaning the same failure happens at around the same time regardless of whether you reboot your system or whatever. So I won't say the obvious things.

Generally, when I export from AME, I ensure all other Adobe apps are closed. That means not leaving Premiere or AE open during export. This was especially important, it seemed, on my older hardware because it seemed there was a low-level CUDA out-of-memory error occurring at the point of failure (I observed this with NVIDIA tools), which seemed to indicate that when the Lumetri effect and related modules receive such a CUDA failure, they don't pause or wait or try again, but bubble a failure up which aborts export. I'm being a little assumptive here because I don't have access to source code and can only infer things... but in short this seemed to indicate I didn't want other apps running and stressing GPU resources during AME export. Same for Pr export... exit AME and AE and other apps. In short, make sure competing GPU-using apps aren't running. Note the observations of this paragraph occurred a release or two ago so I cannot say the same workaround would apply today. Take this paragraph as abstract info toward just saying keep other GPU-using apps closed while exporting, especially on older/lesser hardware.

I never did this, but I heard transcoding to an intermediate like DNxHD, CineForm, or ProRes can help effects processing, possibly helping to avoid this error, especially on older hardware.

Since it seems like you've tried a lot of things, the only other thing I can say (abstractly as well) ... you mention "reapply all the settings" ... do you mean scouring the timeline, deleting existing Lumetri effects (created with the old version of Pr), and reapplying them? If so, did you delete the effects, and use a preset to reapply, or did you drag a fresh Lumetri from the current version of Pr's effects panel? if the former, you might consider the latter...

What i'm getting at is I've seen Presets persist Pr-version-specific "things" which seemed to negatively affect my experience in this area in one particular case, where I could, in a deterministic manner, apply a preset Lumetri and where it had persisted characteristics affecting the lumetri stack during export so as to hit this error. This led to another workaround for me which was to re-apply fresh non-preset Lumetri effects from the current version of Premiere to override older versions of the persisted effect... persisted with the project in a prior version of Premiere... which were seemingly causing problems by affecting the lumetri processing/stack so as to cause export failure. Meaning... I used an older Premiere, had timeline, applied Lumetri then, saved project, upgraded Premiere, opened that old project, and the Lumetri effects persisted with that older project (saved with the older Premiere) caused the newer Premiere to exhibit the lum export failure. So I replaced all of them with fresh lumetris not fromm older presets. To speed this up, you could apply fresh lumetri effects, copy/paste numeric settings (the numbers, not the persisted effect/preset) from the old to new lum, and create a new preset using that version's lumetri... then use that new preset. The whole point here...

Presets are nothing but files or persisted data that is used by the effects stack... it's not like they are bad or good in and of themselves... they contain values and it appears to me that the structure or nature of what is persisted can change from version to version... those values affect how software code is executed in the effects stack which means that a preset from one version of Pr can cause a later version to behave differently or execute code differently. As well, I view any effect stored within a clip or any entity within a project to a form of "preset" meaning it's a persisted form of data that shapes how effect processing occurs. I am suspicious that how a past version of Pr persists such data may end up not being as optimum in a later version of Pr compared to re-establishing the effect starting from that then current version of Pr. Generally that should not be required, but it seems to have mattered in at least one case I hit... so I expect this to be more rare, but worth keeping in mind. The team is supposed to ensure past persisted data is forward compatible when they upgrade... but there are so many variables that it's impossible to catch every possible issue. Savvy users must be vigilant with their own persisted data and how it behaves in later versions that read and use that data.

I can only speak in abstracts here but I'm just saying that when I hear of an older project's persisted lumetri's are in play and there are lumetri export failures, it causes me to want to share the above abstract info... it's all just a hint that you might consider re-establishing fresh lumetri's completely disconnected from any past persisted data (i.e.,avoid past version presets and copy/pasted or importing from data persisted with past version... drag/drag lum from effects panel for fresh start... copy/paste numeric values is fine because those don't carry over internal config values... creating new presets in the current version of pr is also fine as it's all persisted with the version you presently using... the point being to try to distance yourself from data persisted in older version in areas where you specifically are seeing issues... painful but possibly a workaround).

Maybe you did all that... if so, forgive! ... but ... sorry to hear you're having issues... the above is my try to help 'cuz as others say, I feel the pain...

It's verbose but I feel your pain and the above is the best I can offer... maybe Adobe has some concrete steps nowadays but dealing with this error is sort of like whack-a-mole. If you have older hardware, you might consider an upgrade if feasible. I've had nary an issue with my newer hardware.

R Neil Haugen
Legend
July 30, 2017

NIcely put ... very nicely put!

One thing that can occasionally work when bringing "old" version presets into a new version: apply that old preset without any other changes in Lumetri on a clip in the new version, and then go to the top of the Lumetri tab, and "Save as preset" in that new version. That has for some brought 'old' presets that were problematic into a usable state.

Another thing to try is to take a problematic preset, and do a "Save as .cube", then simply apply that LUT either in the Input slot in the Basic tab or probably the Creative tab's Look slot.

Neil

Everyone's mileage always varies ...
Legend
July 30, 2017

https://forums.adobe.com/people/R+Neil+Haugen  wrote

...One thing that can occasionally work when bringing "old" version presets into a new version: apply that old preset without any other changes in Lumetri on a clip in the new version, and then go to the top of the Lumetri tab, and "Save as preset" in that new version. That has for some brought 'old' presets that were problematic into a usable state. ... Another thing to try is to take a problematic preset, and do a "Save as .cube", then simply apply that LUT either in the Input slot in the Basic tab or probably the Creative tab's Look slot.

Neil

Good to know!

Rameez_Khan
Legend
July 6, 2017

Hi everyone,

Sorry for the delayed response!

Do you mind going through the troubleshooting steps provided in this article? How to fix issues that cause errors when rendering or exporting

It can be really helpful. This issue can be caused due to "n" number of reasons and everybody's solution may differ.

Let us know what you find out.

Rameez

Julian Cortizo
Participant
July 30, 2017

I have this issue for over an year, and I read avery post with so many people with the same problem, is so frustrating. Turning of CUDA for rendering is so much slower. And besides the problem is arbitrary, in some projects or sequences it happens in others not.

We need a solution!

My system:

Intel i7 6700

Mother Asus Z170-A

EVGA Geforce 960 (Driver: 384.94 up to date)

Windows 10

Premiere CC2017 (up to date)

Thanks!!

Encoding Time: 00:07:46

07/29/2017 09:19:41 PM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

GPU Render Error

Unable to process frame.

Writing with exporter: QuickTime

Writing to file: D:\blabla/blabla/blabla.mov

Around timecode: 00:03:07:11

Rendering effect: AE.ADBE Lumetri

Rendering at offset: 187,167 seconds

Component: EffectFilter of type GPUVideoFilter

Selector: 9

Error code: -1609629695

R Neil Haugen
Legend
July 30, 2017

There can be all sorts of reasons why you are getting this. So it isn't "a" solution ... there are some things that might be set better in the code, but a lot of the issues are dependent upon the hardware of certain users.

Neil

Everyone's mileage always varies ...
Zoe7traveller
Inspiring
July 6, 2017

I'm having the exact same issue.  I dunno, I guess I decided it was a GPU memory issue or something (just guessing out of desperation and ignorance).  This happens when I try to use Lumetri  to render at over 2k.  If I render video below 2k, it seems to magically work.  I'm not on the most robust system for video -- it's a Surface Pro 3, I7 with 8gb ram......but it does the job for most small projects.

I see people have been having this issue for months.  I've been reading a bit and can't seem to find a work around either.    

R Neil Haugen
Legend
July 6, 2017

Lumetri is a heavy-resource effect, and that Surface with only 8Gb of RAM is barely able to work the program ... start adding in large frame-sizes/rates and especially go to the long-GOP mov/H.264/5 formats of most non-pro video cams and you stress it out a lot more with 4k.

For editing, use of small Cineform (NOT H.264!) proxies works fairly well. For "small", think editing work not file-size on disc. Full intraframe codecs like Cineform, DNxHD/R, and ProRes are bigger on disc but require far less of the CPU/RAM system than most mov and H.264 produced by DSLR's, mirrorless, and drones.

For renders/exports ... it's that original media that's in use, so yea ... that just needs horsepower.

Neil

Everyone's mileage always varies ...
Zoe7traveller
Inspiring
July 6, 2017

I admit I don't fully understand some of what you said.  I guess I just assumed that Lumetri should work (as well as any other color correction I might add), but that it just might work more slowly.  I have heard (but have not yet tested) that I can switch from gpu to software for rendering.  Maybe that's worth a try.

Participating Frequently
July 6, 2017

RameezKhan​ I just saw your other question was for another user. so you can disregard my yes and no comment. lol