![]() ![]() ![]() Not sure what to say, but it's definitely "funny". it's working now, including moderately complicated node trees of about 8 nodes, OFX, keys, and Neat4Video. SO! In a fit of optimism I opened my project from last night. Tried again with new project and a GH5 clip, and that worked too. Tried ProRes render from last night, same result.įully shut down Resolve, started it up again, this time with a new project, importing a ProRes render from last night, and it worked. (but I think the multiple projects stayed open). It allowed play briefly (but no video showed) and then, the GPU full error popped up. I started a new project, and imported a clip from the same folder. This was from a fresh boot, and then a reboot. Nothing else has changed with the computer. The error message pops up when I try to play, click, or scrub on empty portions of the timeline, and does so even with master FX bypassed. I render clips individually for stock media, so it is not a complicated timeline, although some of the individual clips (non transcoded GH5 h.264 10bit 4K). ![]() The project consists of a timeline with 5 individual clips in it. Have not tried to suss that out, but of note, on my machine with Studio 16 Beta, I have used it for two days with no issues, but loading up a project today (the same I rendered successfully from last night), cannot work. This is with Windows 7, since I was informed it is not supported, I have not asked for community support since, but my wife has the free version recently installed and doing a very simple operation on her Windows 10 laptop, she got GPU Memory Full message. Please feel free to move this to the appropriate place on the forum - if I posted to the wrong section, my apologies. I really love so many elements of what Davinci Resolve does that I try to overlook these - but I believe this is a serious flaw and many users will hit a wall early without addressing with a setting to limit the video memory to whatever the users base cards support and having the software scale appropriately around that - even if the performance isn't what a top top spec machine would yield. I saw some people saying that minimum spec for 4k timelines is something around 11-12 Gb GDDR? Is this true? Could there be a memory leak in the built-in 'Noise Reduction' code - as I heard that is a sure way to hit this 'GPU memory full' error. I am just curious if there is maybe a more efficient way to cycle or purge the video memory when old cached elements aren't needed. My main question: Will this issue be looked into? I see many posts all over the net about this occurring for others. This is on a very small 4K timeline (2 minutes max) with minimal node adjustments and a couple of Fusion clips for lower 3rd titles and some onscreen text elements at the end. I am running with a 1050 ti w/ MQ 4 Gb GDDR + 16 Gb of RAM (Dell 9570). On the same project in 15.3.1.003 I was not getting this error. My main issue walking into version 16 public beta was: 'GPU Memory Full' right off the hop. I did a lot of research on selecting the right settings and using optimized media and caching where I can. ![]() I backed up my database for 15 and upgraded to 16 (I was soooo excited to try the new features and hoped for some optimization in the codebase to allow the program to be more efficient with resources). So, we recently bought Davinci Resolve Studio - I have the last version of 15 installed and everything is working well - although I get a lot of slowdowns when having Fusion clips as part of the timeline (this isn't my issue but leads to my main issue). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |