Microsoft.Windows.Devices.Midi2.Endpoints.Virtual
Fully-featured app-to-app MIDI in a MIDI 2.0 world involves connections to a virtual device which must participate in the full MIDI 2.0 protocol, from discovery through protocol negotiation. To support this scenario, the way app-to-app MIDI works in Windows MIDI Services is for an application to define a device and then using the MidiVirtualDeviceManager, construct that device’s endpoint. Once the device endpoint is opened (like any other connection), Windows MIDI Services will then construct a second application-visible multi-client endpoint which applications will use to talk to the device app.
During that conversation, the service will also handle discovery and protocol negotiation with the virtual device just like it would any physical device.
In addition to the service component, it is implemented in the client API as a type of Client-Side 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 |
| 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.
