Erae II coming soon

I wonder what the release date is? I’m thinking of getting one now that the Loom projects seems failed. Would like to get it on pre-order but they don’t say exactly when that will end.

1 Like

If you scroll up to SteveElbows’ most recent reply, you’ll know as much as the rest of us.

2 Likes

I had also backed the Loom project so having to decide wether to get this. I believe, in the Alex interview at SynthFestUK, he says that the arpeggiator includes the expressive parameters which I assume it’s an MPE arp (of sorts? he’s not very specific about it)? That would be of interest to me. Also curious what the sequencer will be like. And curious what it will mean practically that it is MIDI 2.0. The original was supposed to support 2.0 but I wasn’t clear what that could mean going forward. I’m inclined to pre-order.

2 Likes

yeah, we’ll have to see what the new firmware brings…

I didn’t really find many of the ‘extras’ (sequencer etc) that useful on the mk1.
but I think they are getting a bit of a rework, and I think the display on the mk2 will make things a little more accessible.

for me, main thing with mk2 (except obviously playing surface) will be the looper, I just want to use this for motion recording for eurorack.

but in many ways, thats the strength of the ET (1 & 2) they are so configurable, that we all use in different ways, e.g. I can imagine some use the sequencer, even though it wasn’t for me.

midi 2.0 , yeah, plans were always confused about this.
basically the internal firmware was built around a structure ‘similar’ to midi 2.0 specs, in particular using hi-res midi and (iirc) per note ‘expression’.
SO… the idea is, it would be ‘relatively easy’ to add external midi 2.0 support, but this never materialised.

that said, the FAQ for ET 2 says…

so does sound like this time, they will have the external interface this time around.

(I think mk1, only said it was ‘midi 2.0 compatible’ , or perhaps even more nebulous ‘midi 2.0 ready’ ;))

all that said, Im pretty sure they said mk1 will be getting a firmware (and Erae Lab) update alongside the mk2, which will bring new functionality.
so perhaps the mk1 will get this too, with that new firmware.


in other news… we got an update on KS.
basically they expect to ship at end of November, then it’ll be 2 weeks shipping.
so mid December.
(this is good, as we still have a 6 weeks leeway, to avoid Chinese new year)

so… end of year :slight_smile:

anyway… if you want to know latest… best place it on kickstarter, they are do a reasonable job on the communication front.

3 Likes

Always appreciate your assessments. Most helpful!

1 Like

Regarding MIDI 2.0, I’d split the broader issues up into a few different things:

a) Missing pieces of the picture and potential catch 22 and chicken or egg complications stemming from these. For example Windows support is still in dev and hasnt been released to the general public yet. Other operating systems have support but any limitations to those implementations wont become very obvious until more people actually try to use it. And then we have other major pieces that will only come gradually, including DAWs and various synths. These absences have slowed down the release of MIDI 2.0 functionality in the devices even when the developers of those devices have been otherwise keen to launch.

b) The number of different aspects of MIDI 2.0 that exist. There is the stuff that aids with auto-config and mapping, auto discovery of device capabilities by other devices. There is high resolution stuff. There is stuff that can totally replace MPE and offers a very large number of per-note parameters, but there is also alternative stuff int he spec that is just an expansion of the existing MPE protocol, maintaining its core way of working but adding extra resolution.

Only once we have a few devices with released or publicly available beta firmware that make use of some of those MIDI 2.0 features to actually offer something more for users of expressive controllers and instruments, will I have much to say that is more specific to actual users. So far Korg have dabbled with some of the auto-mapping stuff but not stuff of relevance to this forum. Woodman’s Immaculate Maple Syrup Studio have some MIDI 2.0 stuff in several products that is of some relevance to this forum, but there arent enough 2.0 products from other companies that would allow me to go on about whats available from Woodmans in a more useful, broader context yet. But I am only only synth and one expressive controller away from being able to start going on about that and showing more useful interoperability examples. But even when that happens, it will still mostly be a curiosity for a while, until the scene grows and more parts fall into place. There will be some MIDI 2.0 stuff in the next public beta of Waldorf Quantum/Iridium firmware, but until I know which aspects they have actually implemented, I cannot be too confident about the relevance to this forum. Could be highly relevant, in which case that relevance will also apply if Erae II ends up including those same features, ie they could become a great expressive pairing, or not. Right now, if Erae II came out tomorrow with the right MIDI 2.0 features enabled, and nothing else came out at the same time, the only potential pairing that I know about would be to try using it with a mac running WoodSynth. And right now, if that pairing is successful then it would involve a direct pairing, people would have to keep their non-MIDI 2.0 DAWs out of that equation.

2 Likes

In terms of the MIDI 2.0 DAW situation, the devilish detail regarding the support that a few DAWs have will only become clearer once people have more products to try with them. Some of the info on paper is pretty vague, and much of it only makes reference to higher resolution in a far more limited context of expression, eg higher resolution note velocity (which one Roland product can support).

Here is an example of what was being said about MIDI 2.0 DAW support from a Novermber 2023 article, and I havent actually heard much more about this area at all since then:

MultitrackStudio supports MIDI 2.0 and MIDI 2.0 VCM, MIDI-CI, Property Exchange Program List, MIDI 2.0 VCM with Articulations,

Logic supports MIDI 2.0 CVM and those can be passed to AU plugins,

Steinberg’s Cubase 13 and Nuendo 13 translate some MIDI 2.0 messages into VST3 format and supports high resolution velocity, CC, aftertouch, pitch bend, and poly pressure data. According to the Steinberg website both Nuendo 13 and Cubase 13 are ready for the widespread adoption of MIDI 2.0.

