MMA and AMEI announce MIDI 2.0/Web-MIDI

[Chaser]

MIDI 2.0

[Chaser]

 Web MIDI (MIDI Support in Web Browsers)
           
MIDI hardware support has been available for a long time in most computer/tablet/smart phone platforms but until recently there has been no standard way to use local MIDI devices with a browser or a browser-based Operating System.

The Web Audio Working Group of the W3C designed the Web MIDI API to provide support for MIDI devices as a standard feature in Web browsers and operating systems across multiple hardware platforms. Google has led the way by contributing to the specification and by shipping the first implementation of the Web MIDI API (in Chrome v.43 for Windows, OSX, and Linux), continuing to demonstrate the company's interest in helping musicians interact with music more easily using the Web.

Being able to connect to local MIDI hardware will increase the creation and distribution of music-making applications for PCs, tablets and smart phones. It also means that popular MIDI hardware can be used to control any kind of software in the browser (using physical buttons and knobs instead of on-screen sliders, for example).

For hardware device makers, instrument control panels and editor/librarians which previously needed to be produced in multiple versions can now be implemented once in HTML5, and consumers can run them on any Web device (tablet, computer, or smart phone) and even "live" over the Web.

And since the browser is connected to the Internet, musicians can more easily share data and even connect music devices over a network.

Here's why the Web-MIDI API for Web browsers is the most significant advancement of MIDI since... MIDI itself!

Works on all platforms and devices. Anything with a web browser can run a Web-MIDI app and use local MIDI hardware.
Works with your existing MIDI setup. If your MIDI gear is connected to your computer, tablet or phone (by a cable or even wirelessly) that same connection will connect your MIDI gear to your Web-MIDI enabled browser.
Updates are automatic. No need to install new versions, the latest version is always available at the website URL.
Accessible anywhere. Apps and data in "the Cloud" are available anywhere you have an internet connection.
It's the Internet! Browsers make it easy to connect you and your music to other people via social media and on-line MIDI communities.
Web MIDI

The Web MIDI program is moving along..Web-MIDI support is just beginning and there are a few API's already.

The DM Dock owners may benefit from the Web MIDI program.

Here are a couple Drum Related.. Web-MIDI  API's you may find interesting..

You don't need a midi connection to audition..just hit play and  apply different kits/impulse responses etc to the demo's.
Web Audio Drum Machine 1.0

Complete web site that supports the new Web-MIDI API.
(Currently Google Chrome works and Identifies the Drum modules properly.There is a Web MIDI API extension for Mozilla Firefox , but requires a plugin that Mozilla Firefox will not install.)
In the settings select midi input ..the module..midi FULL has multiple zone support.
You do not have to change the notes in the module.
Highlight the midi note box,enter your own note or strike the trigger/zone and it will midi learn.
Play Drums Online

There is also a Cross Platform DAW from Open Labs
Stagelight
   
Web MIDI API Repository

[Chaser]

I haven't updated this topic in a while as there hasn't been much progress for Drums...until recently.. and it's Great News.
I am a member of the MIDI Association...so I try to be as involved as much as possible so I have access to info as it becomes available.
I was waiting for the 2nd Drum profile to be Adopted/Standardized before posting..however lost patience..

In 2020 MIDI 2.0 was adopted..
Since then there have been 8 MIDI-CI (Compatibility Inquiry-Bi-Directional MIDI) Profiles Adopted/Standardized for Manufacturing/Production .
There are currently 8 MIDI-CI Profiles Adopted/Standardized for Manufacturing/Production.

There are now (2) MIDI-CI Profiles for Drums.

(1) MIDI-CI Default Drum Note Profile (Drum Sounds to Note Numbers)..Drum Machines/Multipads/keyboard etc
This was Voted/Adopted/Standardized in Feb 2025 after NAMM.(Basically the original GM Drum Standard 1983-present we are all accustomed to)

(2) MIDI-CI Drum Performance Profile (Electronic Drum Kits)
This will include positional sensing for drums,cymbals and a robust hihat with pressure sensing.

