- Ensure multiple devices are handled properly. Notably, one issue I'm having is that G-Stomper only sends MIDI signals itself to the last connected device, the one shown in the MIDI setup. This often leads to issues for me such as no MIDI clock being sent to the correct MIDI device, and lesser issues like drum pads not being lit up on play because the MIDI Note messages are only being sent to the keyboard and not the controller with the pads.
- Map devices to MIDI Interfaces. It would be very useful if I could treat my keyboard and my controller as separate MIDI Interfaces despite both sending on Interface 01. I could, for example, control the VA synth with the keyboard and the sampler with the controller/pads, without being limited to 16 channels for both combined. It should be possible to make this distinction and map devices to interfaces virtually, because G-Stomper can already tell the devices apart (notably by name, but I imagine a more stable distinction can be made by, say, ALSA card, though I don't really know Android programming myself).
- Allow configuring devices (and/or interfaces) separately. Not critical for me but follows naturally from the rest, I think. For example, I might want clock and note messages sent only to the controller and never the keyboard. In my case it doesn't really matter, unless there's a noticable performance impact to sending these messages to all devices?
FWIW, my current rig consists of a Nexus 7 (2013) on Android 6 with an Arturia BeatStep controller and a CME Xkey keyboard, connected using a powered OTG hub.