# MIDI 2.0 Device Support

**URL:** <https://forum.juce.com/t/midi-2-0-device-support/58965>\
**Category:** General JUCE discussion\
**Created:** [November 28, 2023, 7:31am UTC](https://forum.juce.com/t/midi-2-0-device-support/58965 "2023-11-28T07:31:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ryanblock](https://avatars.discourse-cdn.com/v4/letter/r/a9a28c/32.png) [@ryanblock](https://forum.juce.com/u/ryanblock)\
**Post date:** [November 28, 2023, 7:31am UTC](https://forum.juce.com/t/midi-2-0-device-support/58965/1 "2023-11-28T07:31:18Z")

</div>

When will I be able to plug-in a [Roland A-88MKII](https://www.roland.com/us/products/a-88mk2/) into a Mac and be able to read 16-bit velocity messages through Juce?

I saw the MIDI-CI support recently landed in JUCE which is great news. When will we be getting full UMP 2.0 message and device support?

[This video](https://www.youtube.com/watch?v=Y8Gng4x_vOY) provides a nice overview of where things stand with MIDI 2.0 as of 11/17/23. To summarize, there are a few 2.0 devices already available on the market and there is OS level support for these 2.0 devices on all OSes except for Windows.

Are you going to wait until Windows support is finished before releasing something? I’m sure it will release eventually but it just keeps on getting delayed and delayed. Isn’t device support on macOS, iOS, Android and Linux enough for now?

---

<div class="post-metadata">

**Author:** ![t0m](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/t0m/32/16413_2.png) [@t0m](https://forum.juce.com/u/t0m)\
**Post date:** [November 28, 2023, 8:54am UTC](https://forum.juce.com/t/midi-2-0-device-support/58965/2 "2023-11-28T08:54:54Z")

</div>

We’re going to wait for Windows before we add device support to JUCE. Delivering something now that we then might have to reconfigure to conform to how things work in Windows would be double the work for the JUCE team, and disruptive to everyone already using the new functionality.

---

<div class="post-metadata">

**Author:** ![ryanblock](https://avatars.discourse-cdn.com/v4/letter/r/a9a28c/32.png) [@ryanblock](https://forum.juce.com/u/ryanblock)\
**Post date:** [December 18, 2023, 12:28pm UTC](https://forum.juce.com/t/midi-2-0-device-support/58965/3 "2023-12-18T12:28:22Z")

</div>

Windows MIDI 2.0 Developer Preview 2 was released today:

> **[Release Developer Preview 2 · microsoft/MIDI](https://github.com/microsoft/MIDI/releases/tag/dev-preview-2)**
>
> We're excited to release the latest snapshot of Windows MIDI Services, including the new Windows Service, the API and projections, the console app, and the USB MIDI 2.0 driver.
> This is a developer ...

Also this was said in the discord before it’s release:

> The core session and endpoint send/receive code has been stable for a bit. The device watcher code for enumeration was recently added, but is functioning well. Areas that are still iterating
> 
> - MIDI CI Profiles and Property Exchange support
> - App-to-App MIDI MIDI CI/UMP Virtual Device
> - Mechanism for getting certain config changes up to the service at runtime (a json parameter) without restarting service
> - Bunch of stuff inside the service itself which do not impact the shape of the client API
> 
> So not necessarily complete, but very close to it. The only reason something else may change is based on testing/feedback from customers or if our next API review insists something has to change. The final API review hasn’t yet happened here, so still an opportunity to make critical surface area changes if, for example, a key feature just doesn’t work properly from a supported language. The USB driver looks like it still needs more work and testing before we share it out, so I’ll create another interim API build for folks here soon and publish the release notes with it.