|
<< Click to Display Table of Contents >> Navigation: Nodes > Tasks > Mistika Features > Set DisplayFilter files |
Given a display filter that was created containing certain images, this node permits to substitute those images by others.
This permits to create display filters that can compose logos and motion graphics by using example images, and later use this node to substitute the original images for the necessary ones at workflow execution time (Once the images are substituted, encoder nodes can load the modified display filter to achieve the desired results)
Note: This node can only replace the image files that are used, not text appearing in the display filter. If what you want is to replace the text overlays (watermarks) use the Watermark Cfg node instead
input1 ... inputn (custom images): One input connector for each image clip found in the display filter (after selecting it in the display_filter property), with the connectors optionally named as the original images found in the display filter (if the Use Names property is On). In these inputs you can connect any other images to substitute the originals.
dFilt: The modified display filter file.
Display filter: The display filter file to modify. (Mistika display filters are predefined effect templates typically created in Mistika Ultima and Mistika Boutique)
Destination: Where to store the modified display filter. If left empty then the original display filter will be overwritten by the new version. If you define a new destination then it will create a new display filter, and the original one will remain untouched.
However, please note that the DisplayFilter property in this and other nodes will only offer the display filters stored in the official location ( SGO Apps/shared/display_filters ).
Use Names: If it is On then the names of the original image names found in the display filter are used to name the input connectors. Otherwise they are named as input1, input2, ... inputn. This is just for interface clarity, deactivate it when the original names where non meaningful.
This node is normally used in combination with rank connectors, as you will want to prioritize the display filter configuration before loading the display filter in an encoder node. As per the example image:

Note that this node does not "pass" the display filer to the encoder node. What it does is to modify the display filter file itself, but it still needs to be selected in the encoder node (the display filter "Promo" in this example).
Property Label |
Property ID |
Display Filter |
displayFilter |
Destination |
url |
Use Names |
useNames |