Been using DaVinci Resolve 18 for the last 3 months, pretty much without issue - occassiona GLU initiailisation failure on startup, but easily restarted. Running it on a Dell Inspiron laptop with 24GB RAM and 1 TB SDD.
Edited some footage yesterday of Balvenie Distillery, some drone flying and still photograhy wiht a 24 frame cross disolve. Came to render it and it reaches 53% / 1 min 37 sec and then DaVinci closes down. Tried changing the footage, setting up another timeline and copying it over, but still crashing, any ideas?
Free version, render set to 4K, MP4, H.264 29.97 Frame rate, quaity restricted to 110000kbs, same settings as I have always used and have worked for every previous video…
Just trying some diferent music and rendering as a 2nd timeline, fingers crossed it may work this time…
yes, plays fine, no glitches, tried about 5 times last night, changing diferent pictures and transitions, even removed the subtitles for the pictures, but wouldnt have it… Wss up until 0045 trying to get it working…
INTEL i5 processor, NVIDIA GeForce MX230 GPU, set to high performance for Resolve and sleep modes turned off…
No NR running that I am aware of, and nothing else running on the computer…
Just shut down again at some point, so its not the music… I may have to start the edit again and see if that helps…
I’m using DaVinci Resolve Studio 17 but had a very similar issue a while back and it turned out to be the render quality setting. In Auto it kept crashing but when changed to ‘Restrict to’ and lowered the kb/s setting it would then render. Try coming down from 110000 kb/s.
If this has been the setting used successfully many times in the past, then it would be strange if this were the setting causing the issue - but everything worth trying.
Ok, created a new project, rebuilt it and it still dies half way through, removed the inividual picture and it still does it…
Opened another project that has previously rendered ok and re-delivered and it ran no issue whatsoever, so it seems like its an issue with the still images, or the transitions between them…
Bugger…
Going to remove the disolves and manually fade in and out… and see what happens then…
The cross-dissolve really does very little. Would be seriously surprised if this was the culprit.
By any chance, were you using the Fusion Transition version, rather than the standard transition? That’s a little more processor intensive and just could be the difference?