Open GriffinSauce opened 2 years ago
Planned for implementation after the "Profiles" feature milestone as the API doesn't have room for additional command meta-data.
Cool, is the plan to allow arbitrary meta-data ?
That would be exciting, it would allow for all kinds of reversible abstractions!
Yeah that's the goal, still on the drawing board at this stage though.
Note: this is a feature request.
Issue After selecting a command through the device library, the raw midi message is added to the config and the context from the device library is lost.
Example
Control Change - [Ch: 1] [Controller: 49] [Value: 127]
is addedDesired/expected outcome
This way you can see what the message is actually doing and modify it in context. (in this example, change it to HX Stomp FS2 for example).
Right now the feature inserts a midi message and your options to modify it are:
... assuming that you even remember which message is which later on. ;)
I think maintaining the abstraction of the device library would make a massive difference in the user experience.