The NIX-ENGINE is a flexible and scalable audio server, either used for achieving medium to high levels of processing in an automated environment, or for providing cost effective flexibility in large Post Production facilities.
NIX-ENGINE is modular product, with a basic, single-function version being extremely cost-effective. Complex workflows can be realised by purchasing multiple modules, and these complex workflows can still be applied to your media files using simple watch folders, or by integrating at API level into other tools.
NIX-ENGINE has optional access to all processing functions available within the desktop tools. Depending on license, functions are available individually, or can be ganged into complex sequences of operation.
NIX-ENGINE can provide any of the following functions:
With NIX-ENGINE users can configure ‘workflows’, and any one workflow can do a multi-step combination of any or all of the available modules. The following diagram illustrates a workflow required by one of our Broadcast customers, although of course you can also define a workflow to simply Loudness correct stereo files.
NIX ENGINE carries out all of the processing steps shown in the illustration, from a single API command. No complex re-programming of your MAM is required to make changes to your workflow – simply use our easy UI tool to create your new workflow, then off you go! A typical workflow like this can be configured within a couple of minutes, and of course making edits in future takes mere seconds.
This screenshot shows how the above workflow is displayed within our user interface.
NIX ENGINE consists of two main components, NIX FLOW and NIX ENGINE. NIX FLOW provides a REST API interface to third party tools. There is one NIX FLOW in every NIX ENGINE deployment, and NIX FLOW is installed as a Windows service or OSX daemon. NIX FLOW passes files to be processed to each NIX ENGINE process. Various configurations are possible depending on your license. For example, there can be multiple NIX ENGINEs on a single PC.
Another common configuration is for environments where a large number of users wish to have files processed, but the actual volume of files is quite small, such as with larger Post facilities. For these cases, it is possible to use NIX ENGINE in conjunction with eCLIENT. Every operator has an eCLIENT, and these all share a central processing facility.
© TSL Products 2016 All Rights Reserved