WARBL Forum

Pfew, great! The problem was that that MIDI Through port was bouncing messages back to the Configuration Tool, which thought it was the WARBL sending a response back. After that the Config Tool was targeting only the MIDI Through port. Maybe that port is just always open on Linux? Now the Config Too...

Great! Does it seem to be working correctly now (sending commands to the WARBL)?

Could you try connecting again now, after force-reloading the page (Crtl-F5)?

I added another fix to look only for a port that has sent a WARBL-specific CC message.

Thanks! Interesting-- it found an output port with same name as the port that it received a message from, so it thinks that that is the WARBL.

I'm not sure what that MIDI Through port is-- do you have any other MIDI apps open, or any other MIDI hardware connected?

Sorry, I wasn't clear: -Go to the normal Configuration Tool page: https://warbl.xyz/configure.html -Open the Developer Tools (as you have done), and click "console" -Plug in the WARBL if it's not plugged, and click "Connect" in the Configuration Tool There should be some messages...

Oh, sorry, navigate to the Configuration Tool (and click "connect" if necessary).

Yes, that helps, thanks! When you have a minute, could you please open the developer tools in Chrome on Ubuntu, click on "Console:, try to connect to the WARBL, and tell me what messages it shows in the console? It should list the input and output ports names. The developer tools (at least in W...

Okay, I’ll need to revisit that fix I made for the new Chrome version. I’m not sure why it was working previously and not now, but hopefully I can figure out a simplified method of detecting which port the WARBL is on. The app version just sends messages to all ports, which is why it is working for ...

Sorry, I was just linking back to the thread about velocity for Walter's sake so he could see that, and because I believe it's the same issue, but now caused by the incorrect device name. The instructions for changing the device name are in the README: https://github.com/amowry/warbl Yes, I believe ...

I think to allow for the fix in the Config Tool for Chrome on Ubuntu, you'll also have to change the product name to "WARBL" as mentioned above. Here's the thread about that Config Tool issue:

viewtopic.php?f=6&t=352&start=10