| Namespace | Windows.Devices.Midi2.Transports.Network |
|---|---|
| Type Name | MidiNetworkClientEntryState |
| Type | WinRT Enumeration (a 32-bit unsigned or signed integer) |
| IDL | MidiNetworkClientEntryStateEnum.idl |
Reported by MidiNetworkConfiguredClient.EntryState.
| Value | Numeric Value | Description |
|---|---|---|
Pending |
0 |
Set up, and waiting for the service to connect it |
Active |
1 |
The service has created the client. Use IsSessionActive to see whether MIDI is flowing |
Failed |
2 |
The configuration entry itself was rejected, so trying again can’t help |
Unavailable |
3 |
A direct connection that stopped answering. The service won’t try it again on its own |
Unavailable only applies to direct address connections. Nothing announces that a fixed address is back, so the service stops sending it invitations, instead of sending network traffic forever. Call ConnectNetworkClientAsync again with the same ClientId to retry.
A discovered (mDNS) client never becomes Unavailable. It goes back to Pending, and it’s picked up again whenever the host advertises.
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.
