<< Click to Display Table of Contents >> Navigation:  Nodes > Tasks > Render Engines > Mistika Render

 

Purpose

 

The MistikaRender node permits to execute render processes for Mistika render jobs (.rnd script files), which can be created with other Mistika applications as well as some Mistika Workflows nodes (mainly the encoder nodes). The render process produce new media files, which are passed to the output connectors.

Note: If you plan to render  .rnd scripts coming from other computers please note that the local system may need additional third party plugins and additional licenses ...

Standard properties

Object Name

Color

Bypass

Lock

File Path

 

Standard Encoder properties

Render Farm

 

Inputs

 

rnd: The .rnd file or files containing the Mistika render scripts.

 

 

Outputs

 

AV Out: Rendered media file (image files, with or without embedded audio)

 

Ext. Audio: Rendered audio files (when using rnd files producing external audio).

 

Notes:

 

In principle the render process will create video and/or audio files in the target folders that were configured within the .rnd file (when creating the .rnd), that is, the path location  for the rendered media is not specified in Mistika Workflows but within the rnd scripts themselves.

 

However, the media path can be redefined with the File Path property, so that they can also be changed within a workflow.

 

Once they are rendered, the node outputs provide convenient access to the new media files.

 

Note: You can generate .rnd render scripts with Mistika Ultima or Mistika Boutique using the Render panel->Write Script Only button.

 

Alternatively, those Mistika products (and also Mistika VR) provide a Render->AddToRenderQueue function to create .RND Files that can be then submitted to external applications. One of these options is to Send rnd to a Mistika Workflows Watch Folder, so you can then get the files with a Watcher node connected to this node for basic batch processing.

 

Example:

 

1.- Write a render script (.rnd) with Mistika Boutique. During that process you will specify the render name, destination path, destination format, etc.

 

2.- Drop the .rnd File into the workflows editor.

 

3.- drop a Mistika Render node into the editor too

 

4.- connect the "To" connector from to the RND File node to the "rnd" connector into the Mistika Render node.

 

5.- now, if you add the workflow to the Queue and run it, the render will be executed as defined when you wrote it with Mistika

 

Note 1: if you define a path and/or sequence name in the File Path property of the Mistika Render node, then the render destination will be changed. Note that you can only change the destination folder and  file name, but not the render codec and other settings that need to be defined in Mistika Boutique.

 

If you leave the File Path property empty, then the path and name defined in the .rnd File are used

 

Note 2: if you have multiple .rnd, you can also drop a folder containing them, in which case all of them will be rendered when you execute the workflow.

 

Note 3: another option is to connect a Watcher node. In that case, once the workflow has been activated (added to the Queue Panel) any .rnd landing into the watched folder will be rendered automatically.

 

 

 

 

 

Developer reference (API Rest - node/MistikaRender/property/[Property ID])