Configuration files overview
The plugin has a base set of features that can be selected using the available fields and dropdowns in the Stream deck editor. If these base features do not cover the needs of your particular midi setup, there are several ways you can extend the plugin by adding configuration files. The following set of configuration files are possible:
For actions with Fader or Cycle buttons, you can create files that define steps to be cycled through and translate incoming midi messages to text and images.
In the Program Change and Control Change actions, you can replace the Programs and CC Commands lists in the plugin dropdowns to better reflect the actual effect of the individual commands in your setup.
In the Note On/Off action you can load articulation files that populate the dropdown with articulation names. Articulation files can be custom built or you can load Cubase/Nuendo Expression Maps and Logic Pro Articulation Sets.
Fader db files
When using fader buttons in the Mackie Control or Control Change actions, you can display the actual dB value on the button by selecting your target daw in the selection dropdown. If your daw is not listed in the dropdown, you can add it by adding a configuration file that describes how to translate the raw midi number sent by the daw to dB values.
Mackie Control Layout files
You can select your target daw in the Mackie Control action to get command selections corresponding to that daw. If your daw is not listed (or you are not satisfied with the default configuration), you can extend the selection dropdown by adding a configuration file describing which commands are available for your daw.
Fader image files
The graphic display of faders in the Mackie Control and the Control Change actions can be customized using your own images. These images must be created using the strict rules defined in this documentation.
Dial Fader image files
The graphic display of faders in the Mackie Control and the Control Change dial actions can be customized using your own images. These images must be created using the strict rules defined in this documentation.
V-pot image files
As with Faders, the V-pot graphic display in the Mackie Control action can be customized using your own images. These images must also be created using the strict rules defined in this documentation.
Please note that V-Pot images V2 are much more flexible and can be used by more actions, so my recommendation is to create V-Pot V2 designs described below, not V1.
V-pot image files V2
V-pot images V2 are more flexible than V1 and can be used in all actions displaying V-Pots. If you are about to start creating your own V-pot design, I strongly suggest using this instead of the more limited V1 format.
Cycle direction image files
Cycle buttons can display direction indicators superimposed on the background image and will show the direction of the following button press.
The image files for faders and V-pots are, of course, image files (.png). Image files can be created/edited in many programs; If you don't have a favorite program, I recommend using GIMP as it is free software with rather extensive image manipulation features.
All other configuration files are .xml files. XML files are "ordinary" text files with the extension .xml and must follow a specific XML syntax and structure. It is possible to create and edit XML files in Windows, but I recommend using Notepad++, a feature-rich editor. In Notepad++, you can tell the program that you are working with an XML file, and Notepad++ will help with coloring, matching tags and other helpful things. In macOS, you can use TextEdit to create and edit XML files. I assume there are more "XML friendly" editors in macOS as well, but unfortunately, I'm not experienced with macOS and cannot recommend any specific editor.
Both programs (Gimp & Notepad++) have a learning curve, but if you learn them (for the bits you need), they are pretty good (in mho).