Thu Jan 03, 2013 2:05 am
Same issue here, on two systems, rendering identical material from, in one case, a network volume, in the other case, a local folder.
Material is S-Log from a Sony F3, recorded via SDI to a Hyderdeck Shuttle, QT-wrapped DNxHD, rendering audio and video to DNxHD 120 MXF using the default 1D LUT. Our machines:
Resolve Lite 9.0.4 on a 17" MBP, 10.8.2.
Resolve 9.0.4 on a Mac Pro 3,1 with 16GB and 3 x 680GT in a Cubix, 10.8.2.
In each case the Deliver page seems to be fine, the render begins, then after some random time it stops progressing, indicated FPS drops to 0.0 and Resolve continues to render black clips, as the remaining time counts up.
Sometimes a force quit is needed to Stop Render, and usually switching to the Media Pool reveals a bin of clips that display black in the viewer. Removing clips and re-adding them doesn't help, and a quit is needed to refresh, after which the media pool is empty on relaunch. Resolve simply ceases to see its sources, which have gone nowhere.
This is the only project on which we've had this issue to date. RED and Alexa material have been fine, F-3 via a Hyperdeck Shuttle has not. As a precaution, I've made sure Energy Saver and Screensaver settings don't kick in, no drives go to sleep etc... this issue seems entirely self-generated by Resolve. Unless...
A very frustrating way to feed an editor four shoot days over the holiday season! Thoughts welcome.
Peter Barrett