| Namespace | Windows.Devices.Midi2.Transports.Rtp |
|---|---|
| Type Name | MidiRtpRemoteClientForgetErrorCode |
| Type | WinRT Enumeration (a 32-bit unsigned or signed integer) |
| IDL | MidiRtpRemoteClientForgetErrorCodeEnum.idl |
Returned in MidiRtpRemoteClientForgetResponse.ErrorCode.
| Value | Numeric Value | Description |
|---|---|---|
NoErrorInformationAvailable |
0 |
No more information is available |
UnrecognizedCommand |
2 |
The RTP-MIDI transport in the service doesn’t know this command, usually because it’s older than this API |
InvalidOrMissingEntryIdentifier |
3 |
The request didn’t say which host |
MalformedEntryIdentifier |
4 |
HostId isn’t a valid GUID |
HostNotFound |
5 |
The running service has no host with this id |
TransportNotReady |
7 |
The transport hasn’t finished starting. Try again in a moment |
RemoteClientNameTooLong |
9 |
RemoteClientName is longer than 255 characters |
InvalidOrMissingRemoteClientName |
13 |
RemoteClientName is empty |
ServiceUnavailable |
1000 |
The request never reached the transport, because the MIDI service isn’t running, or the RTP-MIDI transport isn’t installed |
InvalidArgument |
1002 |
Your code passed a null configuration |
ClientApiException |
1003 |
Something went wrong in the client API |
The values from 1000 up come from the client API, not the service.
There’s no error for a remote device the host has no decision for. Forgetting it succeeds, because what you asked for is already true.
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.
