So I set the “No Overlay” to “MPE XYZ Pad”, Set X -> CC1, Y -> CC2, Pressure -> CC3, Threshold -> 0, and enabled Absolute X & Y, 14-bit CC, and Recenter CC. Using a “Processing” sketch with The MidiBus library and some basic MIDI byte-dumping print statements, with the Morph plugged in via USB I used multiple fingers on the Morph and could see the contact ID, X & Y location, and contact pressure being continuously streamed. So the Morph can definitely format the desired multitouch data into a MIDI/MPE format.
However when using the BLE interface instead of USB I see 3 MIDI messages each time when I remove a “contact”/finger from pressing, and no other data besides that. And that’s with an unchanged No Overlay configuration. Additionally, the wifi for the computer was turned off, and the Morph was right next to the computer - so I wouldn’t expect interference to be causing any problems. Especially since there were always the 3 packets that were received.
And in case it’s of any help, only the last byte/parameter of the third byte had any variation (for single contacts). Multiple contacts were detected and given unique IDs, however those too would only send their three MIDI messages when each contact was removed.
Is this the expected behavior of the Morph in an MPE mode over Bluetooth?
If there are any additional tests/diagnostics that I could do to help identify the problem, assuming there is one, please let me know. It would be awesome to be able to use the Morph cordlessly as-is without having to build a data-path hardware workaround.