| Namespace | Windows.Devices.Midi2.Transports.Network |
|---|---|
| Type Name | MidiNetworkHostConnection |
| Type | WinRT Runtime Class |
| IDL | MidiNetworkHostConnection.idl |
Returned inside MidiNetworkConfiguredHost.Connections.
| Property | Description |
|---|---|
UmpEndpointName |
UMP Endpoint Name reported by the remote client |
ProductInstanceId |
Product Instance Id reported by the remote client |
RemoteAddress |
Current remote IP address. For display only; not stable for identity matching |
RemotePort |
Current remote source port. For display only |
IsSessionActive |
True if a transport session is active with this remote client |
IsPendingApproval |
True if the host is waiting for user approval/denial before admitting this client |
EndpointDeviceId |
The endpoint device id created for this connection, when active |
CurrentLatencyTicks |
Current measured latency in QPC ticks |
RetransmitCount |
Count of command packets resent to this client |
RetransmitRequestCount |
Count of retransmit requests received from this client |
TotalCountNetworkPacketsSent |
Total network packets sent to this client |
TotalCountNetworkPacketsReceived |
Total network packets received from this client |
A remote client is identified by UmpEndpointName and ProductInstanceId, not by RemoteAddress and RemotePort, because addresses and ports can change between reconnects.
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.
