| Namespace | Windows.Devices.Midi2.Transports.Rtp |
|---|---|
| Type Name | MidiRtpSavedClient |
| Type | WinRT Runtime Class |
| IDL | MidiRtpSavedClient.idl |
An RTP-MIDI client saved in the configuration file. The service connects it every time it starts. MidiRtpTransportManager.GetSavedClients returns one of these for each saved client.
| Property | Description |
|---|---|
ClientId |
The GUID that identifies this client. It’s the same as MidiRtpConfiguredClient.ClientId when the client is set up in the service |
Comment |
The Comment saved with the entry, often the device’s name. Empty when none was saved |
Name |
What the remote device shows for this PC. Empty means this PC’s name |
CustomEndpointName |
The name the customer chose for the endpoint. Empty when the endpoint uses the name the remote device sends |
MatchCriteria |
A MidiRtpClientMatchCriteria saying which remote device to connect to |
AutoReconnect |
False when the client connects once, and stays disconnected after the connection ends |
SendRecoveryJournal |
True when the client sends the recovery journal, so the remote device can repair a lost Note Off |
IsEnabled |
False when the service shouldn’t connect the client |
This comes from the configuration file, not from the service. It tells you what the service connects the next time it starts, and it works even when the service isn’t running.
MatchCriteria is a new copy each time you read it, so changing it changes nothing that’s saved.
To forget a saved client, pass a MidiRtpClientDisconnectConfig to MidiServiceTransportPluginConfigManager.SaveUpdate.
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.
