Gpu processing on the current clip failed because of an error davinci

Hey,

I just had the same problem and found a really simple solution. Maybe it works for someone else too

I just picked all clips on the timeline and moved them some seconds backwards, then I placed the render in/out range at the corners and started rendering. worked fantastically, no idea why

OnTheRopes wrote:

Lirlox123 wrote:Hey everyone, try going to preferences>user>UI> UN-CHECK «stop renders when a frame or clip cannot be processed» that worked for me.

Hope it helps

Upgraded to 16.1.2 Studio today, I always tend to delay upgrading but thought it was perhaps okay by now.
I had this exact Render issue, but your solution has worked, cheers. Just a shame BMD can’t be bothered to comment on it.

Great! This fixed it for me. Have 16.2.0.055. Built my first Fusion composite for particle dissolving a title. Couldn’t render. Tried another solution from this forum which didn’t do the trick. Happy about this one . However, this issue should be addressed by the developers. It’s like Windoze in the nineties — crashed if you touched the keyboard! Not a suitable tool for production.

Just started receiving same RENDER JOB FAILED condition on a segment containing a cross dissolve of 2 1080 segments that each have grading and sharpening.

Dropping render speed didn’t help. Neither did relaunching app nor rebooting workstation. Disabling «stop render when clip…» stops the RENDER JOB FAIL message, but now GPU MEMORY IS FULL keeps popping up. The render will finish but the rendered segment is unusable due to repeated and missing frames.

So thinking my root cause of the RENDER FAIL is full GPU memory?

Supporting this theory is that if either the cross dissolve, grading or sharpening are removed, the segment renders fine. All 3 consistently create the GPU MEMORY FULL message, but only during rendering or when played in the DELIVER page. Error message does not display when playing in the EDIT page. Re-rendering cache of the segment then trying to render segment didn’t help.

When playing in DELIVER, GPU memory usage shows it’s running between 85% and 90%. GPU MEMORY IS FULL message occurs when GPU memory usage spikes much over 90%.

GPU processing is set to CUDA manual pointing to GTX 1070. Running the latest NVIDIA Studio drivers.

System:

Win10 Home
GTX 1070 8GB running Studio Driver V442.19
DR Studio 16.2.0.055

Any more hunches?

Update: original issue reported as RENDER JOB FAILED. Disabling «stop renders when a frame or clip cannot be processed» stops the RENDER JOB FAIL message and completes the render. But GPU MEMORY IS FULL error messages now surface during render and the rendered product is corrupt.

I isolated it to a 3 second segment where 2 1080P clips are cross dissolved. Each clip has equally applied grading and sharpening applied via COLOR page nodes. Sharpening used a shared node. No other effects applied.

The GPU MEMORY IS FULL error started on the DELIVER page then appeared on the EDIT and COLOR pages as well. Monitoring the GPU the memory was peaking around 95%.

Here’s what didn’t fix the problem:

— rebooting DR or the workstation
— reloading latest 1070 Studio drivers
— changing GPU processing mode to CUDA
— changing proxy mode to 1/4 resolution
— changing render speed
— pre-rendering the clips to cache
— removing the color grading or the dissolve
— yelling at the screen
— kicking the workstation

Here’s what fixed the problem:

— deleting the SHARED NODE used for sharpening to a separate node dedicated to sharpening for each clip.

This conversion from a SHARED NODE to non-shared dropped GPU memory consumption from ~95% to a more manageable 60% — all with the desired end result. Now everything renders fine.

Why would this happen? Would like to think my i7 32GB Win10 GTX 1070 8GB DR Studio config would be more than enough horsepower for this simple composition.

Hope this helps others with their own troubleshooting.

@Paul. We can’t reproduce the memory issue.

Can you send us the simplest project export .drp that causes the issue on your system? Along with a Resolve diagnostics log captured while the issue is happening?

Thanks!

*FIXED*

Hey guys, multiple threads talking about the same issue, be good if we could merge them all.

I tried a few things….

Tried the video workaround someone posted (new project etc etc). This didn’t work for me.

I had NOT tried «Stop renders if a frame fails» option (I thought I had but I just checked and it was on).

But I did notice on the render when it failed, on a Text+ clip, so I removed it, copied the exact same clip from another timeline which also used it, pasted and it rendered fine.

I use like a «master template» timeline as a base for my movies. So they all begin, end the same with sam lower thirds etc. Never had this issue after maybe 30 different renders.

Then all of a sudden I had this issue. No idea what it is, but if you only have one timeline that’s failing, try to see where it stops. I noticed a big black screen on half the render which I could tell was the Text+ clip.

Hope this helps some of you.

Lirlox123 wrote:Hey everyone, try going to preferences>user>UI> UN-CHECK «stop renders when a frame or clip cannot be processed» that worked for me.

