Im guessing the firmware websites ‘new features’ are mislabelled as 1.1.1 (and are 1.1.2), but copy pasted as is from website.
edit: Embodme have corrected website, updated post
not many new features, which is ok (for me), I like to see stability updates etc.
good to see they are continuing to focus on the sdcard ‘issues’, which still seem to plague some.
I’ll probably update later today…
whats your experience?
ofc, the elephant in the room is… where is the Erae 1 update?
even as a Erae 2 owner, this makes me nervous how they didnt really keep up their promise for the Erae 1 owners.
also, why oh why, does Erae Lab have two versions, rather than one that works for both models.
Hi, I have installed the update but after a while there is errors in layouts uploads, duplicates and wrong presets.
Reverted to the previous one and the problem is solved. So I will wait for next update…
Yes! I’m having this same problem. Push from Erae Lab to Erae2 is unreliable and buggy. Reverting to 1.1.1 fixes this, but then I don’t get my favorite new feature in 1.1.2, Retrigger!
Gosh I hope they fix this; there must be plenty of people with these things experiencing it.
It’s really a pain to make small changes to a Layout and then have to fight with the thing when it won’t Push those changes.
Still quite new to this device and excited but yet disappointed since having the same issue with 1.1.2 / 1.6.2. Not only push is buggy, pull as well receives different data than initially programmed (seen in pressure type, when set to poly it initially works but is read back as channel).
I tried firmware downgrading and it improves on push (pull issue persists). But latest FW allows DAW and Lab concurrently which improves turn around times so much when playing with the device that I do not want to miss it.
So as current workaround I keep my layout sources on the PC and switch on preview in Lab. When cycling through all 8 layouts or applying small changes, it seems to take over everything and when storing the project in Erae it appeared to work as far I checked yet.
But this is far from being comfortable and needs urgent fixing.
Thanks for your suggestion. I directly contacted their support by mail prior to writing here. Will issue a ticket on their forum next time or if I do not get any response.
Unfortunately I have not found a public issue list on their site yet.
As a FYI: I am also having problems transferring a layout from Erae Lab to Erae2.
However, it works if I select a different layout on the Erae before transferring.
B.T.W. Does anyone know how the finger stream messages from an API element are exactly structured? The available documentation on this topic is unclear to completely wrong. I’ve spent hours on it and almost got it working, but I still sporadically get values that are only half as high as they should be.
Why, oh why did they make it so complicated?
I updated my api (to latest erae api spec) a few weeks before Christmas for some stuff I was working on.
you can find it here.
seemed to be working fine, though I’ve not done final testing on the project Im working on that uses it.
basically v2 made a change to the way the finger id is presented (iirc, it was. a few weeks ago ;)) - the docs are correct, but it did take a couple of reads
…thanks, technobear! I’ll take another look at it.
Maybe I’m just too stupid to really understand it. So I just kept trying and trying and trying … Often enough that works, not this time though
what Ive not checked, is if the Erae 1 latest firmware conforms to this ‘new spec’ (as spec implies it works with both) OR if it was intended that (Erae1) would be updated at some point in the future.
in which case, I’ll have to ensure my api works for both the older and newer version of spec… not a big deal, but its always nice to remove redundant code.
I had exactly the same problem but I can’t quite remember what the issue was. I think it was to do with incorrectly unpacking the 7bit values. Make sure you’ve converted the 7bit pack/unpack functions in the API docs precisely to whatever language you’re using.
Then its:
data[2] & 0x07 = Finger Action: 0 = down, 1 = move, 2 = up
data[3] = Zone ID
data[4-13] = Finger ID: unpack to get 8 bytes, convert to 64 bit unsigned int.
data[14-27] = XYZ: send the entire XYZ data to the unpack function, it returns 12 bytes, 4 for each of XYZ, convert to float.
Thanks, moonfold! Yes, I think so too. Unfortunately, I don’t program in Python or C, but in ClassicVisualBasic (don’t laugh).
I’ve given up for now, but maybe I’ll try again when I have more time.
It’s been awhile since I’ve used my Touch II and I went on the website to troubleshoot today while I was going through some tutorials and new setups for my eurorack and they have a most excellent AI chat help system set up now. it was fantastically helpful. Every time I hit a roadblock, it was able to immediately tell me exactly what the most likely cause was. I was (obviously) very impressed and it’s really made me appreciate my Touch II more.