Ivory 3 supports High Resolution Velocity MIDI 2.0 Voice Channel Messages.

So does the Supreme Drums Taiko.

On paper MultitrackStudio seems to have implemented the most, and thats been true for years now, but its a pretty obscure DAW.

Thats from New MIDI 2.0 Products Released-November, 2023 – MIDI.org

2 Likes

sure, midi 2.0 will have ‘oddities of implementation’ , thats been the history of midi.

it’ll all come out in the wash, once we start getting products.
ofc these days, with online updates (firmware/software, resolving this is much easier than it used to be.

overall though, I think one issue is just a lack of demand from musicians. for many, midi 1.0 is ‘good enough’. and the prospect of inevitable compatibility issues is a bit off putting.

its a shame, I really thought they’d use MIDI-CI to show how midi 2.0 can help in real-life situations - as its something, completely missing from 1.0 , rather than just more ‘bits’.

similar the improved clock could be a good push, though, I think many musicians are nervous with clocking… its a pain to get right, so once its working leave it alone :slight_smile:

anyway, it’l come, but for now, I think many devs (like Embodme) are just getting there ducks into a row… Im thinking midi 2.0 will just kind of creep into play, rather than be something we one day say… tada, midi 2.0 is here.

1 Like

I wont attempt to judge demand until far more products are available. Until musicians get to see stuff actually working in a obvious and compelling way, Im not surprised that their reactions arent so positive.

So far I think the negativity and skepticism was increased by the very large amount of time that passed between initial hype and actual products. Some aspects of 2.0 not being available via MIDI DIN caused further negative reactions, most obviously from people who arent positive about USB. That ‘no DIN’ limitation doesnt apply to CI, although of course there will still be an issue in the scenarios where some people are used to using DIN only in 1 direction for some parts of their setup, as opposed to the bi-directionality that is required for CI.

I think CI stuff will be first to get the most attention from mainstream products, demonstrators and users. So I still think it will be used in the way you mention, its just we arent there yet. Its what Korg have done with a handful of their synths and their keystage, but there are other aspects of that keyboard/controller product which arent so compelling. And on some of the supported synths Korg have really half-arsed the number of parameters made available via CI. So I havent pushed hard to use that early Korg ecosystem as a great demo of the full potential of this stuff.

Anyway, Im still not going to make any big claims about the attractiveness of this stuff because of the timescale uncertainties. It will be an easier sell if/when it reaches the same level (or beyond) as Native Instruments NKS stuff, but without the proprietary NI negative baggage (NI squandered a fair amount of goodwill over the years so plenty of people are starting from a negative position when judging their stuff. And from a dev perspective, I dont think its even possible to start adding NKS to a product without first talking directly to NI).

1 Like

By the way, I dont own any Korg hardware that I referred to in this context. I’ve had one experience of seeing CI stuff in action for myself so far - I used WoodTroller on a mac with the demo versions of the Korg soft synths that support CI in standalone mode, running on the same mac. It worked, and it was useful for me to see it working in practice, but inevitably that setup wasnt really adding anything compelling for me.

1 Like

From an expressive controller perspective, Im still skeptical about how much added resolution will wow people. Theres a chance it might in specific contexts, and I wont be surprised if some products go hard on the marketing for that higher resolution, but until I get to play for myself I cannot make any claims. Much the same story as me not being completely sold on the idea that MPE+ makes an incredible difference with the Osmose as opposed to normal MPE. Any differences are somewhat subtle in most contexts, and so users style of play and other factors will influence perceptions.

And the 2.0 area Im least certain about in terms of adoption is when going beyond the 2.0 MPE profile and into the more complex world that departs from MPE completely and unlocks far more dimensions of expression per note / control signals per note. I simply dont know if or when any controller will ever come along that feels the need to add even more dimensions of expression per note. Suspect there will be diminishing returns with such attempts, complexity of learning the instrument and mastering control of it seem likely to be an issue, not to mention actual physics and actually being able to truly separate intent across numerous axis.

1 Like

yeah, still lots of questions … which we just need to wait n’ see, and also let the whole thing ‘settle down on’.

but back to OP (ET midi 2.0)
I can appreciate Embodme’s approach of being (internally) ‘ready’ to implement 2.0, kind of future proofing, but not necessarily be in a hurry to actually release.

from a support (and possibly sales) side, it might be easier / more economic to be a follower rather than leader/pioneer in this area. wait till it settles down till others start promoting it as a feature, so can drive new sales.

so, id not be that surprise if the external midi 2.0 is left as a ‘future feature’ on the mk2, which is ok, I think future-proofing is probably enough for now.

3 Likes

Note that this is without VAT (so for example add 20% in France) and add shipping of course

3 Likes

Yeh, for me, pre-ordering from the US still comes to 830 U.S. dollars.

1 Like

I just pre-ordered so really hoping it’s a safe bet with Embodme after getting burned with the Aodyo Loom!

2 Likes

FWIW, I heard back from Embodme saying that the expected ship date is 4-5 weeks from now and that I should expect mine in early December.

3 Likes

Just in time to unwrap Christmas presents.

You’re more generous than I am.

1 Like

I do not allocate gifts for anyone except myself unless I have excess resources available, which is an extremely rare occurrence.

1 Like

Looks like pre-order time has ended and they’ll be shipping really soon. They are taking regular orders now!

From Embodme on the kickstarter page from 4 days ago:
“We were going to write an update as part of the team is flying next week to China to supervise production. All units will be dispatched in December.”

1 Like