WARBL Forum

I've just got the "Soundfonts" app for my iphone, as I wanted to try my breath-enabled soundfonts on it.

Turns out that the app doesn't respond properly to wind controller velocity - it doesn't allow the volume to go above the note-on velocity.

OK, says I, I'll force max velocity on one of the 3 Warbl instruments. Well, I can't. When I turn off the "send pressure as velocity" it enables the max velocity switch, which I turn on, and I save that for that instrument. However, when I look at the other 2 instruments, it's selected there too. Also, when I disconnect and re-connect, the setting (an any instrument) has not been saved.

I think it's a bug.

note: for configuring, I'm using Chrome on both Ubuntu Linux, and on Android. Same results.

Gonzo

Interesting-- I don't seem to be able to reproduce this, but I'll have more time tomorrow, so I'll try again then. Do you have firmware v. 2.1?

In the meantime, you can produce a similar result my mapping a very low input pressure to a very high output velocity.

The maker of the SoundFonts app may be responsive if you let him know about the issue with that-- I've made a few suggestions that he's incorporated in the past year or so. It's still a fairly new app and he seems to be interested in improving it.

Yes, 2.1, but with a custom sax fingering chart.

Gonzo

Found the problem.

I tried re-loading the firmware via Arduino IDE - no change, still wouldn't work

I then fired up a Windows 10 machine I have, and the program changes worked using Chrome. It sounds like a Chrome problem.

The version of chrome I have on the Ubuntu machine is
119.0.6045.159 (Official Build) (64-bit)

The one on Android (7.1.1) is
119.0.6045.163

The Win10 version is
118.0.5993.118 (Official Build) (64-bit)

I noticed when the "Instrument Update" ran (and the change failed) the LED on the Warbl didn't come on.

"Soundfonts" is now working with fixed max velocity.

Gonzo

Okay, interesting! Does the rest of the Config Tool functionality seem to work on Ubuntu and Android? It sounds like for whatever reason Chrome isn’t sending any command to the WARBL when you toggle that switch. I’ll look to see if there’s anything different about that particular one.

I tried changing a few things and nothing would "stick". It appears that this version of Chrome will read the instrument OK, but will not write to it, so maybe the MIDI out is a problem...???

Gonzo

Eesh, not good. I’ll see if I can find anything about this tomorrow.

Does the Config Tool say that the WARBL is connected, and does the LED on the WARBL blink when you first connect? It’s possible that the method we use for detecting that it’s a WARBL and not a different MIDI device isn’t working with this new version of Chrome for some reason.

Yes, the LED flashes on connection, the version is reported correctly, and SOME of the stored settings are correct. It didn't read the velocity setting stuff, but did read things like the pressure maps, fingering selection. Most things appear to be read.

Gonzo

Okay, when you try to change settings, does the LED on the WARBL ever flash?

I'm using 119.0.6045.160 on Windows 11 and that also seems to be okay.

No, it doesn't flash on setting changes.

It does with my windows machine.