I'm also no deep expert, but this is how I understand it: You mentioned class compliance. This means that you don't need extra drivers (plug & play), because your hardware is following a well defined standard interface that the default drivers can use. If you don't need any special features, this is nice because the driver is continuously developed by the OS people and you have a decent base quality.chk071 wrote: ↑Sun Mar 03, 2024 12:18 pmCan you explain to a layman (in layman terms) what that means exactly? I was under the impression that MIDI 2.0 is handled by the respective audio software and hardware. Does the implementation have to do with class compliancy, and plug & play, so you don't need special drivers for your hardware or something?Fannon wrote: ↑Sun Mar 03, 2024 11:30 am I've heard that Windows 11 might get MIDI 2.0 this year. With this they'll completely replace the old MIDI stack and a few of the new improvements will also apply to MIDI 1, like better performance and multi-client streams.
https://devblogs.microsoft.com/windows-music-dev/
For MIDI, the OS Driver I think cares about knowing how to get MIDI over USB and how to make it available again to other software. It could also do routing, monitoring. I think creating virtual MIDI devices is something they now want to ship out of the box.