<< Click to Display Table of Contents >> Navigation:  Nodes > Input > File Formats > Import Mlnk

 

Purpose

 

When loading a media file into other Mistika applications for the first time, the media file is analyzed and a ".mlnk" text file is created in the current Mistika project, containing all the useful metadata about the imported file (tapename, timecodes, frame rate, codec, etc). This indexation process only needs to be done one time per media file, and it permits much faster processing within those Mistika applications later (because all the meaningful metadata was already extracted). This indexation process can be automated with the Mistika MLNK node, which does the opposite to this node.

 

The purpose of the Import Mlnk node is the opposite, given a Mistika .mlnk file it can extract the original media files mentioned on it to import them in Mistika Workflows passing them to the AV out connector, so that they can be used in posterior nodes that could not work with .mlnk files directly.

 

Standard properties

Object Name

Color

Bypass

Lock

 

Inputs

 

mlnk: Mistika .mlnk files.

 

Outputs

 

AV out: The original media files mentioned  in the .mlnk files connected to the input.

 

 

Node specific properties

 

Trim options (From File, Custom):  

 

From File: The .mlnk files can contain in/out points referring to a particular segment of the media file.  

 

Custom (In, Out): This mode permits to redefine the in/out poits (number of frames to be used as head & tail), for which two properties In / Out will appear.

 

Note: In old versions the .mlnk files were using ".lnk" extension instead, which was later renamed to ".mlnk" to avoid confusion with Windows links.  You may still find them mentioned as Mistika ".lnk" files in older documentation, but they are the same type of files.

 

 

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