I just tested this and luckily the pressure value returns to zero in normal midi mode every time so I don't think it's a hardware fault. It must be something in the sysex values as a pressure release value of 0.4 would result in a CC value of 50.
I've got the latest firmware (1.0.9) and the sysex z data for the release action is consistently off. It even jumps up on release (screenshot attached)
Thanks for asking this as I would not have thought to test standard midi. Hopefully a firmware fix for this is released soon!
I have just heard back from Embodme support who have advised that this won't be fixed as z data on a release action is note-off velocity, even though it is also pressure data during the touch gesture.
So this is a feature, not a bug (in their words!)
Update:
Embodme support have just provided a solution if anyone else is trying to use API zone z-data in the same way you would use pressure in the Keygrid.
In the python code, add the following to force the z value to zero on a release action:
z = 0
erae_handler.finger_detection(finger_id, zone_id, action, x, y, z)
client.send_message("/pressure", z)
client.send_message("/x", x)
client.send_message("/y", y)
---
arvind
I've finally got high-resolution sysex data from the Erae 2 that I can use in a Max patch and I'm really disappointed by the pressure values it is sending.
When releasing a touch point, the value rarely returns to zero. Sometimes it is stuck as high as 0.4 if I have applied pressure to get it to 1.0 prior to releasing.
This is a serious issue and I need to know if it is a hardware fault or just a general issue with all the units.
Can someone from Embodme advise on whether there is a fix you are working on or if its possible to return the unit for repair or refund?
It has been 3 months since I received it but as the sysex API was only released recently, I have only just had the chance to properly test it. If it was like this out of the box, I would have returned it immediately.