Page 1 of 1

Acer Chromebook 14 cb-431 midi crash

Posted: Mon Jan 07, 2019 6:24 pm
by bboissonneault
Hey guys

I'm stuggling to connect a midi device to the app on my Chromebook. I have an APC 25 and it works great on my Huawei Mate 10 pro, but when opening the app with the device connected, I'm asked if I want to use the midi device (twice to include the keyboard I guess) and the app hangs and needs to be terminated. If I open the app without the akai, I'm also asked about midi and I click yes but there is no device in setup. Is anyone else having this problem or does anyone have any advice?

Re: Acer Chromebook 14 cb-431 midi crash

Posted: Mon Jan 07, 2019 6:45 pm
by planet-h
Welcome to the forum, bboissonneault
and thanks for your report.

bboissonneault wrote:I'm stuggling to connect a midi device to the app on my Chromebook. I have an APC 25 and it works great on my Huawei Mate 10 pro, but when opening the app with the device connected, I'm asked if I want to use the midi device (twice to include the keyboard I guess) and the app hangs and needs to be terminated. If I open the app without the akai, I'm also asked about midi and I click yes but there is no device in setup. Is anyone else having this problem or does anyone have any advice?

I can reproduce the behavior on my Asus Flip Chromebook. It is clearly some chrome os problematic. For some reason, every device that has been connected over USB remains in the MIDI device list (outside G-Stomper). That's why it's reported twice by G-Stomper, or even more. You can try to answer either the first or the second one with No, as clearly only one will work.
The issue exists only on USB connections. When you connect over Bluetooth LE, all works as expected.
I'll give that a closer look this week and see if there's a way to get around it.

Re: Acer Chromebook 14 cb-431 midi crash

Posted: Mon Jan 07, 2019 7:35 pm
by bboissonneault
Thanks for the quick follow-up. I'll try "no" first then yes and see what happens. When I do not have my APC connected, I do still get the request which I assumed was for the keyboard. Does gstomper take the laptop keyboard has a midi device by default? When I click "yes" to the single request, nothing happens.

Re: Acer Chromebook 14 cb-431 midi crash

Posted: Mon Jan 07, 2019 9:00 pm
by planet-h
bboissonneault wrote:Does gstomper take the laptop keyboard has a midi device by default? When I click "yes" to the single request, nothing happens.

Not G-Stomper, but maybe the underlying MIDI API. I don't think it recognizes the laptop as a MIDI device. I rather think it's the Chrome browser, or the MIDI API thinks that G-Stomper is a MIDI device (which it is clearly not). I'll go after that.

Re: Acer Chromebook 14 cb-431 midi crash

Posted: Tue Jan 08, 2019 10:38 am
by planet-h
Can you please tell me what Chrome OS version you're using?

Re: Acer Chromebook 14 cb-431 midi crash

Posted: Wed Jan 09, 2019 4:29 am
by bboissonneault
Chrome: 71.0.3578.94
Platform: 11151.59.0
Firmware: Google_Edgar.7287.167.132

Re: Acer Chromebook 14 cb-431 midi crash

Posted: Wed Jan 09, 2019 9:27 am
by planet-h
Thanks a lot for the info, bboissonneault.
I filed an issue in the android-midi google group.
I'll keep you posted.

Re: Acer Chromebook 14 cb-431 midi crash

Posted: Thu Jan 10, 2019 2:03 pm
by bboissonneault
Thanks for the help

Re: Acer Chromebook 14 cb-431 midi crash

Posted: Thu Jan 10, 2019 3:57 pm
by planet-h
bboissonneault wrote:Thanks for the help

No problem. That's what support is for;).
It appears to be a bug in the latest Chrome OS version.
The guy who is responsible for the MIDI API at Google passed it on to the Chrome OS development team.
So there's a good chance that it'll be fixed soon.