OSD Names

YinAndCheesecake

When assigning multiple items for one knob (eg. Chrome & VLC), OSD gives 'K6' (name of knob).
Potentially allow the option to add custom text / override OSD name?

Low priority.

GiacoAV

You can freely change the name displayed on the OSD by changing group names like shown bellow.
It even supports emojis ! 😉

Jack

The OSD sort of accidentally does this. 👀

If it dumbly detects that only a single assignment is present on a fader then it'll show the assignment's name, whereas if more than one assignments are present it'll show the fader's name.

For most people, the fader's name is always shown as this dumb check also counts any inactive assignments (e.g. apps that aren't open, old app .exes, old devices, or old plugins).

The "Extendable OSD" milestone is one that should make this behaviour a tad more customisable.

https://forums.midi-mixer.com/d/3-extendable-osd

meghanmarkel

Jack The OSD sort of accidentally does this. 👀

If it dumbly detects that only a single assignment is present on a fader then it'll show the assignment's name, whereas if more than one assignments are present it'll show the fader's name.

For most people, the fader's name is always shown as this dumb check also counts any inactive assignments (e.g. apps that aren't open, old app .exes, old devices, or old plugins).

The "Extendable OSD" milestone is one that should make this behaviour a tad more customisable.

https://forums.midi-mixer .com/d/3-extendable-osd

Can I ask something about it ???

nolevm

You're absolutely right, having the OSD (On-Screen Display) simply show the knob name can be limiting when assigning multiple items to it. Custom OSD names would definitely improve usability.

Here's a possible approach:

Custom Text Entry: Allow users to enter a custom name for the OSD that appears when the knob is adjusted. This name would override the default knob name and provide clear identification of the assigned items (e.g., "Volume (Chrome & VLC)").

Presets or Templates: Provide a set of pre-defined names or templates that users can choose from. These could include generic options like "Multiple Items" or "Custom 1win apk" along with more specific options relevant to the software (e.g., "Audio Mixer").

Combined Approach: A combination of custom text entry and presets could offer the most flexibility. Users could choose from presets for common scenarios or enter their own text for more specific configurations.

Implementing any of these options would require changes to the underlying software that controls the OSD. But the benefits in terms of clarity and user experience would be significant.