Set the values for "On" and "Off" commands. The default values are 127 for "On" and 0 for "Off," but you can modify them if your device or DAW requires different settings. If a single-byte command is selected, the maximum value is 127; for NRPN or a dual-byte command, the maximum value is 16,383.
The dropdown determines how received values affect the button state. The options are:

• The On value and all values above it will set the button to the On state. Values below the On value will set the button to the Off state.
• The On value will set the button in the On state. All other values will set the button in the Off state.
• The On value will set the button in the On state. The Off value will set the button in the Off state. All other values are ignored.

(Only visible if button type is "Hold")

For Hold buttons, some devices or DAWs might miss the "off" command if it is sent too soon after the "on" command. The Cubase "Forward" function, for example, will ignore the "off" command if it is sent less than 250 milliseconds after the "on" command (...don't ask me why). If you press a Hold button briefly and the system doesn't respond to the "off" command, try adding a minimum hold time (in milliseconds). If your key press is shorter than that time, the plugin will delay sending the "off" command until the minimum time has elapsed.

A latch button is, in effect, a Toggle button with an added association with a "latch group".

If you, for example, are using messages to control articulation, it can be helpful to disable the previous articulation when a new one is selected. Only one button in a latch group can be on at any given time. When a button in a latch group is pressed, a command to turn off the previously active button (if any) is sent before sending the command to turn on the pressed button. There is an option to reset the active button by long-pressing it.

Latch groups are shared between the Generic Midi and Note On/Off buttons, so pressing a Generic Midi latch button can trigger a Note Off message for a Note button and vice versa.

Select a group from the dropdown to add a latch button to an existing latch group. The dropdown lists latch groups detected since the Stream Deck application was launched, which may include groups from different profiles or folders. If latch groups are only used in profiles or folders you haven't activated since the last start of the Stream Deck app, they won't appear in the dropdown. If you know there's a latch group that isn't shown, you can still assign the button to it by registering it as a "new" group, as described below. As long as the group name is exactly the same (case sensitive) as a group in a not yet activated profile, it is considered the same group.

To add a new latch group, type the group name in the text field and click the + button. The group will appear in the dropdown menu and will be automatically selected for the current button. There is no way to manually remove groups from the dropdown. If you remove all buttons from a previously used group, it will be deleted the next time the Stream Deck application restarts.

If latch buttons are set to use two icons, the most recently used button will display the On state and show the appropriate icon. When another button in the same latch group is pressed, the first button will switch to the Off state while the new button displays the On state. With this setup, you'll always see which button is currently active. Please note that if the buttons are set to monitor Midi In, an incoming command that matches a button will activate that button and deactivate the other buttons in the same latch group.

The fader button is designed to display a mixer fader.

If two adjacent fader buttons control the same thing, meaning the Midi ports, command, channel, and control (if applicable) are identical, they will pair and synchronize their settings. The synchronized settings are shown with green labels. Changing a synchronized property will automatically update the same property on the paired button. When two fader buttons are paired, the fader display spans across both buttons.

If the fader direction is set to "Auto", the lower/left button will move the fader down, and the upper/right button will move it up.

The fader button(s) can optionally show a VU meter and state icons.

The fader button can show a VU meter linked to a MIDI control of your choice. The value sets the VU position if it is connected to a MIDI command with specific values (like CC or note). If it is linked to a MIDI command without values (such as Pitch Bend or Program Change), the control itself adjusts the VU position.

The full range of the selected MIDI command (0-127 or 0-16383) is used to set the visual VU level from 0% to 100% of the fader display size.

If the connected MIDI command does not transmit linear VU values, you can choose a VU scale to convert the received MIDI values into an accurate visual percentage. Currently, only a VU scale for Cubase is available because Cubase, for some reason, uses an exponential curve when sending VU values. Without selecting the Cubase VU scale, you will not see a VU display with levels aligning with what Cubase shows in the mixer.

The VU meter settings are synchronized across paired fader buttons because the VU meter covers both buttons.

The fader button can show a state icon linked to a MIDI control of your choice.

You can choose to display both an On and an Off icon or just one of them. The size and position of the icon can be freely adjusted. For example, you can have a small icon that shows both states or a large mute On icon that fills the entire button when the mute state is active.

Each button in a paired fader setup has its own icon, and the icon settings are not synchronized across the buttons.

You can make some visual tweaks to customize the fader display.

You can colorize the fader handle. The results vary depending on the image used for the handle; if it’s a very dark handle, you should colorize it with an opaque color that covers the handle image. If it’s a light handle image, you can use a more transparent color, allowing some of the handle’s characteristics to show through.

You can add a handle shadow for a slight 3D effect. If you prefer a flat design, you can remove the shadow.

Handle tweak settings are synchronized between paired buttons so the handle looks the same on both.

You can colorize the info area (also known as padding) in any color you like. This setting is not synchronized between buttons, allowing different colors on paired buttons.

In addition to the options in the visual tweaks section, you can modify the font, size, color, and attributes of the text in the info area using the Stream Deck editor's title configuration. The default settings are applied to the text, and as long as the Stream Deck editor settings are unchanged, the design file's settings are used. This can be somewhat confusing because the settings used might not match what is shown in the Stream Deck editor settings.

The default settings for the Stream Deck are shown in the image.

• If the font option is "Default," the font specified in the design file is used; if the font is changed, the font in the Stream Deck settings is applied.
• If the font color option is set to white, the font color specified in the design file is used; if the font color is changed, the font color in the Stream Deck settings is used.
• If the font size option is "12", the font sizes specified in the design file are used, and the text will be scaled to fit the available space. If the font size is changed, the font size set in the Stream Deck settings is used, and no scaling is applied.
• The "Show Title" checkbox and the vertical alignment options are unused and have no impact.

A cycle button relies entirely on a configuration file ("Translation file") that specifies the steps it should cycle through. Every time the button is pressed, it advances to the next item listed in the configuration file, sends the Midi value directly or glides to it, and displays the (possibly translated) value on the button and optionally shows a button image associated with that specific value.

A Cycle button displays a value as defined by the translation file. Each item in the list can have a unique display, including both text and image. Depending on the configuration in the selected translation file, the button can either jump to the next list item or smoothly transition to it with a glide or fade effect. Direction indicators can be overlaid on the button image. See the translation files for more details.

When a new Cycle button is created, it always starts on the first item in the configuration file and moves "up" (i.e., each press advances to the next item in the list).

The End behavior dropdown specifies what happens when the button reaches the last item in the configuration file.

• Stop means that no more increments are made; it remains "stuck" on the last item in the list. Each time the button is pressed, the same value is sent (as defined in the last item in the list).
• Loop means that it will loop around and start over from the other side of the list.
• Bounce means that it will change direction and go back through the list in the direction it came from.

If the translation file defines glidetime, glideuptime, or glidedowntime, the plugin will gradually fade or glide from the current value to the next over the specified period. You can pause or stop the glide by pressing the button during this time. Pressing the button again will resume the glide. Please note that to continue the glide from the current value, the parameter useclosestvalueonreceive must be set to "no".

The name "V-pot" is borrowed from the Mackie Control, where it describes a knob that can rotate. The function is similar to the Fader button, but the V-pot can provide clearer visual feedback when controlling a knob that appears in your DAW.

If two adjacent V-pot buttons control the same function, meaning the same Midi ports, command, channel, and control (if applicable), they will link and synchronize their settings. The synchronized settings are indicated with green labels. Adjusting a synchronized property will automatically apply the same change to the paired button.

If the rotation direction is set to "Auto", the lower/left button rotates counterclockwise, and the upper/right button rotates clockwise.

Scrub wheel buttons have most of the same features as V-Pot buttons. While a V-Pot button has a limited rotation range and sends different values depending on its position, a Scrub wheel button is endless and always sends the same value. 

For Scrub wheel buttons, the following additional fields are available:

Scripted buttons lack editor properties except for the script (inline or loaded from a file).

Scripted faders and V-pots share many display properties with their unscripted versions but lack any MIDI configuration.

Unlike the unscripted versions, the plugin cannot automatically pair adjacent buttons because it cannot determine if they control "the same thing." To pair a couple of scripted fader or V-pot buttons, you need to manually assign the "lower" and "upper" button roles. When two scripted fader or V-pot buttons are paired, the script must be assigned to the lower button, and that script will control both buttons.

When the button is pressed, the basic behavior for scripted faders and v-pots is to...

1. Move the fader/v-pot.
2. Tell the script the control has moved and its position.
3. Repeat the above as long as the button is pressed.

If you have a situation where you don't want the visible fader or v-pot to move automatically, you can set the speed to 0. In this case, the script will only receive a single notification when the button is pressed; the rest is handled by the script.

Among other things, the scripts can modify the assigned button design and speed, which results in changes to the properties in the editor; these changes are then saved in the button configuration.

The plugin doesn't consider the file extension for script files, so you can use any extension that works best for you. However, I recommend using ".midiScript"; it is unique, clearly indicates the file's purpose, and supports automatic syntax rules if you use the Notepad++ plugin or the VS Code Midi plugin extension.

Please refer to the script pages for a complete list of features for scripted Generic Midi buttons.