We regularly have AE jobs that don’t complete although Deadline says it is complete. We end up with 0KB frames in our output. If we are rendering to a MOV, it simply stops outputting. Again, Deadline shows no errors and completes the job. We can delete the 0KB frames and then resubmit the job and it finishes up without issue. I know we can set the minimum frame size checking for the image sequence renders but we have gotten better render times with Multi-Machine enabled and then the option doesn’t exist for Output File Checking. For a current project, we are hoping to render to MOV but cant with this issue happening.
Anyone have similar issues? Any suggestions?
We are still on Deadline 6.2.50. All Win7 64-bit slaves. AE 2014 and 2015.
Hello,
Could I have you save out a job report(docs.thinkboxsoftware.com/produc … nd-history) from a task where this happened and send it over to us? We’d love to see if there is any indication of the problem. One where things worked well would be good too.
Job Reports Attached. You can see the two most common errors in the first couple of reports: file read error and file write error. Our workaround has been to re-queue the job and, typically, it does not throw that error again. The job may throw the same error on a different file in which case we repeat the workaround and it moves on. Eventually, the jobs nearly always finish without us changing anything, just re-queue over and over again.
We have been testing the renders outside of Deadline with the same command line arguments and we continue to get the same issues so I dont think it is a Deadline problem. Wondering if there is a way to get Deadline to handle the issue and just re-queue without manual intervention.
deadline Reports_Job.zip (193 KB)