Last month, Thinkbox announced the availability of Deadline 8, which debuted on-demand, per-minute licensing for Deadline, Thinkbox’s Krakatoa and Sequoia, and third-party applications including The Foundry’s NUKE and KATANA, and Chaos Group’s V-Ray. Users buy time credits online, with those minutes consumed only when the Slave application is rendering.

Deadline 8 monitor
Deadline 8 monitor

For the month of May, users can sign up at the Deadline on Demand web site and will receive complimentary time in 10,000-hour increments on a first-come, first-served basis. The credits will expire at 12am PDT on June 1, 2016. It’s a great way to try out the service and see how it can work for your projects or facility.

The hours may be used for their on-site or cloud-based rendering.

The recently-released Deadline 8 lists a number of improvements. The v8 Proxy Server allows users to securely connect to and interact with remote and cloud-based render farms over public Internet without the need for a virtual private network (VPN). For VPNs already in place between remote locations, the Proxy Server can be used to provide a more stable connection over high-latency networks.

The new version of Deadline also features improved Monitor interactivity, with long running operations such as deleting thousands of jobs or configuring hundreds of Slaves now being executed in the background and controlled by a new Background Operations panel that allows users to view, pause and cancel activity. Multiple Monitors are now supported, enabling users to control several farms or offices simultaneously from one screen, and the List panels in the Monitor have been rewritten from the ground up to be more efficient when handling thousands of jobs or Slaves.

Deadline 8 also adds application support for Toon Boom’s Harmony, The Foundry’s KATANA, NVIDIA Iray for Maya, Imagineer Systems’ mocha Pro and UnrealSwarm. For additional stability, application plug-ins and events now run in a clean environment that is separate from Deadline applications. The environment is reset between render jobs, ensuring that any changes made will not impact subsequent jobs. Since applications and events are sandboxed, if an issue were to occur, only the problematic application or event would restart and Deadline as a whole would remain unaffected.


Thanks so much for reading our article.

We've been a free service since 1999 and now rely on the generous contributions of readers like you. If you'd like to help support our work, please join the hundreds of others and become an fxinsider member.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.