The MIDI-CI Drum Performance Profile is scheduled to be Voted on/Standardized by Mid 2025..which is anytime now.

The group that worked on the MIDI-CI  Drum profiles...for almost a year...

Steve Fisher- Director  Drums Product Development Medeli

Ben Israel- Research and Content Design Manager -Yamaha

Mike Kent- Chair of MIDI 2.0 WG/MIDI Association Executive Board.Drum Profile  Chair Co Founder Amenote,

Mike Snyder -Innovation Manager, Electronic Instruments at Avedis Zildjian Company

Ikuo Kakehashi- Founder of BAC Audio  a team of master electronic instrument engineers who worked on Zildjian's new  ALCHEM-E series electronic drum kits,

I would presume Medeli..being one of the largest Manufacturers/Private Label/Re-Branding etc in the World..that we may see Drum Modules (or Re-Brands - Alesis etc) with MIDI-CI Drum Performance Profile (Positional Sensing..Bi-Directional MIDI etc) in Production...within a year or 2.

Watch the Video...I am surprised it hasn't made more News in the E-Drum Community....then again there hasn't been much in the way of a Press Release etc.

I will add the link for the MIDI-CI Drum Performance Profile (Electronic Drum Kits) when available

VIDEO
MIDI 2.0 Drum Profiles - The MIDI Association

MIDI-CI Profile Default Drum Note Map

MIDI-CI for USB was donated (Amenote) to Microsoft...there is a pre-release MIDI 2.0 driver available which works well.

Windows MIDI Services
This project is the next-generation MIDI API for Windows, including MIDI 1.0, MIDI CI, and MIDI 2.0.
It includes enhancements, a new USB class driver, new transports, and a suite of essential tools.
The project adds many enhancements and bug fixes to our MIDI 1.0 support, and importantly adds support for the latest revisions to MIDI CI and MIDI 2.0 as approved by The MIDI Association.

There is a MIDI 2.0 Developer Collaboration
MIDI 2.0 Workbench and requirements/support for LINUX Machines.
MIDI 2.0 support was added in Linux kernel 6.5. and for MIDI 2.0 to work you need alsa-lib version 1.2.10 or higher.



EDIT:
Added Links

[Chaser]

One of the most significant developments for MIDI 2.0 at the 2026 NAMM show was that announcement by Microsoft that the new Windows MIDI Services (a new MIDI API, Service, Tools, and SDK) is rolling out to retail Microsoft Windows throughout the month of February, 2026.

At January NAMM 2026, Pete Brown and Gary Daniels from Microsoft showed off Windows MIDI Services top features for musicians and developers, and explained some of what is going on under the hood.

Windows MIDI Services is a modern, rebuilt system for handling Musical Instrument Digital Interface (MIDI) on Windows, offering full support for both legacy MIDI 1.0 and the new MIDI 2.0 standard with Universal MIDI Packets (UMP), enabling faster, more reliable communication, simultaneous multi-client access to devices, automatic translation between versions, and new tools like the MIDI Services Console for management and diagnostics, all built on an open-source foundation for future expansion.

About Windows MIDI Services
Windows MIDI Services is the new MIDI API, Service, and SDK in Microsoft Windows. It's delivered in two parts:
In-box MIDI Service and plugins, the new MIDI 2.0 kernel driver, plus backwards-compatibility support for WinMM and WinRT MIDI 1.0 APIs.

You get this when you install Windows.

An out-of-band shipped SDK Runtime and Tools package.
You need to download and install this yourself.
We ship the runtime and tools out-of-band to enable us to move quickly and continue providing new features and capabilities for customers and apps.

Benefits for everyone

No need for third-party USB drivers in most cases.
Most USB MIDI 1.0 devices are class-compliant and will work without third-party drivers. This means no wrestling with their position in the registry, or worrying about compatibility. Don't install third-party drivers unless absolutely necessary, and you'll have a better MIDI experience on Windows.

Supports your Existing Apps.
The existing WinMM and WinRT MIDI 1.0 APIs have been repointed to the new Windows Service. This provides a subset of the new features, including multi-client so your apps will continue to work as today, but will be even better.

