MIDI-MT - Application Configuration Files

The configuration file

• General Configuration Section

• Module settings

• “units” control configuration section

• Control Configuration Example

The configuration file is in the popular Json format and you can use any text editor to change it. A working example of a configuration file is also included in the distribution. You can find it in the application installation folder; a copy of the configured configuration is located in the docs subfolder with the name “MidiController.cnf”.

The main parameters of the configuration file can be configured from the dialog that launches when you select the “Start” menu item. You can also configure these settings directly when editing the configuration file.

General Configuration Section

{
  "config": {
    "name": "MidiController",
    "autostart": true,
    "build": "1.0.6.3"
  },
  "units":[... description of controller controls...]
}

The values ​​of global parameters and their relationships are described in more detail in the Settings section.

Module settings

All information about setting up modules is located in a common configuration file. It is also possible to strictly override the settings of a specific module by placing a settings file of the same name with the module with a .json extension in the same directory. An example in the picture below.

JSON sections of module settings are located in the description of the modules themselves.

“units” controls configuration section

The control’s description line looks like this:

{
    "scene":177,            // control scene 
    "id":22,                // control key
    "type":1,               // control type
    "target":254,           // group
    "longtarget":12,        // target 
    "onoff": false,         // last value 
    "value": 2,             // last value 
    "apps": [               // application list
       "App1",
       "App2"
    ]
}

Scene (scene), the real Scene MIDI ID is indicated in the configuration. A scene is a selected preset; a typical controller usually has 4 scenes:

ID (id), MIDI control identifier, I hope everything is clear here.

Control type:

Target (target,longtarget), the destination of the control payload. For buttons, the first value, target, is a quick press, the second value, longtarget, is a long press. If you don’t need to use a long press, set the longtarget property to 255. For other types of controls, the second value is not processed, but requires a set value.

Also, the target value can indicate the relationship to the group, as in the cases with the groups Audio sessions, Multimedia keys, Lights controls and Smart House. In this case, the longtarget value specifies the payload.

Working example of control configuration

{
    ....,
    /* setting for scene number 2 */

    "units":[
        {"scene":177,"id":22,"type":0,"target":0,"longtarget":255},
        {"scene":177,"id":13,"type":1,"target":1,"longtarget":255},
        {"scene":177,"id":31,"type":3,"target":3,"longtarget":255},
    ]
}