Or check this video:

Hope it helps

This helped! Also, I just updated to 16.2.2, good so far

I was having the same problem. It started after I added a temporal noise reduction node to one of my clips in the color screen. When I disabled the noise reduction node, the issue disappeared. This only happens when I set the «Frames» dropdown to something other than zero. The spatial noise reduction settings don’t seem to affect the issue.

Windows 10
Threadripper 1950x
GTX 1070 Ti
Resolve 16.2.2.011

Don’t approach DR with your preconceptions from another NLE.
Many features are better, some worse, most are different.

Resolve Studio 18.1.2, MacOS 12.6.2
MacBook M1 Pro, 16 GPU cores, 32 GB RAM
and
iMac 2017, Radeon 580, 32 GB RAM
Speed Editor

I had the same issue.

Neither Preferences>User>UI> Uncheck «stop renders when a frame or clip cannot be processed» nor instructions from the youtube video someone shared above worked for me.

Than, I realize I didn’t have enough space on the disk. Created enough space on the export destination and it worked fine.

Mike_Molgart wrote:

OnTheRopes wrote:

Lirlox123 wrote:Hey everyone, try going to preferences>user>UI> UN-CHECK «stop renders when a frame or clip cannot be processed» that worked for me.

Hope it helps

Upgraded to 16.1.2 Studio today, I always tend to delay upgrading but thought it was perhaps okay by now.
I had this exact Render issue, but your solution has worked, cheers. Just a shame BMD can’t be bothered to comment on it.

Great! This fixed it for me. Have 16.2.0.055. Built my first Fusion composite for particle dissolving a title. Couldn’t render. Tried another solution from this forum which didn’t do the trick. Happy about this one . However, this issue should be addressed by the developers. It’s like Windoze in the nineties — crashed if you touched the keyboard! Not a suitable tool for production.

This fixed my render issue as well, and we were able to keep rendering! I think there was a glitch in the original clip file, that a number of frames were missing, because there were a couple of words missing in the speaking. That tripped up the render process, but when I unchecked that box, I was able to render it anyway, even with the missing frames.

Affinity Harmonics wrote:I was able to render my video after 3 hours of trying to figure out what was wrong… It looked to be where ever the render crashed, is where I included a «Freeze Frame» clip. After I going back and removing them, I was able to render my video. Hope that helps anyone else stuck!

I was running into the same issue and noted the following: The issue was because I used a freeze frame at the very end of a media — and then extended the clip further to the right (where there was actually no media any more, but Davinci allowed to do so in the first place). But this was where the rendering stopped.

After replacing the freeze frame which was extended beyond the end of the media by a freeze frame extended only backwards to the left (i.e. within the actual media) immediately resolved the problem and the material could rendered without issues.

Thought I’d add my experience with this issue to the list. I have an older computer, specs below, and I get the error: «Render job 1 failed as the current clip could not be processed. GPU processing on the current clip failed because of an error.» when I output my project to a file.

I tried various fixes found in this forum, but the one that worked for me was going to Preferences -> Memory and GPU -> GPU Configuration -> GPU processing mode, set it to «Auto» and then un-check the «use gpu scopes.»

I can recreate my issue 100% of the time with a simple project with a single video+audio on the timeline. Then, add a 2nd track, where I bring in a jpg file that will show up over the video, for say 10 seconds. When the rendering gets to this jpg file it stops and fails rendering.

My computer specs:
Windows 10 v2004 (OS build 19041.630)
DR 16.2.7.010
Intel i7-3770 3.4 GHz
16 GB Ram
NVIDIA GeForce GTX 555
NVIDIA driver v391.35
Samsung 860 EVO SSD 2TB hard drive (plenty of free space)

Would it be possible to have specific error codes?

My first ever edit was a trim at both ends and rendered successfully. My second was eight clips selected from a single source clip. I’ve been trying all day to get this to render but I keep getting the Render job failed — clip could not be processed. Even with the ‘stop on render’ turned off in preferences.

I would like to learn Resolve rather than keep using Premiere. However I’m unable to learn from such general errors that mean nothing. Even after spending all day trying to resolve them using every suggestion I have found. I’m now terrified of using Resolve for an actual job. This problem could end me.

I have to jump on the train as well.
None of the above mentioned solutions worked for me.

The footage is 360 degree 5.7k Apple prores 422. I tried different fusion scripts :
(transfor, shape 3d, merge 3d, camera 3d und render 3d, as well as viewer equirectangular)

I hope there is a solution to this problem.
Best regards
Albrecht

Just had this very issue. One of the dozen clips I imported from my iPhone XS caused this ‘render fail’ at the end of one clip. The clip would play just fine in the editor and transition. But the ‘render’ failed at the end every time. I took a second or so off the end of the reported problem clip, and restarted the render.
Things went perfectly fine then.

