Activity › Forums › DaVinci Resolve › Resolve 11 freezes on render
-
Resolve 11 freezes on render
Posted by Paul Provost on October 6, 2014 at 11:33 pmSeeing this behaviour consistently if I try and render anything over 5-10 minutes long. Either Resolve just disappears “poof”! Or it freezes on render. Sometimes file keeps writing while gui is locked up, sometimes not.
Have to output 15 min feature reels over and over just to get one successful output.
Writing to same raid, different raid, many different codecs and resolutions. I’m on a Mac 10.9.4 with 4 x Amd 280x 6gb cards. Resole 11, 11.1b, 11.1
Saw a recent post from another user on windows with Nvidia card with exact same symptoms.http://www.filmandtvcolor.com | colorist | Los Angeles, CA
Twitter: @4kfinish
Marc Fisher replied 11 years, 6 months ago 7 Members · 13 Replies -
13 Replies
-
David Baud
October 7, 2014 at 1:31 amHave you tried to deleting your Resolve cache folder and recreating a new one? Last week I had some trouble with rendering my output: cleaning up my cache folder seemed to do the trick.
David Baud
Post & VFX
KOSMOS PRODUCTIONS
Denver – Paris
http://www.kosmos-productions.com -
Paul Provost
October 7, 2014 at 4:17 amHey thanks I’ll try it.
Every time I try something and think it’s fixed it returns though. Maybe this one…http://www.filmandtvcolor.com | colorist | Los Angeles, CA
Twitter: @4kfinish
-
Martin Sansom
October 7, 2014 at 9:40 amHave the same problem on my IMac when writing to the same raid, I’ve changed the destination to a faster SSD and so far its worked, no crashes, maybe the destination drive has to be faster than the source drive?
-
Paul Provost
October 7, 2014 at 3:26 pmI read from one Sas raid and write to another. Both 800mb sec or faster. But maybe it’s raid driver or something.
http://www.filmandtvcolor.com | colorist | Los Angeles, CA
Twitter: @4kfinish
-
Nuno Garcia
October 8, 2014 at 1:35 pmPaul I have the same problem with episodes of 35 minutes.
but the activity monitor tells me still render, so i wait and all the episode is render and ok.
I read from one San raid and write to another.Mac Pro late2013
Processor 3,5 GHz 6-Core Intel Xeon E5
Memory 16 GB 1867 MHz DDR3 ECC
Graphics AMD FirePro D700 6144 MB
Software OS X 10.9.4Nuno Garcia
https://vimeo.com/nunotk -
Paul Provost
October 8, 2014 at 3:37 pmExcellent report. Ver of resolve? Does resolve project crash? When you re open resolve does the render queue stil show the job rendering?
Thanks
Paulhttp://www.filmandtvcolor.com | colorist | Los Angeles, CA
Twitter: @4kfinish
-
Nuno Garcia
October 8, 2014 at 9:54 pmYes Paul, Resolve still show the job rendering after you re open. (keeps spinning arrows)
Resolve V. 11 after I update to 11.1 but continues to do the same, freezes during render, stop the render at random places .
I had never seen this behavior in any other pos production house that i work.when you know something let me know 😉
Nuno Garcia
https://vimeo.com/nunotk -
David Baud
October 8, 2014 at 11:27 pmhmm… could it be a napping issue? have you checked the box Prevent App Nap in the Get info window of Resolve? might be a stretch for your problem, but who knows…
David Baud
Post & VFX
KOSMOS PRODUCTIONS
Denver – Paris
http://www.kosmos-productions.com -
Marc Wielage
October 11, 2014 at 2:54 amI think David has a good suggestion above. The default in install is for App Nap to be turned on, so watch out for that. Even with current Macs, we occasionally run into fragmented memory and similar problems, so it might also be best to start a new session each day with a reboot, at least if you plan to render. And don’t have anything running in the background if possible. The few times I’ve had render issues, I was blithely web surfing and screwing around in the background, which is risky when the GPU cards are being driven hard, flat out.
It’s not generally a problem when color-correcting, but I think rendering is a stress on the system from any program and you have to lighten the load as much as possible on the hardware.
-
Paul Provost
October 11, 2014 at 4:13 amYeah well this is a recent and known issue in 11 that has specific symptoms experienced by a diverse user base. Anyone having these freezes please send crash reports to BMD as its being chased down.
I think I may have had this same thing pop up before in ver 9, but can’t remember that far back.http://www.filmandtvcolor.com | colorist | Los Angeles, CA
Twitter: @4kfinish
Reply to this Discussion! Login or Sign Up