<< Click to Display Table of Contents >> Navigation:  Nodes > Tasks > Classifiers > Classify By Extension

 

Purpose

 

This node filters the input media by its file extension. In this way, you can route different types of media files through different output connectors. You can also define the behavior for extensions that are not declared (either to ignore them or stop the workflow).

 

Inputs

 

files: To connect the files to be filtered. You can connect a Folder or Watcher node, for example.

 

Outputs

 

Output List of possible extensions: A definable list of connectors. You can add/remove connectors by adding/removing their names on the Extensions property. When adding / removing values to this property the connectors will be automatically added or removed.

 

 

Standard properties

 

Object Name

Color

Bypass

Lock

 

Python standard properties

 

Code

NOTE: An introduction to all the Python tools in Mistika Workflows is available in the Python scripting tools section.

 

 

Node specific properties

 

Extensions: Comma separated list of possible extensions (without the initial dot). The default list includes common media formats: mov, mxf, mp4, j2k, r3d, rnd. You can add or remove extensions as needed. Each extension in the list creates a dedicated output connector on the node.

 

Filter Mode (Exact Match, Starts With, Contains, Ends Width). Permits partial matching. To permit flexible names such as ".tif" / ".TIFF", or ".jpg" / ".jpeg",  

 

Case sensitive: Case sensitive matching. Activate it to avoid files not strictly matching your naming rules due to human errors.

 

 

Error mode:  When no matching is found, this property defines what kind of error message will be sent to the error log (None, Info, Warning, Critical). This is mainly to facilitate user scripts parsing render log files later (or human monitoring). But note that this is just a log message, the case Critical will not stop the workflow execution because this node provides its own error control branches via the other connector (when the output connectors do not cover all the possible outcomes).

Note: All those messages / errors are shown in the Render Log panel, and they are also saved to the daily log file under the SGO AppData/workflows/log folder)

 

 

 

Developer reference (Python - ClassifyByExtension.[Property ID], API Rest - node/ClassifyByExtension/property/[Property ID])