Multi-client by default.
Any endpoint (including MIDI 1.0 devices) can be used by multiple applications at the same time. That means you can use a librarian or controller app at the same time your DAW has a connection open.

Supports your Existing Devices.
Windows MIDI Services supports the MIDI 1.0 devices you own today, including those with vendor-supplied kernel streaming drivers, as well as class-compliant MIDI 1.0 and MIDI 2.0 devices. The experience will be better/faster if they use the new class driver, but we recognize that is not always possible or desirable with some existing devices.

Faster.
In our testing, we've found that the new infrastructure is much faster at sending and receiving messages compared to the older API, even with plugins configured in the service. There are no built-in speed caps or throttling in Windows MIDI Services, even for older USB MIDI 1.0 devices. The new MIDI 2.0 driver is not limited USB full-speed, and supports USB 3.x speeds.

Lower Jitter.
Along with higher speed comes lower jitter. This will vary by transport type (USB vs Network vs Virtual), and the device Windows is talking to, but the jitter is in the low microsecond range even without any compensation.

More Deterministic.
Speaking of latency compensation, the new API enables timestamp-based message scheduling for outbound messages for any apps using the new API. In addition, incoming messages are tagged with a timestamp when received by the service.

App-to-App and Virtual Device MIDI.
Windows MIDI Services includes built-in virtual / app-to-app MIDI 2.0 to enable lightning fast communication between apps on the PC.

Better tools.
We supply the midi.exe Windows MIDI Services Console for developers and power users, or anyone comfortable with the command line. You can use it to monitor endpoints, send and receive messages, send/capture SysEx data and much more. We also include the MIDI Settings GUI app for renaming devices, configuring your MIDI setup, testing, and more.

Built-in Scripting Built-in support for scripting MIDI using PowerShell.
Want to automate synchronization between mixers? Want to set up a script to initialize all your devices for a show? All this can be done via the PowerShell Cmdlets.

Developer Benefits

UMP-Centric.
The new SDK fully embraces MIDI 2.0 and the Universal MIDI Packet format and handles all required translation in the service and driver. This makes the app model simple while ensuring all your existing devices continue to work. Messages to and from any endpoint, whether it is MIDI 1.0 or MIDI 2.0 data format, are transparently translated in the service, and presented as UMP through the SDK.

Extensive Endpoint Metadata
We've built upon Windows.Devices.Enumeration with our own MIDI-specific device class, which provides much more information about a device. Not only do we have user-provided metadata (name, description, images, settings), but also more device-provided information. This is also where you have access to MIDI 2.0 device features like Function Blocks, Group Terminal Blocks, Device Identity, and much more. See MidiEndpointDeviceInformation for details.

Device Connect/Disconnect Notification
No restarting your apps to detect the presence of a new device. Whenever an endpoint is created, updated, or removed, the app receives an event with all the required details. Additionally, apps can opt-in to automatic reconnect to any device they are communicating with, should it become disconnected during a session. See MidiEndpointDeviceWatcher for details.

Extensible.
The service has been designed to be extensible by Microsoft and third-parties. New types of transports can be added at any time, including during prototyping of a new transport specification. (We're working on Network MIDI 2.0, Bluetooth MIDI 1.0 and considering RTP, all using this model.) No kernel driver experience required in most cases.

Open Source.
The source code is open and available to everyone under a permissive license. Not sure how something works? Want to create a transport but aren't sure how we did it? Want to investigate a bug or contribute a feature? The code is there for you to explore.

MIDI 2.0 (and enhanced MIDI 1.0!) comes to Windows 11

The MIDI Association has worked on two Drum Profiles in 2025.

The Default Drum Note Map Profile specifies 62 Drum/Percussion Sounds mapped to Specified Note Numbers.
This is the common mapping in many Drum Machines and Synthesizers since the 1980s.

This Profile was adopted in the fall of 2025.

The Drum Performance Profile is focused on the more advanced features available in electronic drums kits which have positional sensing for cymbals and drums and complex hihat configurations.

The Drum Performance Profile design is complete and it should be approved in Q1 of 2026.