So my best guess is at least in my case, the Apple produced .mov files had one of them that wasn’t quite clean and compatible with Resolve.

For reference purposes, I was rendering to 1920x1080P 30fps H.265 Quicktime with Linear PCM stereo audio destined for YouTube.
Resolve 16.2.6.005

The source clip was

Format : MPEG-4
Format profile : QuickTime
Codec ID : qt 0000.00 (qt )
File size : 165 MiB
Duration : 18 s 432 ms
Overall bit rate : 75.0 Mb/s
Encoded date : UTC 2020-12-24 06:39:03
Tagged date : UTC 2020-12-24 06:39:21
Writing library : Apple QuickTime
com.apple.quicktime.location.ISO6709 : +47.6270-122.0433/
com.apple.quicktime.publisher : ISO: 965.16925
com.apple.quicktime.software : Created with FiLMiC Pro 6.12.9 build 16197

Thomas

—
Amateur w/ occasional professional product producing aspirations

ThomasSmailus wrote:So my best guess is at least in my case, the Apple produced .mov files had one of them that wasn’t quite clean and compatible with Resolve.

Not only Apple, most smartphones record video with variable frame rates (even with FiLMiC Pro), which can cause trouble in Resolve. More primitive editing software can normally handle that.

Don’t approach DR with your preconceptions from another NLE.
Many features are better, some worse, most are different.

Resolve Studio 18.1.2, MacOS 12.6.2
MacBook M1 Pro, 16 GPU cores, 32 GB RAM
and
iMac 2017, Radeon 580, 32 GB RAM
Speed Editor

I have this issue on 17.1 beta

I am not using fusion or dehaze. The only thing I’m using is color correction and retime. No freeze frames. I tried replacing all of the clips from source. No luck.

The strange thing is, the project renders just fine in quicktime format. It won’t render .mp4

Original source is .mov

I also have this on 17.1.1 Build 9 (and had this in the past, very frustrating)

This workaround did work for me:
youtube video: 6eflSIgrkz8 (I’m not allowed to post urls on this forum…)
Basically in playback menu: Render cache on smart, and Fusion memory cache on.
Then in deliver page on advanced settings, check Use render cached images.

The strange thing, after the workaround has worked, and I disable the workaround, it works again as expected.

nspusmc wrote:The strange thing is, the project renders just fine in quicktime format. It won’t render .mp4

Which codec are you using in the MOV container? My observation is that hardware accelerated renders into H.264/265 can stress a GPU and that it works better if you first render a master in a mezzanine format.

Don’t approach DR with your preconceptions from another NLE.
Many features are better, some worse, most are different.

Resolve Studio 18.1.2, MacOS 12.6.2
MacBook M1 Pro, 16 GPU cores, 32 GB RAM
and
iMac 2017, Radeon 580, 32 GB RAM
Speed Editor

I started getting this error today on timelines I have been exporting just fine. I tried all of the mentioned workarounds in this thread.

What ended up working for me was choosing a different codec on export. I had it set to DNxHR HQ then switched to DNxHR HQX 10-bit and everything went back to working great.

I am on a PC using Resolve Studio version 17.2.2 Build 4.

Don’t approach DR with your preconceptions from another NLE.
Many features are better, some worse, most are different.

Resolve Studio 18.1.2, MacOS 12.6.2
MacBook M1 Pro, 16 GPU cores, 32 GB RAM
and
iMac 2017, Radeon 580, 32 GB RAM
Speed Editor

Don’t approach DR with your preconceptions from another NLE.
Many features are better, some worse, most are different.

Resolve Studio 18.1.2, MacOS 12.6.2
MacBook M1 Pro, 16 GPU cores, 32 GB RAM
and
iMac 2017, Radeon 580, 32 GB RAM
Speed Editor

Binsfeld wrote:The fusion clip is rendered when I use the «render cache». Then if I check «use rendered media» my job goes through.

So I just had this problem in 18 but the solution this person posted worked oppositely for me. I kept erroring every time I had «use render cached images» turned on. I turned it off, and the clip rendered.

saronbrandao wrote:I had this same problem while rendering an animation that contained scripts. I was able to watch that on the viewer, but couldn’t render. My solution was pretty simple, I set my cached files to high quality and then I got back to fusion tab, right clicked the mediaout node and chose «cache to disk«, then I played the animation once till it is cached and once I was back to the deliver page, down in the video options, I selected advanced settings/ use render cached images. Then, send it to render again and the problem was gone I think it works every time your are in a situation which you can playback your clips but cant render them. I hope it helps.

Oh my gosh! Thank you so much!
This worked. Had been banging my head over this for more than a day.