YOUR CLOUD CONNECTED STUDIO
Today’s studio pipelines are more complex than ever. The modern facility uses multiple tools, utilized by hundreds of artists, all with varying compute demands. That makes for a complicated rendering pipeline that, if left unchecked, can quickly snowball out of control.
Deadline is a high-end render management solution that is designed to simplify things. It’s deep, customizable functionality manages rendering complexity on-premises or on the cloud with native AWS integration.
Register to try Deadline 10 today by filling out the form below:
To help you get up and running quickly, the Thinkbox Marketplace provides Usage-Based Licensing for popular content creation tools (such as Maya, 3ds Max, Vray, and others) removing the complexity of adding additional licenses. When combined with Deadline, these solutions help you efficiently and cost-effectively scale your render farm to deliver projects on time and within budget.
Deadline is render management for the modern studio.
Integration with AWS Cloud
Deadline supports native integration to the AWS Cloud to enable customers to expand their render farms simply and securely. To ensure that all the appropriate files are available in the cloud, Deadline synchronizes with local asset servers and manages the data transfer before rendering begins, tagging accounts and instances for cost tracking.
Flexible Licensing Options
Deadline supports traditional Floating licensing as well as Usage Based Licensing via the Thinkbox Marketplace. These licensing models can be used separately or together across local, remote, or cloud-based render nodes. Deadline also supports dynamically switching to Usage Based Licensing if no floating licenses are available.
Remote Connection Server
The Remote Connection Server is a new Deadline application that is meant to be a drop-in replacement for the Deadline Proxy Server application. In any situation where you could use the Proxy Server, you can use the Remote Connection Server instead.
Dynamic Licensing Switching
The Deadline Slaves can now automatically switch between traditional Floating Licensing and Usage Based licensing. Prior to rendering a job, a Slave will first try to check out a Floating License. If this fails, the Slave will check if the Floating License threshold has been reached, which is based on the number of Slaves currently rendering with Floating licenses. If it has, the Slave will then use Usage Based licensing if the Usage Based limit has not been reached.
Deadline AWS Portal
The AWS Portal in the Deadline Monitor connects to your existing AWS account, and allows you to launch AWS render nodes that connect to and extend your on-premises render farm. The render nodes can use Deadline Usage Based Licensing, or they can use floating licenses by connecting to your on-premises Deadline license server.
Execute Command Whitelist
To enhance security, a new Execute Command whitelist option has been added to Remote Administration, which allows you to define the exact commands that are allowed to be executed on remote machines. This allows administrators to simply pick from a list of pre-defined commands to execute remotely, and removes the ability to type in arbitrary commands. This new feature is optional, and enabled by default.
Flexible Deadline Client Configuration
All settings in the deadline.ini configuration file can now be overridden using environment variables. Simply prefix “DCONFIG_” to any supported deadline.ini key and give it a value. In addition, Deadline will now fall back to the values at the user and system level if an environment override isn’t present.
Flexible Job Scheduling
Use numeric job priorities, machine groups and pools, and job-specific machine lists to explicitly control distribution of rendering resources among multiple departments. Limits allow you to handle both limited license plug-ins and render packages, while job, asset, and script-based dependencies allow you to control when your jobs will begin rendering.