Windows.Devices.Midi2.Transports.Loopback
Types for creating loopback endpoint pairs. A loopback pair is two MIDI 2.0 endpoints, A and B, connected to each other. Whatever is sent to A comes in on B, and whatever is sent to B comes in on A.
These samples create a pair of MIDI 2.0 endpoints connected to each other, while your app runs. Endpoints made this way are temporary. They last only while the service is running, and aren’t saved in the configuration. Remember to remove the ones you create.
Click or tap the type name to view more details.
| Type | Description |
|---|---|
| MidiLoopbackCreationConfig | Config sent to the service to create a loopback endpoint pair |
| MidiLoopbackCreationResponse | Response from the attempt to create a loopback endpoint pair |
| MidiLoopbackEndpointDefinition | The information supplied when creating a loopback endpoint pair |
| MidiLoopbackEndpointEntry | Information about one side of an active loopback endpoint pair |
| MidiLoopbackEntry | Represents an active loopback endpoint pair instance |
| MidiLoopbackErrorCode | Error codes returned by Loopback transport operations |
| MidiLoopbackFeedbackProtection | What a MIDI 2.0 loopback does when MIDI keeps coming back into it |
| MidiLoopbackManager | The primary class used to create or remove loopback endpoints |
| MidiLoopbackRemovalConfig | Config sent to the service to remove a loopback endpoint pair |
| MidiLoopbackRemovalResponse | Response from the attempt to remove a loopback endpoint pair |
| MidiLoopbackSavedEntry | A loopback pair saved in the configuration file |
| MidiLoopbackUpdateConfig | Changes a loopback pair that already exists |
| MidiLoopbackUpdateResponse | Response from a mute or unmute operation on a loopback endpoint pair |
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.
