Microsoft has significantly upgraded music production capabilities in Windows 11 by integrating support for both MIDI 1.0 and MIDI 2.0 through Windows MIDI Services. This update involves a complete rewrite of the existing MIDI 1.0 code, creating a combined stack that enhances performance and adds infrastructure for MIDI 2.0.
Key Features and Improvements
The new Windows MIDI Services introduces several key features. Multi-client support allows multiple applications to use each MIDI 1.0 port and MIDI 2.0 endpoint simultaneously, eliminating the need for custom vendor drivers. Users can customize endpoint names and metadata, with options for classic API names, new-style names, or fully custom names, along with images and descriptions via the MIDI Settings app.
Additionally, the update includes built-in loopback and app-to-app MIDI capabilities. Native loopback endpoints work across APIs, including WebMIDI, on x64 and Arm64 architectures. Applications can present themselves as full MIDI 2.0 devices and are translated to MIDI 1.0 for compatibility with legacy apps.
Advanced Translation and Timing
Windows MIDI Services automatically translates and scales MIDI 2.0 messages, allowing high-resolution devices to be used by any application. MIDI 1.0 apps receive downscaled values, while MIDI 2.0-aware apps benefit from full resolution. The service also supports timestamps and scheduled messages, ensuring precise timing with accuracy under a microsecond.
A new USB MIDI 2.0 class driver, usbmidi2.sys, has been introduced, offering improved power management and faster communication with the MIDI service. The older usbaudio.sys remains for compatibility, but devices can be assigned to the new driver for enhanced performance.
Development and Community Involvement
Windows MIDI Services was developed openly on GitHub with contributions from the community and partners such as AMEI/AmeNote, Yamaha, Roland, and others. Developers can access preview tools on GitHub and via WinGet, and are encouraged to contribute and participate in discussions on Discord.
Future plans include an in-box low-latency USB audio driver with ASIO support, additional transports like BLE MIDI 1.0/2.0 and Network MIDI 2.0, and a virtual patch bay for enhanced routing. These features are being tracked on GitHub and Discord.
