First Impressions - Erae II

[thetechnobear]

from kickstarter update…

Unfortunately, there has been a slight delay with our assembly manufacturer, Picca, due to a hold-up in receiving one key component: the vibrators for the metronome feature.

This was initially intended to be a surprise, but given your eagerness to receive your units (which we truly appreciate), we prioritize transparency over keeping it under wraps.

I missed this entirely

ok, so I did notice a metronome setting, but I assumed what this would do was put an audio signal out on one of the CV jacks, to use with headphones.
why? because something else I have/had did this - Squarp Pyramid?

but I was wrong, there is indeed a pizzo which vibrates the unit. feels like its located in the top left (?!)

as you’d expect, it vibrates on beat and bar (differently), its pretty good in terms of feel.

for my taste/setup, I think its too powerful.not only does it vibrate the unit, but also on my wooden desk resonates it too. so its kind of an annoying (to me!) sound.

that said…

• I can imagine if you were in a noisy environment, it actually could work really well - where feeling would be better than hearing a click.
• given supply issue, I wonder if it was a late addition, so perhaps we’ll get an option in firmware to reduce intensity a bit.

overall…
It’s a nice surprise that definitely is useful, just for me it’s a bit too intense.
I hope they allow us to reduce this in future firmware.

---

notes:

a) if you use the mount (e.g. live performance), then Im sure it will be much better.
b) you can ‘insulate’ the Erae from your desk with a rubber mat, or even a bit of the packaging it comes with.
c) I’ve sent some feedback to Embodme to see if its possible to allow firmware to change intensity.

[thetechnobear]

@keymanpal

Thanks Mark for all insights and impressions, what about a side by side with ERAE TOUCH 1?

Wild idea they could even compliment each other? ET1 more “controller” duties and ET2 playing…

yeah, I do want to give this a go…
however, Im having a bit of an issue with desk space
(the ETs are pretty big, so two take up a lot of space)

really, I just need to re-organise things a bit, and it should be fine.

actually, I need to get some longer cables, to give me some flexibility in placement - something Ive been saying for about 2 years!
perhaps I’ll order these in the new year

[gwpt]

Hi @thetechnobear,
I am eagerly awaiting my Erae 2 and was curious about it with eurorack Eagan Matrix module vs the continuumini (which I also own). Have you used the mini?

If so, would the Erae + matrix module been a good replacement for the mini? I.e, do you think Id miss anything on the mini if I sold it to buy an Eagan Matrix module instead?

TBH honest I’ve always been a little disappointed with the mini. The Y axis is so hard to control that I find it difficult to use, and tend to just use X and Z.

Cheers, and thanks for all the info

[thetechnobear]

sorry, I’ve don’t really have much experience with the mini.

I guess, the main thing you’d miss, with E2 + EMM is it’s less ‘portable’.
there is something nice about having an instrument that is ‘standalone’.

the EMM main advantages over mini are audio in, and cv in.
(bare in mind - the cv in, controls only one voice)

probably what Id do, is keep the mini until you get the E2, and see how you feel it plays together, as likely you’d drive the EMM or mini via E2 → midi,
so its going to be similar experience, then you can device if the eurorack vs standalone tradeoff is what you want.

also Haken have released (?) the EaganMatrix Micro so that might be another option?
(afaik, the Micro is basically a mini without the surface)

[gwpt]

That is a good idea, ill try that.
I had not heard of the micro ill check it out. Thx!

[greaterthanzero]

I need to look into calibration and/or repair options for my Continuumini

I think I’d rather have a micro (or two), but can’t ethically offer this in trade without first making it behave properly.

[NothanUmber]

Also got my Erae II yesterday. Playing with it for some time now, so here some (first) impressions:

