|On this page|
Generates work items that render an IFD file using Mantra. The IFD file can be read from upstream, or manually specified with a custom path.
Work Item Generation
Whether this node generates static or dynamic work items. You should generally leave this set to "Automatic" unless you know the node’s work items can be computed statically, or that they need to be generated dynamically.
This node always creates dynamic work items: it waits until the upstream work items are known, and generates new work items from the upstream work items.
This node always creates static work items: it creates the number of work items it thinks it needs based on the parameters (and any upstream static items) before the network runs.
If the input is static (a static processor, or a partitioner with only static inputs, or a mapper), this node generates static work items, otherwise it generates dynamic work items.
How the processor node handles work items that report expected file results.
If the expected result file exists on disk, the work item is marked as cooked without being scheduled. If the file does not exist, the item is scheduled as normal.
If the expected result file exists on disk, the work item is marked as cooked without being scheduled. Otherwise the work item is marked as failed.
Work items are always scheduled and the excepted result file is ignored, even if it exists on disk.
The source of the IFD file
Upstream Output File
Uses the output file produced by the upstream work item as the path to the IFD file.
Custom File Path
IFD file specified by a custom filepath.
The data tag used to select the result from the upstream work item.
The path to the IFD file.
Overrides the image output file name.
Extra Mantra Args
Specifies extra arguments that will be passed to the Mantra executable when rendering the IFD.