GPU Memory Full ?

Get answers to your questions about color grading, editing and finishing with DaVinci Resolve.
  • Author
  • Message
Offline

wireless112

  • Posts: 139
  • Joined: Sat Apr 21, 2018 8:23 pm
  • Real Name: Jeremy Johnson

GPU Memory Full ?

PostSun Apr 29, 2018 4:17 pm

So I searched and found a post on this topic, resulting replies all blamed the issue on the size of the project.

In my case it's something else-

I've bounced between a number of NLE's over the last 6 weeks for a project that I made the mistake of borrowing a P2 camera for. I had my complete project Stills, Trims, Multicam, even a chessy effect, finished in Vegas Pro 15. But it refused to render the P2 footage. So I figured my CPU was old and could use improvement as my Mobo was also experiencing USB issues. Anyway updated to the specs in my signature. Still no render. Checked them all out. Settled on Resolve. I love how the manual tells you everything and is well written.

I got my project all trimmed, denoised, and color corrected in resolve 15b1. When it came time to do the multicam, that's when it all fell apart. After much experimentation with proxies and what not, Resolve could get to about 48fps which would have been workable. But the audio was also choppy, that was too annoying to deal with. 15b2 came out and I upgraded, no improvement. So I subscribed to Premiere as my trial had run out. Got the multicam completed and rendered out to DNxHD HQX. I pulled the single 1080P 60 file into the media pool. I then added a single JPEG to the media pool and got GPU Memory Full. It's not even on the timeline. Just in the pool. So I hit OK. Added the video to the timeline. Then added the still to the timeline. The preview window would not display the still. The images on the track with the the still were images from the other track which had the video.

Went back to Premiere and finished the still work. Didn't like how Premieres rolling credit's work and am back in Resolve. Good thing my eyeballs can't see any real loss on HQX renders.

At this point I consider this post to be more of a bug report. I've already spent enough cash on this, I am not paying mining prices for a GPU, when the ones I have work just fine for everything else I do.

To be clear -
In 15 b1 and b2 -
I had the mxf P2 (720p 60)clips totaling a duration of more than 2 hours. I had all the mts files from my CX900 (1080P 60) for the same duration. I had massive amounts of DeNoise applied, massive amounts of color correction (compared to what I've seen in tutorials), At least 60 different cuts and trims. Never once experienced a "GPU Memory Full" error. The individual cameras rendered out in about 20 hours each at 60P.

A new project with a single 1080 60P clip and a single jpeg in the Media Pool causes the GPU Memory Full.

Prior to updating my machine (Fx 8350 with 24GB of RAM) I had the whole thing done in vegas, Neat Video, ProDad Stabilization, Ignite Auto Color, I mean everything. (That's how bad the footage was off of that P2 camera) Never had an error until I went to Render. Updating the hardware just got me to the error faster. I didn't have any of the cheater programs in Resolve because I didn't need them. Resolve can do it all. Off topic - but I am sure some readers are thinking well no duh sherlock all of those cheaters were causing the crash, but nope. Created a new project with just a single P2 clip, vegas wouldn't finish simply transcoding it either. Hindsight being 20/20 it would have been far cheaper to transcode in AME, but Vegas can't handle any of those codecs that maintain quality. Or that I've found to work anyway.
Jeremy Johnson

System Build -
Gigabyte Designare EX
Threadripper 1950X
64 GB of DDR4 3600
1 - 3080 ti - Studio 566.36
1- Intensity Pro 4K - Driver 14.4
1 - Win 10 Pro for WS - Version 22H2 - Build 19045.4894
Resolve Studio 19.1.2 Build 3

Return to DaVinci Resolve

Who is online

Users browsing this forum: Google [Bot], Mike Manus, panos_mts, shanebush, VMFXBV and 248 guests