This article explains how to install the Mistika Workflows plugin for Deadline, and how to configure it.

This article assumes that you already have a Deadline render farm fully tested and working, and it focuses only in the configuration of the Mistika Workflows side. Please refer to the official AWS Deadline documentation in order to setup your Deadline renderfarm according to your own environment. 

Also note that all render nodes of the farm must have Mistika Workflows installed and licensed to be able of render its jobs. 

We strongly recommend to test Mistika Workflows directly on each render node (without using Deadline) before trying to use it with Deadline. Otherwise the diagnostic can be very complex not knowing where the problems come from.

Mistika Workflows Deadline plugins installation

NOTE: Due to changes in the plugins code on Deadline side, the Mistika plugins are changing often. The files attached to this article will be updated as both applications evolve, but if they do not work in your case then please notify it to so that we can review and update them if necessary.

Mistika Workflows plugin consist on several files that must be placed at ../DeadlineRepository10/custom/ 

These files can be found attached to this article in the MistikaWorkflows plugin for

The "plugin" folder that it contains needs to be copied here (with all its content):


And the submission script custom/scripts/submission/ needs to be copied here:


Finally edit the DeadlineRepository10/custom/plugins/MistikaWorkflows/MistikaWorkflows.params file and make sure it points to the workflows executable in your system, as they will be pointing at a default installation paths.

Once you have copied these files, Mistika Workflows plugin will appear in Deadline Monitor and it will be ready to receive Mistika Workflows jobs. You can check it by activating the Power User mode in the Tools menu, then go to 'Configure Plugins':

Deadline configuration in Mistika Workflows

In Mistika Workflows, go to File menu --> Preferences --> RenderFarm, and put the paths to Deadline and MistikaWorkflows submission script as found in your system. Default paths are:

Deadline Path: C:/Program Files/Thinkbox/Deadline10/bin/deadlinecommand.exe

Deadline Submission Path: C:/DeadlineRepository10/custom/scripts/Submission/

You can also add here the desired params to be taken into account when processing the job, such as defining the group and the pool to be used during the render. Find below at the end of this article the full list of available params.

Submitting Mistika Workflows jobs to Deadline

Mistika Workflows can send two types of jobs to Deadline: 

1 - At per workflow level:  Each time a workflow is triggered (typically by a Watcher node or an Auto Trigger node) it will be sent to a different render node.  This method is the most efficient when there are multiple clips to be processed, as sending them to different render nodes provides better resource utilization in terms of disk IO, optical flow processing, and because it also applies to other nodes different than transcoders.

2 - At Transcode task node level:  Workflow nodes transcoding media formats are typically the most complex to process and can be very time intensive, so this method permit to transcode a same clip by using multiple render nodes at the same time (with each render node rendering different packets of frames). This is the best method when you normally get isolated clips (not batches of them) and the priority is to render the incoming clip as fast as possible.


In particular:

1 - In order to submit a whole workflow from the Render Queue to Deadline, the Queue renderfarm toggle must be active before the queue is executed:

2 - On the other hand, if you want to send a particular trasncoder task node to the renderfarm, its 'Render Farm' toggle must be activated (and then execute the workflow in the Render Queue as usual).  In this way only the particular task node will be sent to the render farm:

Additional parameters can also be added to be taken into account. Most of the parameters will be added automatically by Workflows when submitting the jobs.  Some others like "-q [--quiet]" can be added manually (the "quiet" mode avoids  showing file dialog prompts asking for confirmation).

The full list of available params to be introduced is:

-i   [--ifile]               --> Input file to be processed

-n  [--name]            --> render name

-r   [--range]            --> range

-S  [--sequence]      --> 0 if it is a movie, 1 if it is a sequence 

-o  [--ofile]              --> output file

-F  [--restServer]     --> feedback URL

-J   [--jobID]             --> Render JobID

-b  [--blockSize]      --> number of frames per render chunk

-p  [--product]        --> product

-g  [--group]           --> group

-P  [--pool]             --> pool

-q  [--quiet]            --> quiet mode