| Namespace | Windows.Devices.Midi2.Transports.Rtp |
|---|---|
| Type Name | MidiRtpHostCreationErrorCode |
| Type | WinRT Enumeration (a 32-bit unsigned or signed integer) |
| IDL | MidiRtpHostCreationErrorCodeEnum.idl |
Returned in MidiRtpHostCreationResponse.ErrorCode.
| Value | Numeric Value | Description |
|---|---|---|
NoErrorInformationAvailable |
0 |
No more information is available |
InvalidJson |
1 |
The service couldn’t read the configuration it was sent |
MalformedEntryIdentifier |
4 |
HostId isn’t a valid GUID |
InvalidEntry |
6 |
The service couldn’t read the host entry |
NameTooLong |
9 |
Name or ServiceInstanceName is longer than 63 bytes in UTF-8 |
InvalidPort |
10 |
ManuallyAssignedPort isn’t between 1024 and 65534 |
InvalidName |
12 |
A name couldn’t be used. A name that’s advertised can’t have a period in it |
ServiceUnavailable |
1000 |
The request never reached the transport, because the MIDI service isn’t running, or the RTP-MIDI transport isn’t installed |
TimedOutWaitingForHostToStart |
1001 |
The service accepted the host, but the host didn’t start in time |
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. CreateRtpHostAsync waits for the host to start, and reports TimedOutWaitingForHostToStart if it doesn’t, instead of reporting success that isn’t true yet.
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.
