This is really interesting. Windows device handling can be tricky sometimes, especially when things work at one layer but fail silently at another. The channel detection approach is clever.
> Windows only natively exposes BLE-MIDI through the WinRT API, which almost no DAW polls.
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?
Surprisingly Windows audio stack is a mess. I have a mini keyboard with Bluetooth and it was an adventure to get it working in Windows. In Linux it was pretty much plug and play.
Low latency audio drviers are also messy in Windows when not using an audio interface with well written ASIO drivers. Pipewire in Linux is much easier to configure. Looks like MacOS also does not have this driver problem.
It is surprising. Because most audio plugins and DAWs support only Windows and MacOS.
For what it is worth, Microsoft is in the process of rolling out Windows Midi Services for Windows 11.
https://microsoft.github.io/MIDI/
A few more years and we might be able to approach Atari ST levels of MIDI performance…
This is really interesting. Windows device handling can be tricky sometimes, especially when things work at one layer but fail silently at another. The channel detection approach is clever.
Wow very cool project! I will test it out later today - i have always been using cabled connection for my midi keyboard
> Windows only natively exposes BLE-MIDI through the WinRT API, which almost no DAW polls.
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?
That wouldn't surprise me.
Surprisingly Windows audio stack is a mess. I have a mini keyboard with Bluetooth and it was an adventure to get it working in Windows. In Linux it was pretty much plug and play.
Low latency audio drviers are also messy in Windows when not using an audio interface with well written ASIO drivers. Pipewire in Linux is much easier to configure. Looks like MacOS also does not have this driver problem.
It is surprising. Because most audio plugins and DAWs support only Windows and MacOS.
If you use a Mac, you'd be amazed at how many things can't be done on Windows without 3rd-party software.
Do you know how to spot a Windows user ? They print-and-scan to merge their PDFs.
Tried with the Yamaha Seqtrak on Windows 10, didn't work.
Thanks! Totally understand – the tool’s core audience is definitely Windows users facing MIDI driver headaches. Appreciate you stopping by though!
Impressive work! Alas I don’t use windows but if I did I would certainly check this out.