Windows.Devices.Midi2.Transports.Virtual
In MIDI 2.0, full app-to-app MIDI means connecting to a virtual device that takes part in the whole MIDI 2.0 protocol, from discovery to protocol negotiation. So in Windows MIDI Services, one app defines a device, and then uses MidiVirtualDeviceManager to create that device’s endpoint. When the app opens the device endpoint, like any other connection, Windows MIDI Services creates a second endpoint. Other apps see that second endpoint, and many of them can use it at once to talk to the device app.
The service also handles discovery and protocol negotiation with the virtual device, just as it would with a physical device.
In the client API, the virtual device is a message processing plugin: MidiVirtualDevice.
Click or tap the type name to view more details.
| Type | Description |
|---|---|
| MidiStreamConfigRequestReceivedEventArgs | Arguments supplied when a client of this endpoint has requested stream configuration |
| MidiVirtualDevice | Represents a virtual device in app-to-app MIDI |
| MidiVirtualDeviceClientEndpointInUseChangedEventArgs | Event args for the MidiVirtualDevice ClientEndpointInUseChanged event |
| MidiVirtualDeviceCreationConfig | Information supplied when creating a new virtual device |
| MidiVirtualDeviceManager | The interface to the service for creating a virtual device |
Windows MIDI Services is an open source project with all source available on GitHub. We have a great community on Discord as well. Between GitHub and Discord, you should find the information you are looking for.
