| Namespace | Windows.Devices.Midi2.Enumeration |
|---|---|
| Type Name | MidiEndpointTransportSuppliedInfo |
| Type | WinRT Runtime Class |
| IDL | MidiEndpointTransportSuppliedInfo.idl |
| Property | Description |
|---|---|
IsReadOnly |
True if this object should be treated as read-only |
Name |
The endpoint name as provided by the transport |
Description |
The description, if any, as provided by the transport |
SerialNumber |
Any unique serial number (iSerial in USB, for example) from the transport |
VendorId |
If the device is connected to the new UMP USB driver, or we can otherwise obtain it, this is the USB VID idVendor |
ProductId |
If the device is connected to the new UMP USB driver, or we can otherwise obtain it, this is the USB PID idProduct |
ManufacturerName |
If the device is connected to the new UMP USB driver, this is the manufacturer name from the USB headers |
SupportsMultiClient |
True if the endpoint supports multi-client use through Windows MIDI Services |
NativeDataFormat |
The MidiEndpointNativeDataFormat indicating if this device natively uses the MIDI 1.0 byte format, or the UMP format |
TransportId |
GUID identifying the transport in use |
TransportCode |
Short identifier for the transport, such as KS or BLE |
DriverDeviceInterfaceId |
The driver device interface id for this endpoint, if applicable |
TransportId and TransportCode are how you tell what kind of thing an endpoint actually is,
which WinMM never really answered. VendorId and ProductId here come from the transport, and are
not the same as the parent device’s identifiers.
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.
