| Namespace | Windows.Devices.Midi2.Transports.BasicLoopback |
|---|---|
| Type Name | MidiBasicLoopbackFeedbackProtection |
| Type | WinRT Enumeration (a 32-bit unsigned or signed integer) |
| IDL | MidiBasicLoopbackFeedbackProtectionEnum.idl |
A feedback loop happens when MIDI that comes out of a loopback finds its way back into the same loopback, so the same messages go around and around as fast as the PC can move them. A basic loopback’s output feeds its own input, so one app that passes MIDI through while listening to and sending to the same basic loopback is enough to make one. This setting decides what the loopback does about it.
| Value | Numeric Value | Description |
|---|---|---|
Mute |
0 |
Watch for feedback, and mute the loopback when a loop is found, just as if it had been muted by hand. This is the default |
Off |
1 |
Don’t watch for feedback at all |
Muting is the right answer almost every time. A feedback loop can make stuck notes, freeze a DAW and keep the PC busy until someone notices.
Off is there for the rare app that answers every message it receives by sending another one back, as fast as it can. That really is a loop, just a deliberate one, and it can’t be told apart from an accident.
Check MidiBasicLoopbackManager.IsFeedbackProtectionAvailable before using this. When it’s false, the basic loopback transport on this PC can’t watch for feedback, and entries report Off.
Set it for a new loopback with MidiBasicLoopbackCreationConfig.FeedbackProtection, change it with MidiBasicLoopbackManager.SetFeedbackProtection, and read it from MidiBasicLoopbackEntry.FeedbackProtection. See Why a loopback mutes itself for how the loop is found.
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.
