# Midi 2.0

**URL:** <https://forum.electra.one/t/midi-2-0/63>\
**Category:** Ideas / Feature requests\
**Created:** [January 25, 2020, 12:32pm UTC](https://forum.electra.one/t/midi-2-0/63 "2020-01-25T12:32:21Z")\
**Posts on this page:** 19\
**Page:** 1

<div class="post-metadata">

**Author:** ![buyallthecontrollers](https://avatars.discourse-cdn.com/v4/letter/b/d07c76/32.png) [@buyallthecontrollers](https://forum.electra.one/u/buyallthecontrollers)\
**Post date:** [January 25, 2020, 12:32pm UTC](https://forum.electra.one/t/midi-2-0/63/1 "2020-01-25T12:32:21Z")

</div>

It’s still early days for MIDI 2.0, but will it be technically possible to update the firmware of the Electra One to support some (all) of the new features of MIDI 2.0?

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/martin/32/145_2.png) [@martin](https://forum.electra.one/u/martin)\
**Post date:** [January 25, 2020, 9:19pm UTC](https://forum.electra.one/t/midi-2-0/63/2 "2020-01-25T21:19:32Z")

</div>

MIDI 2.0 is on our long term plan. The idea of MIDI CI is so close to what we are doing that we would like to have Electra capable of bridging some gaps of MIDI 1.0 for older instruments and provide MIDI 2.0 interface for them.

---

<div class="post-metadata">

**Author:** ![buyallthecontrollers](https://avatars.discourse-cdn.com/v4/letter/b/d07c76/32.png) [@buyallthecontrollers](https://forum.electra.one/u/buyallthecontrollers)\
**Post date:** [January 26, 2020, 1:37pm UTC](https://forum.electra.one/t/midi-2-0/63/3 "2020-01-26T13:37:10Z")

</div>

Sounds great! 🙂 Thank you.

---

<div class="post-metadata">

**Author:** ![icaria36](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/icaria36/32/2749_2.png) [@icaria36](https://forum.electra.one/u/icaria36)\
**Post date:** [February 1, 2024, 10:30am UTC](https://forum.electra.one/t/midi-2-0/63/4 "2024-02-01T10:30:23Z")

</div>

> [@buyallthecontrollers](#):
>
> It’s still early days for MIDI 2.0

And four years later it’s still is! 😉 But the amount and intensity of bells about it keeps growing slowly and steadily, we start seeing hardware supporting it, and I was wondering whether there are any updates about the long term plan mentioned by @martin above.

---

<div class="post-metadata">

**Author:** ![NewIgnis](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/newignis/32/767_2.png) [@NewIgnis](https://forum.electra.one/u/NewIgnis)\
**Post date:** [February 1, 2024, 11:32am UTC](https://forum.electra.one/t/midi-2-0/63/5 "2024-02-01T11:32:56Z")

</div>

check out Sonic States interview with Microsoft on MIDI 2.0 on NAMM this year. They made some pretty interesting comment on how MIDI (even the 1.0) will change in the near future

---

<div class="post-metadata">

**Author:** ![icaria36](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/icaria36/32/2749_2.png) [@icaria36](https://forum.electra.one/u/icaria36)\
**Post date:** [February 1, 2024, 12:02pm UTC](https://forum.electra.one/t/midi-2-0/63/6 "2024-02-01T12:02:25Z")

</div>

Yes, I’m following [Midi 2.0 - General Discussion - Elektronauts](https://www.elektronauts.com/t/midi-2-0/74153) where this interview was mentioned. However, unless Microsoft has acquired Electra One, that interview doesn’t answer my question. 🙂

---

<div class="post-metadata">

**Author:** ![icaria36](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/icaria36/32/2749_2.png) [@icaria36](https://forum.electra.one/u/icaria36)\
**Post date:** [February 20, 2024, 3:17pm UTC](https://forum.electra.one/t/midi-2-0/63/7 "2024-02-20T15:17:51Z")

</div>

From anther thread. Copied here for future readers.

> [@Next Electra OS](https://forum.electra.one/t/next-electra-os/2704/2):
>
> I want to be very careful here as circumstances in my private life still greatly affect any time sensitive planning. The features on the top of the list are:
> 
> 1. Add support for MIDI 2.0 so that Electra One can act as a proxy, translating (current, eg sysex) parameters to MIDI 2.0 properties.

---

<div class="post-metadata">

**Author:** ![Flyweight](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/flyweight/32/342_2.png) [@Flyweight](https://forum.electra.one/u/Flyweight)\
**Post date:** [February 22, 2024, 10:22am UTC](https://forum.electra.one/t/midi-2-0/63/8 "2024-02-22T10:22:16Z")

</div>

Change how exactly?  
Microsoft just sucks with their shitty midi driver.  
So are we finally getting multiclient support?

---

<div class="post-metadata">

**Author:** ![NewIgnis](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/newignis/32/767_2.png) [@NewIgnis](https://forum.electra.one/u/NewIgnis)\
**Post date:** [February 22, 2024, 5:06pm UTC](https://forum.electra.one/t/midi-2-0/63/9 "2024-02-22T17:06:17Z")

</div>

yes, at least according to themselves

---

<div class="post-metadata">

**Author:** ![markus.schloesser](https://avatars.discourse-cdn.com/v4/letter/m/8e7dd6/32.png) [@markus.schloesser](https://forum.electra.one/u/markus.schloesser)\
**Post date:** [February 23, 2024, 2:30am UTC](https://forum.electra.one/t/midi-2-0/63/10 "2024-02-23T02:30:41Z")

</div>

And showing it live on video 😊

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/martin/32/145_2.png) [@martin](https://forum.electra.one/u/martin)\
**Post date:** [March 7, 2024, 12:10pm UTC](https://forum.electra.one/t/midi-2-0/63/11 "2024-03-07T12:10:09Z")

</div>

a question. I made changes (early dev version) so that E1 supports most of MIDI 2.0 CI profile/property exchange. When I use MIDI 2.0 debug tools (MIDI Workbench and BOME CI tools), I can see that the communication and property exchange goes just fine. One of the use cases is that E1 exposes the preset controls as properties. I guess you get the idea, that would allow us to easily record automation of any preset parameter in the DAW.

But now I am wondering, is any of the existing DAWs capable of reading that info (parameters, technically speaking the CMList data)? If so, any clues on how to do that? I messed around with the Logic Pro and Ableton but I am kind of clueless…

EDIT: I have korg keystage hooked up to my E1 too. That does not seem to initiate the CI discovery/exchange either…

---

<div class="post-metadata">

**Author:** ![markus.schloesser](https://avatars.discourse-cdn.com/v4/letter/m/8e7dd6/32.png) [@markus.schloesser](https://forum.electra.one/u/markus.schloesser)\
**Post date:** [March 7, 2024, 12:17pm UTC](https://forum.electra.one/t/midi-2-0/63/12 "2024-03-07T12:17:15Z")

</div>

Windows currently does not have midi 2 capability, but Pete from MS (psychlist1972) is actively maintaining and working on that on github and released dev 5 preview today.

OS: Osx, ios and Android are supposed to support all midi 2 capabilities.

Wrt DAW: Logic and one other support it, while Pete was showing a dev version of Cubase that supports midi 2 at namm on YouTube.

AFAIK there’s currently no support for ableton (but might be internal only)

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/martin/32/145_2.png) [@martin](https://forum.electra.one/u/martin)\
**Post date:** [March 7, 2024, 12:20pm UTC](https://forum.electra.one/t/midi-2-0/63/13 "2024-03-07T12:20:05Z")

</div>

> [@markus.schloesser](#):
>
> Wrt DAW: Logic

The only thing I can see in Logic so far is the MIDI 2.0 checkbox. Not really sure what it does 😉

---

<div class="post-metadata">

**Author:** ![markus.schloesser](https://avatars.discourse-cdn.com/v4/letter/m/8e7dd6/32.png) [@markus.schloesser](https://forum.electra.one/u/markus.schloesser)\
**Post date:** [March 7, 2024, 12:30pm UTC](https://forum.electra.one/t/midi-2-0/63/14 "2024-03-07T12:30:26Z")

</div>

Is there documentation about this?  
Might be about UMP only.

> **[Release Developer Preview 5 · microsoft/MIDI](https://github.com/microsoft/MIDI/releases/tag/dev-preview-5)**
>
> Hi Everyone. We're continuing our march to production with Developer Preview 5!
> In preparation for our next API review and for moving into production, we've looked at every aspect of the API and ev...

Also the midi 2 gearspace thread has some devices listed that support CI

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/martin/32/145_2.png) [@martin](https://forum.electra.one/u/martin)\
**Post date:** [March 7, 2024, 2:02pm UTC](https://forum.electra.one/t/midi-2-0/63/15 "2024-03-07T14:02:50Z")

</div>

just to clarify my question 🙂 I am quite sure the dev version E1 does support MIDI 2.0 CI. When I use, say Bome-CI software, I can see everything being picked up and negotiated just fine:

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/electraone/original/2X/6/6904e79343b8ba0a12ccac37cdb3c9f5a4130e93.jpeg)

and the preset controls retrieved:

 ![image](https://europe1.discourse-cdn.com/flex017/uploads/electraone/original/2X/3/3267d6dacb2fa7ef64dce031aa5dd6aea30c633f.jpeg)

I was just wondering if / how I could use / retrieve this info in any DAW. eg. displaying on-screen knobs or recording automation of those properties.

---

<div class="post-metadata">

**Author:** ![markus.schloesser](https://avatars.discourse-cdn.com/v4/letter/m/8e7dd6/32.png) [@markus.schloesser](https://forum.electra.one/u/markus.schloesser)\
**Post date:** [March 7, 2024, 3:40pm UTC](https://forum.electra.one/t/midi-2-0/63/16 "2024-03-07T15:40:19Z")

</div>

Are you a member of the midi organization? They will probably have way more info.

Wrt logic: what I wrote earlier, might be that their “midi 2” switch only means ump but not CI

About other daws: I’m only really familiar with Live and there it would be a remote script, but haven’t seen anything wrt CI yet.  
I’d contact apple about logic and steinberg

Edit: I see you already posted your questions on gs! 😊 👍

---

<div class="post-metadata">

**Author:** ![moss](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/moss/32/1528_2.png) [@moss](https://forum.electra.one/u/moss)\
**Post date:** [March 7, 2024, 9:42pm UTC](https://forum.electra.one/t/midi-2-0/63/17 "2024-03-07T21:42:07Z")

</div>

The Korg modwave plugin claims to support MIDI-CI if run standalone.

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/martin/32/145_2.png) [@martin](https://forum.electra.one/u/martin)\
**Post date:** [March 7, 2024, 9:49pm UTC](https://forum.electra.one/t/midi-2-0/63/18 "2024-03-07T21:49:11Z")

</div>

yup, Korg software/hardware is doing well. I can read Wavestate Native parameters just fine. The KeyStage reads all parameters of E1 preset - it just does not show them on OLEDs 🙂

---

<div class="post-metadata">

**Author:** ![martin](https://dub1.discourse-cdn.com/flex017/user_avatar/forum.electra.one/martin/32/145_2.png) [@martin](https://forum.electra.one/u/martin)\
**Post date:** [March 14, 2024, 8:36am UTC](https://forum.electra.one/t/midi-2-0/63/19 "2024-03-14T08:36:25Z")

</div>

Recognized as MIDI 2.0 device with UMP support:

 ![midi-2.0](https://europe1.discourse-cdn.com/flex017/uploads/electraone/original/2X/7/7fada84adb41f0f77491a327b63dc6758844c520.png)

Works on MacOS and Linux (kernel 6.5+). CI Parameter exchange tested in both directions. Electra can read parameters of connected devices as well as it can provide information about the preset controls as CI properties.

There is still a lot do do: creating a preset out of received parameters, allowing translation of MIDI 2.0 parameters to MIDI 1,0 (eg, mapping MKS-50 sysex messages to properties so that DAW can pick them up and automate). The hardest low level part is done though…