• I like the new default smooth playing surface better than the hard one on the Erae I.
• Minimal touch sensitivity feels better than on the Erae I (likely also because of the smoother playing surface which makes it more forgiving to have to press a little harder). No comparison to the Morph though. I’d say you have to hit the surface a little harder than a weighted piano, otherwise there will be no sound. And the required touch pressure is MUCH more predictable than with Erae I now. And the better haptic feedback of the new surface also helps. So I think one can get used to this.
• The minimal concurrently detectable distance between two fingers is definitely better than Erae I, playing with a grid layout with 2x2 dots per key (= somewhere between 1-2 cm^2) is now possible.
• The software has still the same restrictions that I already wasn’t happy about in Erae I (and some new bugs):
  • When having several MPE keygroups in the same layout one can set the number of voices per keygroup - but apparently not the starting channel. So when I e.g. have 3 keygroups with 4 voices each they still randomly block each others channels, so no note appears when another one is already played on another keygroup that coincidentally blocks this channel. (Optimally one could set the number of MPE voices per layout instead of keygrid. Then all elements would share the same “voice pool” and one could play with up to 14 fingers on the entire layout, no matter which keygrid an individual finger lands on)
  • There is no control over pitch rounding for the keygrid. With the hardcoded setting there will always be audible discrete steps when gliding from one cell to an adjacent one (more distinct than with e.g. the Seaboard)
  • It is not possible to individually set the color of arbitrary semitones (This could probably be solved by adding a chromatic scale to the list of scales. Currently I have to switch to off-key mode, then at least chromatic pitches are possible. Still only one color for all off-key fields possible)
  • I didn’t get the the non-MPE modes to send any MIDI (tested with Surge XT and Pianoteq on Win11). Only Keygrid in MPE mode works for me. Tried all channels individually (including 1 and 16 but also e.g. channel 2 which should even work with Surge MPE mode active). (There are three midi devices visible. “Erae II”, “MIDIIN (Erae 2)” and “MIDIIN (Erae 3)”. Only the MIDIIN ones can be selected though, Erae II is greyed out. Could it be that this one would be where the non-MPE elements would send their MIDI events?
  • When having four keygrids in the layout one always gets the message “only four keygroups are allowed” which one has to click away for virtually any click. (Four keygroups actually work ok, the trigger for the warning dialog is just accidentally set to >=4 instead of > 4)
  • There is an option to map absolute x and y to CCs (which would be a workaround for some of the current restrictions, e.g. doing the pitch rounding on the synth side). Currently this is limited to low precision 127 value (7-bit) single CCs though, which leads to audible steps when mapping that CC over the full surface width or height to e.g. pitchbend of the synth. Here it would be good to support “high res CCs” (essentially sending coarse and fine information on different CCs, a way that is supported by many synths). Having the option to map absolute x or y to pitch bend would also be good, so it doesn’t have to be remapped.

So the hardware looks really promising. My initial impression of the software is that it still needs more work to be able to better use the Erae as an actual instrument instead of just as a MIDI controller. But will continue playing with it, perhaps there are some ways around the limitations that I haven’t found yet.

[greaterthanzero]

@NothanUmber

It is not possible to individually set the color of arbitrary semitones (This could probably be solved by adding a chromatic scale to the list of scales. Currently I have to switch to off-key mode, then at least chromatic pitches are possible. Still only one color for all off-key fields possible)

In an ideal world, I’d love a chromatic keygrid with 128 colors.

“One color for all off-key fields” is indeed an ugly limitation, but I’m sort of at “could we stop assuming an octave has 12 notes?”

There’s a lot of very opinionated assumptions in play here. They’re sensible assumptions for the average musician, but I’ve always found that early adopters of advanced technologies are anything but average. Best to provide an “advanced mode”, or at least an API.

Anyway, my planned workaround is “off-key mode, one color for all fields”.

(That one color will be a gradient)

@NothanUmber

When having several MPE keygroups in the same layout one can set the number of voices per keygroup - but apparently not the starting channel. So when I e.g. have 3 keygroups with 4 voices each they still randomly block each others channels, so no note appears when another one is already played on another keygroup that coincidentally blocks this channel. (Optimally one could set the number of MPE voices per layout instead of keygrid. Then all elements would share the same “voice pool” and one could play with up to 14 fingers on the entire layout, no matter which keygrid an individual finger lands on)

That one affects way more users, so I’m more confident that they’re going to fix it.

I think I remember there effectively being two zones in the editor, though. You’d set the first to global channel 1, and the second to global channel 16. Your starting channels are then 2 and 15, converging inwards towards the limit you placed on each group.

It’s been a while since I messed with the editor, though. And of course, I’ve no way to confirm my interpretations.

@NothanUmber

There is an option to map absolute x and y to CCs (which would be a workaround for some of the current restrictions, e.g. doing the pitch rounding on the synth side). Currently this is limited to low precision 127 value (7-bit) single CCs though, which leads to audible steps when mapping that CC over the full surface width or height to e.g. pitchbend of the synth. Here it would be good to support “high res CCs” (essentially sending coarse and fine information on different CCs, a way that is supported by many synths). Having the option to map absolute x or y to pitch bend would also be good, so it doesn’t have to be remapped.

API mode will solve a lot of problems, once unlocked.

[thetechnobear]

yeah, the software is pretty much the same as for Erae mk1 - there aren’t any additions.
The main missing bit, is the api zone. ( and ableton thing?)

Some of the limitations above are same in mk1?
I’d hope/assume first task is feature/functional parity ?!

I’ve been told they are working on an update, which sounds like they are addressing some bugs and things that have been raised.
Though it sounded more on the firmware side (!but that could be , because that’s where most of
my comments lay)

Def good time to send feedback to them.

[greaterthanzero]

Accessories!

The drum stand mounting plate is fantastic, if you have an appropriate stand lying around, or live near a thrift store.

You’re looking for something with a clamp at the top, like this:

pictured above, the Roland Handsonic HPD-10. that’s not the Embodme mount at all.

(the mount is “male”, let’s say. so it won’t just replace a tom or a cymbal in your drum kit, but it might replace the hardware that connects your tom or cymbal to the rest of your hardware)

Anyway, it holds your controller taut, so there’s no threat of it falling off at steep angles (be it leaning towards or away from an audience).

My stand does tend to wobble if I extend it to full height. It’s rock solid at a sitting position, though. And of course, a better stand will be better – the mounting plate can’t be blamed for that.

---

Mixed feelings about the hard cover.

It’s very casual to add and remove, while Erae 2 sits flat on your desk.

The fit is a bit loose, though. So, if you’re using this for protection in transit, you’re going to want to wrap everything (controller and cover) in a towel or something.

I figured it was probably designed to fit snugly on the mounting plate, which would be great if you have to leave your gear unattended after sound check, let’s say. But that use case is more or less blocked. It’s basically incompatible with the mounting plate

---

I think that’s all of them.

(We’re there more accessories? I only bought those two.)

---

EDITED TO ADD

This is the hard case trying to sit atop the drum mount. I can get up to three corners covered.

I’m thinking if I glue a towel across that top section (where the buttons are), it can hang down the back and gravity should hold everything more or less in place.

Conversely, though…

The “Resgods” tray from IKEA sits freakishly well atop this laptop / projector stand while folded closed, and is also as wide as this mixer stand can facilitate. (I think. Mine is the previous model, so I’m not 100% certain that’s still the case)

It’s a bit large for the pair of Launchpad X that I typically like to keep on there, but that extra space is perfect for the Erae hard cover, leaving room on the side for… Livid’s “minim”? I don’t know. It’s not a lot of space.

Leaning towards the audience, this one lip might need to be sanded down for cable management:

Still. That isn’t bad.

[greaterthanzero]

@NothanUmber

I didn’t get the the non-MPE modes to send any MIDI (tested with Surge XT and Pianoteq on Win11). Only Keygrid in MPE mode works for me. Tried all channels individually (including 1 and 16 but also e.g. channel 2 which should even work with Surge MPE mode active). (There are three midi devices visible. “Erae II”, “MIDIIN (Erae 2)” and “MIDIIN (Erae 3)”. Only the MIDIIN ones can be selected though, Erae II is greyed out. Could it be that this one would be where the non-MPE elements would send their MIDI events?

Okay, interesting.

I’m seeing the non-MPE elements coming from “Erae 2”, and the MPE keygrids on “MIDIIN3 (Erae 2)”.

That’s testing with Geert Bevin’s excellent “showmidi”, in standalone mode.

Releases · gbevin/ShowMIDI

(In max/msp, I was only seeing the “Erae 2” port.)

Anyway…

@greaterthanzero

I think I remember there effectively being two zones in the editor, though. You’d set the first to global channel 1, and the second to global channel 16. Your starting channels are then 2 and 15, converging inwards towards the limit you placed on each group.

This is confirmed.

It won’t help with your third or fourth keygrid objects, mind you. But “two halves” is sorted.

I don’t think we’re yet able to detect layout changes externally, though. So, contextually applying those two keygrids to different instruments may yet be a challenge.

@greaterthanzero

Anyway, my planned workaround is “off-key mode, one color for all fields”.

(That one color will be a gradient)

Hated the linear and round gradients. Rectangular at default settings is just marking the corners for some reason, and I like that a lot.

Here’s what that looks like in the editor. This is obviously a glitch, and I’ll be sad when they fix it.

EDIT:
No, wait. scratch that. those dots actually are centered. my frame of reference is just messed up.

---

EDITED TO ADD:

I don’t think Live 12 supports MPE zones.

No idea how to make it treat one block of channels differently than another, save for splitting them externally and sending the processed signals in over virtual midi cables.

So, that’s fun.

[greaterthanzero]

Dragging too far too the left off an MPE keygrid, pitch bend stops at the left-hand edge. You can still move up and down rows, but not stepwise in X.

That’s not ideal, but it is reasonable.

(ideal would be “your touch gesture continues as though the space beneath it was still the same continuous keygrid surface, until you lift that finger”)

Dragging too far to the right is a different story. That jumps to your maximum bend value. Or rather, four octaves above your starting pitch.

That’s neither ideal nor reasonable.

[greaterthanzero]

going way back over here…

@NothanUmber

When having several MPE keygroups in the same layout one can set the number of voices per keygroup - but apparently not the starting channel. So when I e.g. have 3 keygroups with 4 voices each they still randomly block each others channels, so no note appears when another one is already played on another keygroup that coincidentally blocks this channel. (Optimally one could set the number of MPE voices per layout instead of keygrid. Then all elements would share the same “voice pool” and one could play with up to 14 fingers on the entire layout, no matter which keygrid an individual finger lands on)

and…

@greaterthanzero

I think I remember there effectively being two zones in the editor, though. You’d set the first to global channel 1, and the second to global channel 16. Your starting channels are then 2 and 15, converging inwards towards the limit you placed on each group.

…

This is confirmed.

It won’t help with your third or fourth keygrid objects, mind you. But “two halves” is sorted.

If you’re able to use those, I have the other two now.

Uncheck “USB device”, send keygrid #3 out of MIDI OUT A, and keygrid #4 out of MIDI OUT B.

Then, run your TRS MIDI outputs into something like the now defunct “Tapco Link MIDI 4x4” or Blokas’ “MIDI Hub”, to bring those back to the computer on separate USB endpoints.

(It’s important to remind ourselves sometimes that we’re very clever and have boundless resources)

[Prehm]

Honestly, I think they should open source the erae lab software and put it on GitHub.
I‘d bet there are some crafty programmers in the community that would help with fixing bugs and implementing some of the more specific features.

[greaterthanzero]

@NothanUmber

It is not possible to individually set the color of arbitrary semitones (This could probably be solved by adding a chromatic scale to the list of scales. Currently I have to switch to off-key mode, then at least chromatic pitches are possible. Still only one color for all off-key fields possible)

Solved this one, though it’s a bit of a clunky workaround.

• delete your keygrid and replace it with a drumpad

• mark the “MPE” checkbox

• confirm the semitone line offset

• switch over to the “style” tab

• note that all 12 degrees are unlocked, and there isn’t an “off key” line (because your only scale is chromatic). set your colors accordingly.

• you’re going to want to change the “finger animation” options to match what they were in your keygrid element.

[SteveElbows]

@greaterthanzero

I don’t think Live 12 supports MPE zones.

No idea how to make it treat one block of channels differently than another, save for splitting them externally and sending the processed signals in over virtual midi cables.

So, that’s fun.

Yeah, as far as I know all the MPE Zone support that currently exists in Ableton is focussed on the output/instruments/internal routing ‘to’ rather than ‘from’ side of things, not the input side of things. So you can narrow the channel range thats sent to particular hardware synths, plugins and tracks, but theres nothing there for splitting different zones that you may have coming in from controllers on a single MIDI input. And internally, within tracks and recorded clips themselves, Ableton does dynamic channel allocation for the MPE data, rather than honouring the channels your controller originally used - they probably do this in order to support MIDI overdub recording on MPE tracks, and because channel ranges can be redefined when sending the MIDI to plugins, other tracks and external hardware.

For completeness I’ll post a link to their MPE Zone documentation anyway, even though it doesnt seem to cover the scenario you have. https://help.ableton.com/hc/en-us/articles/4409113250322-MPE-Zone-Configuration

[FranklyFlawless]

@Prehm

Honestly, I think they should open source the erae lab software and put it on GitHub.

Feature Requests

[Prehm]

I created a community discord server. Feel free to hop on

Tritt dem Erae Touch 2 Discord Server-Discord-Server bei!

[FranklyFlawless]

I cannot participate due to my strict security practices.

[BetweenTheEars]

Hello,

Has anyone managed to successfully clock the looper on their Erae 2 via the TRS MIDI-In port?

I installed the new 1.0.3 (Jan 16th) firmware and the MIDI in does not appear to accept a MIDI clock from my Pam’s Pro Workout (using its PPEX-1 TRS MIDI-out port) via the MIDI In port. “MIDI” is selected as the clock source in the settings menu, but whenever I hit the ‘play’ button on the Erae, it pulses red/orange and the looper does not activate. FWIW, I was also unable to get a MIDI TRS clock working with the 1.0.2 firmware the unit arrived with, either.

I have a feeling its probably me and not the ERAE, but hoping someone in the community here might be able to help this n00b out

Tangentally, it also seems odd that I can still change the ‘BPM’ setting on the looper, even with an external MIDI clock selected.

Could it be a TRS MIDI A/B issue? I was unable to find any info in the manual whether these are Type A or B, or if the input accepts either A or B.