PREFACE

Dedicated to all who invented the wheel for several times and actually not want to invent it again...

OVERVIEW

What is the MATRIX?

The MATRIX is a Linux based realtime-multidata-controlpackage, ment for the use of any kind of control tasks. The MATRIX could be understood as an input-output control (logic) for any thinkable triggers or displays.

The MATRIX consists out of a "kernel" and several "devices". The main function of the "kernel" is to communicate bi-directional with the "devices" and to interpret the "script", which can be understood as the end application logic.
The "devices" themselves translate the hardware specific data into data, which can be computed by the "kernel".
The "kernel" uses several intelligent software-parts (so called DEVICES) for the communication with the connected hardware. Since you have a midi-compatible sound-card, a DMX-card and a Linux-PC a "MIDI-2-DMX"-converter can easily be put together. Due to the fact that the application logic of MATRIX can be scripted, it is possible to build much more than a static "Midi-2-DMX"-Converter. For example the parameterization of the conversion by, for instance, a speech recognition device would be possible without much afford.

Functionality

For every hardware to be controlled, the MATRIX requires one "DEVICE".
A Device is not only a hardware-driver but equals the logical functionality of the controlling unit or the unit to be controlled. In the majority of cases the unit will be a special hardware: for example a DVD-player or a projector etc. A "logical unit" can also be a special software, for instance a speech- or picture recognition.

Why MATRIX?

The MATRIX is universally applicable and particularly recyclable. Certainly it takes some time to get used to a new scripting language, indeed all logical parts of the MATRIX are strictly separated from the functional parts. That makes it possible to reinstall the same package by exchanging only the application logic (the script).

New hardware? No problem!
An API exists for the interface between kernel and devices - the devices are in general OpenSOURCE. Everybody can optionally write his own device. But for the majority of cases that will be unnecessary because there are plenty of devices ready for download as source code and executive.

Another aim of the MATRIX is to reduce and ease recurring development work in the field of artwork-production. The scripting language can also be learned by the less experienced user. Now everybody can realize his application on his own - the development effort is already done - the user can concentrate on the real application without wasting time on the interminable development of the framework (hardware communication).

Every device stands for a controlling hard- or software respective for a hard- or software to be controlled.

 

NETWORK

Not the whole MATRIX has to be installed on one computer. Kernel & Script are installed on any computer within a TCP/IP Network. The devices are located either on the same computer, or on any computer in the network.

The MATRIX gets into contact with devices defined in the script and communicates the control tasks between "script and device" as if the device ran locally on the computer.

Please note: Certainly, in this case the latency times of the network have to be considered. I.e. the MATRIX will relay the latency times to the system depending on the network and the ongoing data traffic.