Sujet Commentaires sur la news : Les spécifications du MIDI 2.0 sont à présent publiques

Exploring MIDI 2.0: A Conversation with Microsoft's Pete Brown

00:00 Introduction
00:19 Intro to Pete
02:09 What is MIDI?
07:22 Why do we need MIDI 2.0?
09:18 MIDI MPE
10:26 Bi-directional communication
12:10 MIDI CI
13:33 MIDI CI over 1.0 / CI over 2.0 UMP
14:04 Why is Microsoft implementing MIDI 2.0?
18:23 Network MIDI 2.0
19:20 Is this the end of OEM MIDI drivers?
22:40 App to app MIDI communication
25:32 What do developers need to do?
28:21 Bringing old devices into MIDI 2.0
31:17 MIDI 2.0 tools in Windows
32:05 Live demo of the new MIDI 2.0 tools in Windows 11
42:31 Bluetooth MIDI
43:45 Windows as MIDI router
45:17 Open Source Project
47:19 How will it ship?
50:58 Links for developers
52:02 Pete's Windows Audio workstation guides
53:10 What's your favorite synth?

MIDI2.dev aims to promote the adoption of MIDI 2.0 by providing tools and libraries useful to developers.

Resources include C++ Libraries, USB helpers, testing applications, and more from leading contributors to the MIDI 2.0 specifications. Our repositories are at https://github.com/midi2-dev

Windows MIDI Services Info

Main Links:

Docs: https://aka.ms/midi
Repo: https://aka.ms/midirepo
Discord: https://aka.ms/mididiscord

Windows MIDI Services is a complete rewrite of the MIDI stack in Windows. It has been designed from the ground up to support both MIDI 2.0 and MIDI 1.0. It's open source so anyone can see the code, contribute, etc. but we ingest it into Windows internally to ship in-box later this year.

Selected features folks will probably want to know about

• Everything is multi-client by default, so more than one app can connect to the same device at the same time.
• Full MIDI 1.0 and MIDI 2.0 support
• New USB MIDI Class driver which will run, in the case of MIDI 2.0, as fast as the USB port supports.
• New cross-process data transfer that is much faster than what we had for MIDI 1.0.
• User metadata for endpoints, including name, description, images, and more, available to every application.
• JSON configuration files holding all the metadata can be easily ported/copied to other machines.
• Incoming and outgoing timestamps, and outbound message scheduling.
• New Windows service that handles MIDI 1.0/MIDI 2.0 data format translation, MIDI mapper-type plugins, and more
• Support for existing kernel streaming drivers, but we hope to make them completely or mostly unnecessary going forward.
• Built-in loopback MIDI to enable apps to easily communicate with each other. These can be created through the MIDI Settings app, or in the case of temporary ones, through the API
• Built-in app-to-app MIDI. Similar to loopback, but the endpoints are tied to the lifetime of the application that is offering itself up as a MIDI device.
• MIDI Console tool for power users, developers, and those who want to test and or script things through the command line.
• MIDI Settings app for configuration
• Will be available in-box later this year for Windows 11, and shortly after (depends on servicing intervals) for latest supported Windows 10.

A few other things we're working on related to this:

• Network MIDI 2.0 (this will ship after our initial release)
• BLE MIDI 1.0 reimplementation from scratch, fully open source.
• Plumbing the old WinMM and WinRT MIDI 1.0 APIs through to the new service so existing apps can get some of the benefits, including multi-client.
• Considering implementing RTP MIDI 1.0

This specification will define the mechanisms and the message format for exchanging Universal MIDI Packet messages via a local area network. This enables the transport of MIDI 1.0 Protocol and MIDI 2.0 Protocol. This also defines discovery of available Network MIDI devices and Hosts, and management of Network MIDI Sessions.