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:
|Translation files||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.|
|Option files||In the Program Change and Control Change actions, you can replace the Programs list and the CC Commands list in the plugin dropdowns to better reflect the actual effect of the individual commands in your setup.|
|Articulation files||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 that correspond to that particular daw. If your daw is not listed (or if you are not satisfied with the default configuration), you can extend the selection dropdown by adding a configuration file that describes 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 a strict set of rules defined in this documentation.|
|V-pot image files||As with Faders, the graphic display of V-pots in the Mackie Control action can be customized using your own images. These images must also be created using a strict set of rules defined in this documentation.|
- 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 any favorite program, I recommend using GIMP as it is free software with a rather extensive image manipulation features.
- All other configuration files are .xml files. XML files are "ordinary" text files with the extension .xml, and they must follow a specific XML syntax and structure. In Windows, it is entirely possible to create and edit XML files in Notepad, 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 that there are more "XML friendly" editors in macOS as well, but unfortunately, I'm not that 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).