| Namespace | Windows.Devices.Midi2.Transports.Network |
|---|---|
| Type Name | MidiNetworkHostConnection |
| Type | WinRT Runtime Class |
| IDL | MidiNetworkHostConnection.idl |
Returned inside MidiNetworkConfiguredHost.Connections.
| Property | Description |
|---|---|
UmpEndpointName |
The UMP Endpoint Name the remote client reported |
ProductInstanceId |
The Product Instance Id the remote client reported |
RemoteAddress |
The remote IP address right now. For display only. It can change, so don’t use it to recognize the client |
RemotePort |
The remote source port right now. For display only |
IsSessionActive |
True if a session with this remote client is running |
IsPendingApproval |
True if the host is waiting for someone to approve or deny this client before letting it in |
EndpointDeviceId |
The endpoint device id created for this connection, when it’s active |
CurrentLatencyTicks |
The latency measured right now, in QPC ticks |
RetransmitCount |
How many command packets have been sent again to this client |
RetransmitRequestCount |
How many requests to send again have come from this client |
TotalCountNetworkPacketsSent |
The total number of network packets sent to this client |
TotalCountNetworkPacketsReceived |
The total number of network packets received from this client |
A remote client is recognized by UmpEndpointName and ProductInstanceId, not by RemoteAddress and RemotePort, because addresses and ports can change between connections.
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.
