Both the video and the GIF show the incoming MIDI notes when the status bar messages aren't visible. You have looked at it, but you haven't seen it.
The video shows how quickly I can adjust a Kit's parameters. It allows me to compare parameter differences—both by ear and visually—while editing on the fly.
A task that took me 5 minutes would take at least half an hour using the Element List, simply because I’d have to visually hunt for the element by scrolling up and down, not to mention the frequent errors where you start editing a selected element that isn't the one you actually thought was selected.
It doesn't run unless you want it to. I initially thought about making it a configuration option, but it actually makes more sense as a "Select by MIDI" button, since it acts as a selection and editing aid. There's no need to save its state in the settings; you just toggle it on when in edit mode and off when in play mode. It loads in the "off" state by default. It's even simpler to implement that way.
There isn't even a performance drop—or if there is, it doesn't matter, since the feature isn't active during playback.
You wouldn't recommend it? Why not? There are no downsides, only advantages. You didn't bother watching the video closely, let alone trying it out yourself... in a quick build. You'd only need to add one line of code to test the concept.
You simply don't like it, and that's that... fair enough. There's no arguing with personal taste.
Both the video and the GIF show the incoming MIDI notes when the status bar messages aren't visible. You have looked at it, but you haven't seen it.
The video shows how quickly I can adjust a Kit's parameters. It allows me to compare parameter differences—both by ear and visually—while editing on the fly.
A task that took me 5 minutes would take at least half an hour using the Element List, simply because I’d have to visually hunt for the element by scrolling up and down, not to mention the frequent errors where you start editing a selected element that isn't the one you actually thought was selected.
It doesn't run unless you want it to. I initially thought about making it a configuration option, but it actually makes more sense as a "Select by MIDI" button, since it acts as a selection and editing aid. There's no need to save its state in the settings; you just toggle it on when in edit mode and off when in play mode. It loads in the "off" state by default. It's even simpler to implement that way.
There isn't even a performance drop—or if there is, it doesn't matter, since the feature isn't active during playback.
You wouldn't recommend it? Why not? There are no downsides, only advantages. You didn't bother watching the video closely, let alone trying it out yourself... in a quick build. You'd only need to add one line of code to test the concept.
You simply don't like it, and that's that... fair enough. There's no arguing with personal taste.