| Namespace | Windows.Devices.Midi2.Transports.Rtp |
|---|---|
| Type Name | MidiRtpRemoteClientSettings |
| Type | WinRT Runtime Class |
| IDL | MidiRtpRemoteClientSettings.idl |
Held in MidiRtpHostRemoteClientSettingsConfig.RemoteClientSettings. Reported by MidiRtpConfiguredHost.RemoteClientSettings and MidiRtpSavedHost.RemoteClientSettings.
| Constructor | Description |
|---|---|
MidiRtpRemoteClientSettings() |
Creates an empty entry with no limit |
MidiRtpRemoteClientSettings(remoteClientName) |
Creates an entry for this remote device with no limit |
| Property | Description |
|---|---|
RemoteClientName |
The name the remote device sends |
SendSpeedLimit |
How fast the host sends to this remote device. Unlimited by default. See MidiRtpSendSpeedLimit |
SkipInBetweenValuesToCatchUp |
True to skip some in-between steps of long control change, pressure and pitch bend moves when messages pile up behind SendSpeedLimit, so this device catches up. True by default. Set it to false for a device that needs every message, however late. Added in version 2 of MidiTransportsRtpApiContract |
Use this when one device connected to a host needs a different speed from the others. A hardware synth that loses data during a long SysEx dump can get MIDI 1.0 wire speed, while a computer connected to the same host gets no limit. For this device, SendSpeedLimit and SkipInBetweenValuesToCatchUp are used instead of the host’s.
A remote device is known by the name it sends, ignoring uppercase and lowercase differences, the same way the host’s remembered decisions know it. RTP-MIDI carries nothing else that stays the same from one connection to the next. An entry with no name is left out when the configuration is sent or saved.
The host uses this speed from the moment the device connects. A device that’s already connected changes speed right away, without being disconnected.
RTP-MIDI can’t tell this PC when a device misses data, so unlike Network MIDI 2.0 there’s no choice to slow down by itself.
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.
