Perfecting Bluetooth MIDI on Windows: A Deep Dive into a New Utility

Bluetooth LE MIDI offers the promise of a clean, cable-free studio setup, but for many Windows users, that promise has often been met with frustration. Despite devices successfully pairing, digital audio workstations (DAWs) and other MIDI applications frequently fail to recognize them, leading to a silent and unproductive experience. This common pain point stems from architectural quirks within Windows' native MIDI handling.

Erwin Mayer, a developer who faced this exact dilemma with his Roland FP-90X piano, embarked on a debugging journey that uncovered a stack of independent bugs. The result is "Perfect Bluetooth MIDI for Windows," a free, open-source utility designed to bridge this critical gap, allowing Bluetooth MIDI keyboards to function as if they were wired devices within any DAW or Web MIDI application.

The Persistent Problem of Bluetooth MIDI on Windows

The core issue lies in how Windows natively exposes Bluetooth LE MIDI. It does so exclusively through the WinRT API, an interface that most traditional DAWs simply do not poll. This means that even when a Bluetooth MIDI device successfully pairs with a Windows 11 PC, applications like Ableton, Pro Tools, FL Studio, Reason, or Reaper remain oblivious to its presence.

As one Hacker News commenter aptly summarized the widespread nature of this problem:

I haven’t used Windows for ages. Does this mean that almost every Windows user with any Bluetooth MIDI keyboard is unable to use it out of the box with their DAW without installing additional third-party software? Does it apply even to latest version of the very widely used DAWs like Ableton, Pro Tools, FL Studio, Reason, and Reaper?

While workarounds like MIDIberry combined with loopMIDI exist, they often prove unreliable or overly complex, failing to provide the seamless, single-app experience users desire.

A Comprehensive Solution: Bridging the Gap

Erwin's utility tackles these challenges head-on by leveraging the new Windows MIDI Services (WMS) stack, which includes a powerful feature called loopback endpoints. These endpoints allow data written to one side to emerge from the other, making them visible as normal MIDI ports to any winmm, WinRT, or WMS application.

Solving Two-Way Communication

The solution addresses two critical directions of MIDI communication:

1. Piano to PC (Input): The application takes WinRT BLE-MIDI input and routes it to WMS loopback output. This allows the DAW to 'see' and receive notes from the Bluetooth keyboard.
2. PC to Piano (Output): This direction presented a more elusive bug. Despite notes being sent and reaching the piano at the GATT layer, the instrument remained silent. After extensive debugging, it was discovered that the Roland FP-90X, while defaulting to transmit on MIDI channel 1, actually receives on channel 4, a setting that cannot be changed on the device itself. Notes sent on channel 1 were silently discarded by the synth engine, offering zero feedback at any layer.

The Clever Channel Detection Feature

To combat the silent channel mismatch, the utility includes an ingenious "Detect" button. This feature plays a series of test notes, ascending through each MIDI channel from 1 to 16. Users simply count the notes they hear, and that number reveals the correct receive channel. This setting is then saved per BLE MAC address, making it a one-time, 75-second setup per piano.

As one commenter noted, "The channel detection approach is clever."

Technical Underpinnings and Community Reception

The utility is built with .NET 10, using Avalonia for its portable UI (though the BLE/MIDI core is Windows-only). It leverages Microsoft.Windows.Devices.Midi2 packages for WMS integration and directly uses Windows.Devices.Midi (WinRT) for BLE, avoiding older drivers. The project is open-source under the MIT license, distributed as a single, self-contained ~21 MB executable with no installer, telemetry, or account requirements.

The project has garnered positive attention, including from Pete on the Microsoft Windows MIDI Services team, who commented positively on its BLE integration. While initially tested with the Roland FP-90X, the generic nature of the BLE side suggests compatibility with other devices like WIDI Master, CME, Yamaha MD-BT01, Korg microKey Air, and ROLI Seaboard. Users are encouraged to report device tests, issues, and submit pull requests.

Latency and Alternatives

One common concern with wireless MIDI, highlighted by users, is latency.

The big question is what does your average latency look like?

While the original post doesn't provide specific latency figures, the goal of a "perfect" solution implies minimizing it. For many, wired connections remain the preferred choice for critical, low-latency performance.

I have multiple pianos, always used cable because I wanted it to work without problems in Linux and Mac. Also I can't stand delays.

Other projects, such as libremidi, were mentioned as potentially polling BLE devices, suggesting alternative approaches or components that could also address parts of this problem space. The utility's PC-end solution also holds promise for those working on projects like a "Linux MIDI gadget" to send signals to a PC over BLE.

Conclusion

"Perfect Bluetooth MIDI for Windows" represents a significant step forward for musicians and producers struggling with wireless MIDI on Windows. By meticulously dissecting and resolving a series of complex, silently failing issues, Erwin Mayer has delivered a robust, open-source tool that transforms the promise of Bluetooth MIDI into a reliable reality. This utility not only solves a frustrating technical problem but also exemplifies the power of community-driven development in addressing niche, yet critical, pain points in the technology landscape.