| Namespace | Windows.Devices.Midi2.Enumeration |
|---|---|
| Type Name | MidiParentDeviceInformation |
| Type | WinRT Runtime Class |
| Implements | IStringable |
| IDL | MidiParentDeviceInformation.idl |
Details about the parent device of a MIDI endpoint, such as a USB device. MidiEndpointDeviceInformation.GetParentDeviceInformation() returns one.
| Property | Description |
|---|---|
Id |
The device instance id of the parent device |
Name |
The friendly name of the parent device |
ContainerId |
The container GUID for this device |
ParentDeviceInstanceId |
The device instance id of this device’s own parent |
RelatedParentMediaDriverDeviceInstanceId |
The device instance id of the related parent media driver device, if there is one |
DriverInfPath |
The path to the driver’s INF file |
DriverKey |
The driver’s registry key |
DriverProvider |
The name of the company that provided the driver |
ServiceName |
The name of the driver service for this device |
DriverVersion |
The driver’s version |
EnumeratorName |
The name of the device enumerator, such as “USB” |
UsbVendorId |
The USB vendor id (VID), for a USB device |
UsbProductId |
The USB product id (PID), for a USB device |
UsbSerialNumber |
The USB serial number, for a USB device that has one |
ReportedDeviceIdsHash |
A hash of the device ids the device reported, for quick comparisons |
These show where to find the USB vendor and product ids, and how this type is different from the ids the transport reports. With WinMM, you would have used DRV_QUERYDEVICEINTERFACE and read the ids out of the interface string yourself.
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.
