Pieter thank you so much for clarifying all this.
We are building a motion midi-contoller with my brother.
Unfortunately BLE does not suit us, because of it’s Windows compatibility issues.
From what I've read, it’s not officially supported in Win10, and even in Win11 it seems to be a hit-or-miss situation.
For now, i will probably use RTP for the prototype, and see how it works out.
RTP is also not ideal for us though, due to it’s reliance on 3rd party software (rtp-midi+bonjour), and mainly due to it’s lack of Linux support.
After your feedback, and further research on the subject, it seems the only solution would be to make a custom Driver/App as you suggested, or a Dongle-based solution instead, ditching Wifi/BT entirely, and using RF modules.
Something like a NRF24L01+ RF Transceiver Module for example.
To give a better picture of what we’re aiming for we compiled this list below:
Essential:
-
Wireless communication
It is a hand-held motion controller, so a cable would defeat the point.
-
Win, Mac and Linux compatibility
-
“It Just Works”
Device “discovery” should be simple and consistent.
Unlike BLE on Windows systems
-
Low Latency
-
If dongle is necessary it should be as small as possible
Ideally as small as those BT mouse dongles.
This may be an issue, since apart from the RF-chip, it will aslo need some sort of processor to convert the incoming data to Class-Compliant Midi.
Unless a custom Driver/App that takes cares of this is used in combination with the dongle, but still I assume there will be some sort of Analaog to Digital Conversion needed which will probably need some sort of processor chip?
Desirable:
1.No necessity for 3rd Party software
2.No need for Dongle
Although it seems the best solution at the moment
3.Hardware Synth compatibility
Dongle would be very useful here
4.Smartphone compatibility
Dongle would not work here, unless the hand-held controller has a an option for “BLE mode”, which will bypass the dongle and transmit BLE (or RTP) instead.