kanduvisla wrote:What is a good midi monitor? I tried the following one, but it does not seem to work. Also it hasn't been updated since 2013, so I think that might also be the case:
https://play.google.com/store/apps/deta ... idimonitor
Generally, I think the one you've used is good : https://play.google.com/store/apps/deta ... idimonitor
But like Caustic for example, it uses the old USB host approach.
This one (MIDIScope) is written by the creator of the Android M MIDI API, and it also uses the new approach.
https://play.google.com/store/apps/deta ... .midiscope
It might either give you the same results, or maybe more details. It's definitely worth a try.
kanduvisla wrote:So the only option now left is to check with a powered usb hub, but I don't have one is those and I doubt if that is the case, given that the controller works with any other app and also with the lights and such.
You might be right by having doubts about the power issue. Maybe I was wrong with my first assumption that it's not a bug in the app.
I checked the crash logs on Google Play, but there is not a single report. So if it's a bug in the app, then it results in terminating the MIDI receiver process without an error. Therefore the only way to find the problem would be to debug it. Unfortunately I don't have access to a Minilab MK2 to test with. But I'll drive some tests with a Beatstep Pro and Keystep Pro, to which I have access to. Maybe the Keystep sends similar messages when changing the octave.
I let you know if I'm able to reproduce the problem.
If you have any chance to try the same controller on any other device using the G-Stomper VA-Beast, that would be very helpful.