Email safabulatdev@icloud.com — a real person reads it.
Windows does not accept Bluetooth MIDI into an application directly; it needs a bridge. Any Bluetooth-MIDI bridge utility paired with a virtual MIDI port will do:
If the PC pairs but nothing arrives, the bridge is nearly always the missing step: pairing in Windows settings makes the device known, not audible.
No bridge needed. Audio MIDI Setup → Window → Show MIDI Studio → Bluetooth, find the name and press Connect. It then behaves like any other MIDI source.
Midiboard can offer an RTP-MIDI session on your network rather than a Bluetooth link. Nothing is paired: the phone offers the session and the computer joins it, so the connection is always made from the computer's end. Turn it on in Midiboard under Settings → Connection → Over Wi-Fi.
⚠️ Wi-Fi and Bluetooth cannot both be live. A network session needs a CoreMIDI client, and holding one is what stops a computer completing a Bluetooth pairing — so turning Wi-Fi on stops advertising, and turning it off gives the radio back.
If the Windows directory stays empty, the answer is almost always Bonjour. rtpMIDI discovers devices through Apple's Bonjour service and reports nothing at all when it is missing — no error, no warning, just an empty list. Make sure the Bonjour service is installed and running, and give both rtpMIDI and Bonjour their own exceptions in Windows Firewall. One exception is not enough.
The phone appears under the device's own name (iOS Settings → General → About → Name), not under the Bluetooth name you set in Midiboard. And once you are on Wi-Fi, the port your software plays through is the session's — a Mac that has ever paired keeps an old Midiboard Bluetooth entry in the list, and picking that one gives silence with no explanation.
Most iPad music apps have a Bluetooth MIDI panel of their own; open it and connect. Apps that use Apple's standard sheet will list Midiboard by name.
That message means the app is still holding a connection that has stopped accepting anything — usually a laptop that went to sleep, or a walk out of range. Midiboard drops it and starts advertising again by itself; Retry forces that immediately. If the other machine had gone to sleep, wake it and re-connect from its side.
Panic in the control strip. It clears the app's own note state first and then tells the receiver to silence everything — in that order, because doing it the other way round lets a monophonic widget helpfully retrigger the note underneath as you lift your finger.
Use the Learn buttons in the widget inspector rather than moving the control by hand. A learn sends that one control on its own and mutes everything else the app would send for the duration, so the receiving end has nothing else to latch onto. An XY pad gets a button per axis, which is the case that most needs it — both axes move the instant you touch the pad.
Nothing playable sits in the home-indicator strip, so an accidental brush at the bottom no longer reveals it. iOS will not let any app disable the swipe-up gesture outright, though. For a performance where nothing may go wrong, use Settings → Accessibility → Guided Access; it is the only true lock the system offers.
Write to safabulatdev@icloud.com. What helps most: your iOS version, what the other end of the chain is, and what you were doing when it happened — "it did it while I was transposing with a pad held" is worth more than a screenshot.