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 Popular

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

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

FYI for CV pitch drift and pitch inconsistency, under  Expressivity Tune settings, try turning off  Vibrato.


For my device, while Vibrato is on, it injects random fluctuations into pad tracking. 

In addition,  'note on' and 'note off'  moments differ in pitch (which might have been coded as a feature?), but with strength turned up it makes melodic runs...challenging.


Forgot to mention, I'm running  FW   V.1.0.7-f7220ba8

I have the same problem. Very low velocity.

If this will not be fixed, together with user defined grids, the unit is worthless to me. Very frustrating.

I hoped Embodme finally was a company that realised that with this kind of devices ( and I own a lot of them ) the software is the atmost important. For the user, but also for them, because the software (internal and external) does make or break the product!

@Donbosse you are right, vibrato is extremely sensitive so if it's enabled it will make the pitch drift with the microvariation of your finger on the surface ! There might be some ways to improve it bysome sort of scaling that would make it cleaner.


@Sander which version are you on ? If you feel that there are clear pressure issue on your unit, please open a ticket with some content like a video that would help us identify the issue. User grid is quite niche and hard to implement, it would be a cool feature and it is defintely on our roadmap, but we focus on product stability first, I hope you understand :) You are absolutely right, software is key !

Being allowed to adjust the anti-false-positive threshold would be good.

@Mathieu: I will open a ticket. I’m on the newest version (with the sensitivity settings). A video doesn’t do much: the midi velocities are just very low (as I can see in a midi monitor) from usb- and also from midi out connection.

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 ?

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? 

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!

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.


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.

Login or Signup to post a comment
More topics in General Q&A
See all 134 topics