You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MIDI controllers do not have consistent names on all platforms. This is problematic for bespoke because controller json configurations rely on the name of the device to know which configuration to auto-load, so configurations will only auto load if they are loaded on the correct platform. I discovered this when I connected my launchpad X on windows and discovered that its name was different from what it was on linux.
Linux
Windows
To resolve this, I propose that something like a names array is added to the midi controller json files that contains an array of midi controller names. This can then be used to lookup device names and more accurately match them to layouts. Additionally, it might let us have more sensible names for some of the json files.
MIDI controllers do not have consistent names on all platforms. This is problematic for bespoke because controller json configurations rely on the name of the device to know which configuration to auto-load, so configurations will only auto load if they are loaded on the correct platform. I discovered this when I connected my launchpad X on windows and discovered that its name was different from what it was on linux.
To resolve this, I propose that something like a
names
array is added to the midi controller json files that contains an array of midi controller names. This can then be used to lookup device names and more accurately match them to layouts. Additionally, it might let us have more sensible names for some of the json files.Build: f82acc4
The text was updated successfully, but these errors were encountered: