Transient note filter not saving

[admin]

One other thing that occurred to me about Ubuntu:

That fix that I made to the Config Tool last week looks for the name "WARBL" as a fall-through if the normal method of identifying the correct MIDI port doesn't work. So, if the name of the MIDI device hasn't been set to "WARBL", then it won't work. Because you're using the IDE instead of the normal method with the compiled firmware you also have to make the product name change outlined in the README. If you've done that in the past and then the IDE or board package has been updated, you'd need to do it again.

If it's easier to just send me your fingering chart .ino I'm happy to compile the code with the correct product name, CDC turned off, correct current consumption setting, etc.

[waltercool]

Hi,

My step-by-step to upgrade the firmware "from code" at Linux. I use Gentoo, it might be easier on Ubuntu since it's user friendly.

1) Use Arduino IDE (AppImage version works fine, just like Mac OSX apps)
2) Configure Adafruit ItsyBitsy 32u4 3V 8MHz. https://learn.adafruit.com/introducting ... -ide-setup
3) Load the 3 files contanining fingerings, main code and functions.

Now, don't upload from Arduino IDE because the window is too short and might be frustrating.

4) Do "Sketch/Export Compiled Binary"
5) Check the folder warbl_firmware (where code exists), get the file warbl_firmware.ino.hex from build/adafruit.avr.itsybitsy32u4_3V/

6) Download and configure qml_cli. This is not easy at Gentoo, but might be at Ubuntu. Usually "pip install qmk" does the job fairly good, then "qmk configure" https://docs.qmk.fm/#/newbs_getting_sta ... allation-2
7) Just run "qmk flash warbl_firmware.ino.hex", make sure you are at the same folder containing warbl_firmware.ino.hex. It will wait for device.
8) Push the WARBL reset twice to enter flash mode while connected to computer
9) Flash done.

If you are just flashing a pre-built binary, just start from step 6. No need to deal with code and stuff.

[admin]

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

[gonzoB]

Ok, I think I've identified the problem. It's probably related to the MIDI port name as mentioned above.

The configureforApp works fine with Ubuntu, but there's no import/export function

The configure.html is the problem with Ubuntu (presumably because of the port name), and the export function doesn't work (again, probably because of the port name)

That link to the "change the name" thread goes to the thread about the max velocity. You didn't mean that??

I'll persevere and figure out how to change the port name - is it case-sensitive?

I didn't have the CDC change set up. but I'm running IDE 1.8.6, so it probably doesn't apply

Gonzo

[admin]

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 the name is case sensitive.

Again, if you don't want to have to change your setup in the IDE I can just compile your code for you since I've already made all those changes.

[gonzoB]

Ok, Thanks Andrew for the compiled version with my fingering file.

Thanks for the qmk HowTo, Walter. I loaded the hex file with qmk (after finding out about the "qmk setup" step).

Result with Ubuntu/Chrome and the "configure.html":
It behaves exactly as the version that I loaded via Arduino IDE. The symptoms are:
- The LED flashes on clicking connect and disconnect
- the LED doesn't flash when changing settings
- the LED doesn't flash when "save for this instrument"
- the settings aren't saved
- the Export button appears to do nothing until you click disconnect, then click Connect. The file is then saved, and appears to be OK when imported again.

However:
The "configureForApp" works perfectly (Ubuntu/Chrome), except that it has no Export/Import functionality

Meanwhile...the instrument is functioning perfectly.

Gonzo

[admin]

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 you, but it would probably be best not to use that firehose approach on all platforms.

[gonzoB]

I did some investigating using https://arachsys.github.io/webmidi/

Chrome on win10 the instrument shows up as a port called "WARBL"

Chrome on Ubuntu it shows up as "WARBL MIDI 1"

Does this help?

Gonzo

[admin]

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 Windows) are in the menu in the top-right corner, under "More tools".

Thanks!

[gonzoB]

How do I "try to connect to warbl"? I can't see any drop-down list or whatever.

Gonzo