Start a new topic
Discussions embodme Forums General Q&A
Answered

Erae 2 Touch issues

I received my unit last week and having these issues:

1 - Encorder doesn't select options on the display

2 - Sensitivity is really bad. I need to hit the pad really hard to get detected so this just makes it unusable for me as you can see in the video.

I already updated it to the last firmware 1.03 and I'm running on the supplied power supply.


Also opened a support ticket and waiting for a reply.


Anyone else having some of these issues?


Video of the issue: https://drive.google.com/file/d/1RCDXR2Xwx4lia-Gdf-kQcvR7bdHuRH1-/view?usp=sharing

Best Answer

How is this "internal test" ran to check the hardware?

2 people have this question
38 CommentsSorted by Oldest First

Holding down Arp and Loop and turning it on never gets me to this test. My Mac says the unit is supplying to much power and thus turns off USB. I plug in other devices via USB to the Mac without issue. 

Gregg: arp + loop + - (the third one is  the MINUS key) ;)

2 people like this

MIDI USB test running for quite some time. Anyone understand what the result should be? I wonder: is there a complete reset of the unit that might fix the issue I have?

@Daniele my result failed also, with a similar error at i:4 j:10 max: 0.212

So you might want to reach out to support to check if you device is also not behaving as it should.

I just swapped the fabric surface for the "silicone drum pad one", and the sensitivity is  remarkably improved! The mooshiness of the fabric surface clearly gets in the way of sensitivity.

Agree with the above - sensitivity is a bit too low for me with either skin, seemingly no option to adjust.

I'm also getting the test error on latest firmware.


Hoping this is a software fix and already on the dev's radar.

TBH looking at the campaign again I think the fabric layer has been made far too thick. The prototype looks thinner and is clearly way more sensitive.


Hello everyone,


A quick message here to address the few issues :


CV stability :

We have found this week an FPGA related bug that would vause those CV instabilities. It was a though one to catch because it was highly dependent on the FPGA batch! You should now experience drift free and stable CV output.


Sensitivity : 

The slicone skin feels indeed a bit more sensitive, because it deforms less under pressure, i.e the force is directly transfered to the sensor surface below. The fabric skin has exactly the same depth as it was during the kickstarter video !

The force treshold should feel quite natural, if it feels hard to trigger at some position on the surface, this is not normal, please reach out to us so we can troubleshoot it, it might be a hardware issue, we've had a few one so far in the batch, and have been actively fixing it for those concerned !

Regarding the continuity while sliding, we chose at release to not implement an adaptive filter because the contiuity was much better that our previous version. But FSR technology being what it is, we will never reach perfect continuity, we will re-implement that filter in the very near future to improve z stability during slides. Also, as some of you mentioned, the pressure/velocity value does not remove our anti-false positive treshold, which is a very easy fix, again on an upcoming update. 

We also have hard-coded said anti false-positive value, which was not the case on erae 1, we might come back on that decision because in very controlled environment this will reduce the minimum treshold required without risking false positives.


Test procedure :

The test procedure is an internal factory test that should not be run by users, and besides, it was a bit bugged so it gave us false flags ! Sorry for telling some of you to run it, we were a bit overrun at the beginning of shipment and thought it would be useful ... it was not, that's on us !


Thank you very much for your early feedbacks, we will do our best to address those issue as efficiently as possible, handling 1000 products in a month was clearly one of the most challenging thing we had to face so far with our small team !


Cheers,

Mathieu

3 people like this
I received my unit today - and besides the rotary knob hangs a bit when pressing, it is a joy to play the erae2 - its not super sensitive, but enough - did not try the silicone yet . Has potential to he the coolest midi controller i owned so far ( and i owned them all!)- much love to your Team, you can do it!

Mathieu: Just got my Erae, updated the firmware (1.0.5) but the CV outputs are completely useless because of heavy CV drift / instability and gate crashes. This FPGA related bug is yet to be fixed in a firmware update? 

Hi Luis,


We made another update you can download that should fix some new found bugs on the CV stability:

https://www.embodme.com/downloads


Let us know if that worked for you ?

what does the "x" in xsafe and xsensitive mean? Extremely safe, or extremely sensitive?

Hello, thanks for getting in touch. Since firmware 1.0.6 the gate issue was fixed. With firmware 1.0.7 there is still a +- 3 hz constant variation as shown in the attached video. 

mp4
202502141133...
(4.26 MB)

Addendum: So i tried the sensitivity options and Xsensitive makes it drift a lot and Xsafe makes it drift less, like in the previously attached video.

Hi there, X means extra ! @luis the maximum drift is about +-3mV or around 1/12th of a semitone. So 3Hz at 600Hz is around what would be expected! However the sensitivity parameter should not affect it, Except if you have vibrato or glissando enabled on your keyboard. Cheers, Mathieu
Login or Signup to post a comment
More topics in General Q&A
See all 106 topics