WARBL Forum

Okay, thanks—it sounds like Chrome is sending an initial connection command to the WARBL but nothing after that. This might be tricky for me to debug because I don’t have Android or Ubuntu, but hopefully with your help I’ll be able to get it sorted. I’ll dig into it tomorrow.

Oh, by the way, are you connecting directly by USB or are you using a hub, BLE adapter, etc.?

Direct USB cable connection

When you have a minute, could you try this link instead of the normal Config Tool link?:

https://warbl.xyz/configureForApp.html

That's the version that we use with the iOS app, and it uses a simplified method of detecting the WARBL. If it works it will help me figure out what's going on with Chrome.

Yes, that worked. I was able to configure and unconfigure the 'force max vel' , and the LED worked when setting were changed, and when changes were written
It worked on both Ubuntu/Chrome and Android/Chrome.

One thing I noticed was that with the new config screen, if you're on inst 3 and you hit the disconnect button, the re-connect, inst 3 is still selected. On the previous version, it defaulted to inst 1.

Thanks for your fast work on this - must be getting late over there!

Gonzo

Thanks! The correct behavior should be that unless you unplug the WARBL, it should remember the current instrument. So, if you disconnect and then reconnect, the instrument should stay the same (e.g. instrument 3 in your example above). If you unplug the WARBL and plug it back in, it should go to whichever instrument is currently selected as the default.

Could you try the normal Config Tool link again? You will have to hard-refresh the page using ctrl-F5 (which should work on Linux as well as Windows) to make sure the changes to the JavaScript get loaded. I made some changes that may make it easier to find the MIDI port that the WARBL is on.

Yes, that seems to work correctly. It detects the "force Max Vel", is able to set it, and the LED on the instrument flashes at each change.

Thanks Andrew.

Gonzo

Okay, great! The issue seems to be that the new Chrome on those particular platforms uses a different name for the input MIDI port and the output port, which makes it a bit tricker to find out "where" the WARBL is. Just let me know if you have any further issues with this.