Why Isn’t My Job Rendering? Let’s Find Out!

When you submit a job to Deadline, render nodes are typically able to pick it up and start working on it immediately. However, it can be puzzling when a job sits in the “Queued” state when there appears to be Deadline Slaves that should be able to render it. To address this problem, we’ve introduced a new feature in Deadline 10.0.10.4 that allows you to investigate the reason!

Read More

Render Node Performance Not Up To Snuff? Time for a Physical!

To make the best use of your available compute resources for rendering, it can be beneficial to determine which render nodes perform the best and, if any, perform below expectations. By using Deadline in conjunction with MAXON ® Cinebench ®, we can make a good approximation of individual render nodes performance across your farm!

Read More

Locking Down Your Farm

Locking Down Your Farm

There are some features in Deadline that require communication over a network. While these features may be powerful and highly useful, they introduce potential security concerns. This article will go through three major security features that have been added in Deadline 9 and 10, focusing on how to use them and how they can help you secure your farm from various potential vulnerabilities.

Read More

Asset File Transfer, Caching, and Storage in AWS

Asset File Transfer, Caching, and Storage in AWS

One of the many goals of Deadline 10 is to ensure that customers can render on AWS as easily as possible. An essential part of moving to a hybrid or fully AWS-based rendering workflow is dealing with transferring asset files to AWS, and downloading resulting renders from AWS. Fortunately, customer can accomplish this job with Deadline 10 painlessly by using the new features that make dealing with asset files in AWS a breeze!

Read More