Same her, after couple of weeks of usage suddenly "SD Read/Write error". I have not done anything with the SD card, it just sits there since it came. Any solution please?
Kinda of a bummer as you can’t rely on the product for live gigs right now. Although it’s definitely made for that use case.
You can’t come to the gig and have to resend your layouts randomly.
I hope it can be fixed by firmware and that it will be.
@Arjan maybe a format with zero-ing out could help, but ultimately as you will rewrite on it, I guess you'll end-up in the same issue.
My guess is Embodme kinda struggles to get the sdcard driver work properly on this unit. I've seen other manufacturers struggling with that and having to update firmware several times to make it more stable.
To name a few 1010music, Isla Instruments, Polyend and Sonicware have had similar sdcard related bugs.
So hopefully it is nott a hardware issue.
I too have that SD card R/W error thing, it's not predictable. More often, when It starts up, it doesn't show up as a MIDI device, but a few restarts makes that happen.
I can save the 8 "projects" in storage - which I assume is on the SD card , but still, that's only 64 layouts out of what could be hundreds. assigning them on the fly to buttons via MIDI (Program Bank + Program change) would be good. Saving loop data on the card would be nice too - or even letting you set that up in the ERAE lab or via the API.
I'd also like to name those projects using ERAE Lab! Remembering what's in Project_3 or whatever is not easy!
Just a heads up. Meanwhile I grapped some old sd card I had laying around, formatted it, and slapped it into the erae, and boom: no read and write errors anymore and it booted fine the last 10 attempts or so.
So maybe, some of the shipped sd cards are just faulty.
It's a transcend microSD HC, class 10, with 32GB capacity.
It's been almost a month since the last fw update. If the pattern since release continues, then hopefully we will soon have another update finally squashing those issues and moving forward !
I understand that code can be unperfect on release, but these switching on/host recognition and sdcard r/w issues are very handicapping for serious use of the product.
I didn't dare using in one of my gigs in June because of this. The ERAE 2 has a lot of potential but stays in "lab mode" for me so far.
I'm optimistic though as this seems to be typical hard to squash firmware stability issues.
At the advice of Embodme in a comment on social media, I've formatted the SDcard to see if things improved.
For now it does look like yes (for reminder I run v1.10). I tried to switch off/on several times and it has never showed me the sdcard r/w and my previously saved project always loaded.
The only thing I'm not sure about (and that may actually be part of the initial cause) : the Embodme provided sdcard was formatted as FAT32. Whereas I formatted with SD Card Formatter tool as exFAT (with Overwrite mode).
Could that be that initial firmwares only supported FAT32 hence the shipped SDcards were mistakenly formatted in FAT32 ? Maybe now it is optimized for exFAT and I know that FAT32 SDcards can be capricious to mount sometimes even on a computer.
It's maybe too early for conclusions right now but things look way better for now, I will keep you posted.
Alexandros Roussos
Since I received my ERAE 2, there has been a lot of enthusiasm for the product but also a lot of bugs, many of which have been fixed in firmware updates that followed (notably touch sensivity, CV instabilities, boot issues).
One that has never been, although almost systematically being mentioned in the fw release notes, up to the one that was released recently at the moment of this post v1.10, is the behavior of the sd card reader.
In the beginning, my feeling was that the scard prevented the unit from booting (the unit booted with it ejected), then this was partially fixed but with sometimes losing the layouts after reboot. Then in v1.10 boot seems to be working systematically.
However, about 50 to 70% of the time, I now see a message during the boot phase saying scard could not be read. And when that happens (most of the time), the unit boots with the factory layouts.
So I don't know why it is so hard or if it's an actual hardware issue that Embodme is trying to patch using firmware updates but the sdcard slot on the ERAE 2 has been useless so far.
Other than the bugs, it's actually quite curious why the ERAE 2 has an sdcard because it can only store 8 projects and you cannot load additional projects from the SD in standalone mode. You can only do this through the ERAE 2 Editor application.
The unit ships with an 8GB sd if I remember correctly so technically we could have stored thousands of projects and looper sequences but right now we cannot even store our basic 8 projects on it. All my test were done with the stock scard by the way.
There's definitely something to do about the sdcard reader/storage management on the ERAE 2, be it in terms of bugs or actual functionality.
Am I the only one facing difficulties with sd card storage or is the issue more widespread ? If I am the only one, then maybe it's the sdcard that shipped with my unit that is faulty. Embodme does not provide clear answer on sd card compatibility for this unit so far so I haven't tried any other.
Although the biggest problem right now is the bugs with the sd reader, I post this on feature requests because this should definitely include more functionality like storing full 8-project sets/backups or provide ability to browse manually load projects from the sd to the ERAE 2's 8 project slots.
1 person likes this idea