I would love if someone can confirm wether the loop quantizer works in the latest version (2.0.82). It’s not working here. I tried every type of element and am recording notes and sending gates, but the quantizer seems broken.
I hadn’t used it much lately, but I seem to remember that it did work at sometime in the past.
Also, while we are at it, Erae Lab stopped pushing my layout automatically and there was no way to force push it. Rebooting my computer fixed it.
yeah, its not quantising on either record or playback.
I reckon it likely has to do with the rework we talked about on the other topic…
remember on here I said
I had a look at the manual, and it shows “11.14 Looper Settings Screen”.
though, oddly, I don’t remember these (though could be wrong)
that’s now completely disappeared…
on a brighter note… Ive just noticed they added the (missing) finger data rate the api zone in 2.0.82, need to test to see if it does anything.
I’ve generally been doing some digging around in EraeLab and also the documentation, and I get distinct feeling they are in the middle of some dev work - as theres stuff, thats not being used/working or detailed fully.
Id not be surprised if 2.0.8x was pushed out, because they needed it for EraeSound, but some other changes that were in the pipeline were not ready.
… perhaps why we have some of these oddities surfacing.
its a shame, they are not giving us any indication / roadmap for future updates.
yeh, it’s really frustrating to go to record and something you’ve relied on is no longer implemented with no notice or notes from them about it. Weird.
Oh, lol. Just noticed that loop button indeed does nothing. Huh. I seldom used it, but not much, though, it’s a nice function. As thetechnobear said, i assume that they are working on some big update, as that’s what Embodme support has told me, when i created my bug reports about Erae. So far they told me about a new scale system with microtonal support. Fingers crossed🤞
in fairness, I think its a bug, hence why its not in the ‘change logs’… an unintended side effect.
just noticed 2.0.83 has been released.
this might explain why I saw the manual change in the last 24 hours 
though no mention of this issue, but I guess worth retesting
one ‘good thing’ about these automated updates is, I suspect its easier for them to package/distribute updates - so perhaps cadence of updates may improve.
yeah, theres a few things already in 2.0.x that have changed that look more about ‘future updates’, including differences in the way things are structured/delivered - but a lot are ‘incomplete’
e.g. the midi 2.0 option is neither documented, not complete, and breaks things.
as above, I suspect whats happened is they had lots of changes in their 2.x dev branch, that were not complete, but then needed to release it to support Erae Sound - so they tried to ‘stabilise’ some bits of it/ removing bits that were not ready - but this broke some other parts.
its something as a dev you try to avoid, but does happen occasionally, esp, if you are releasing a new related product.
probably what excites me more, is they do also look like they are going to deliver on the Erae mk1 promise - something that Erae 1 owners have been patiently waiting on.
hmm… 2.0.83 does not update firmware
[Lab] EraeProtocolInterface: IdentityReply fw=V.2.0.82
[Lab] SyncManager: Vendor USB superseded legacy MIDI connection -- starting sync protocol
[Lab] SyncManager: Device connected
[Lab] SyncManager: Starting connection protocol
[Lab] EraeProtocolInterface: DIAG-D connection info: pid=0xdf05 midiMode=midi1 protocolVersion=3
[Lab] EraeProtocolInterface: Vendor USB reconnected, closing bootloader MIDI ports
[Lab] FirmwareAutoUpdater: Firmware update available
[Lab] FirmwareAutoUpdater: on-disk .syx build (0) is newer than the device but still behind Lab's own compiled build (1025) at the same major.minor.patch -- waiting for a matching .syx instead of flashing an intermediate nightly build.
Im pretty sure this is an error, as you need a valid file in case someone skips a version e.g. goes 2.0.81 → 2.0.83.
also the installed components, already has an ability to pin previous firmware version if that was the intent.
anyway, Id guess means we’ll see a 2.0.84 soon , to just fix this.
EDIT: posted on thier forum to bring visibility, though not sure how much they read it, as its not very active.
I’m hoping this silence doesn’t infer something about the company. They’ve always been so responsive in the past.
You’re kidding, right ? They have many qualities, but communication to users could be improved (understatement here)
Guess it’s been long enough that I forgot 
Though I have to say, they were very responsive at times.
yeah, 100% this…
I think for Erae 2, the updates / improvements have been pretty good (esp compared to Erae 1).
But their support comms is not very good at all,
they have their own forum, which they completely ignore for weeks/months on end - even though, its really low traffic, so would not be much of a support overhead to interact with.
I will admit their email response is ‘better’, they do respond
but all too often, its just a “yeah, thanks for the feedback, we consider for the future”.
overall, we are left in the dark about what they are actively working on…
I think this would not be so bad, if it wasn’t for the fact they spend a LOT of time on marketing communications and events - so it feels all about getting new customers, rather than supporting your existing ones.
for some reason, I think Erae Sound showed this approach rather clearly,.
selling a new shiny thing was a priority… and thats fine (they are a commercial company!)
but for me, I just questioned “why?” ,
the integration in Erae Lab felt like a pay-ware unlock,
for something Id not asked for, nor wanted.
but if they had involved the community, talked about their plans, the vision, and asked for feedback, perhaps early demo versions?
I think there’d be more ‘buy in’, and frankly, Id probably be more likely to have bought.
Finally heard back from Embodme:
"Thank you for your message.
The Loop button is actually unused because… it will be soon dedicated to a full new functionality!
The loop button itself was not really necessary and the loop menu appears by default. The update should arrive at the end the month.
Concerning quantize I tested it and yes it seams broken. I reported it myself to the dev team. Please also report it threw the report button in the lab (the bubble). The fix will be pushed with the next firmware release.
Best regards
the embodme team - nico"
ok, so basically, what we already had guessed 
whilst its nice they ‘belatedly’ replied to you, they’ve still not mentioned anything on the forum.
what’s with “Please also report it threw the report button in the lab”
are they now juggling 3 support channels - forum, support web form, in app panel?
are they linked? do they supply tracking with any of these?
honestly, this stuff is not ‘hard’, you just need to be a bit professional about it…
a solo developer can pull this off, even as a ‘part time’ project.
oh, well, it is what it is… its how they have always operated.
at least its sounds like we will get an update (in a month or so).
Yeh, It baffles me that a company can be so non communicative and not understand that it can affect their “business”. Of course I understand as a company evolves, they may go through difficult times with workloads and all, but this comes across a little haughty, but I’m sure that is probably not really the case, We can’'t know about the possibly huge number of bug reports they are dealing with on a daily basis, especially with them focused on a new software product,
Wax in contact several times in the past with them for Erae 1 layouts for Plasmonic. Bug it was very erratic, some day very rushing, then silent, then again. Never happened.
Like kinda good will but erratic, from outside