JSI removed the USB 2.0 x 7 hub (cheap USB hub) from my equation and that solved the problem of the disconnects. Seems to be solved 100 percent. Also I increased the LoopMidi value for “Detects feedback from” to 20000 commands per 3 seconds and the Sysex Buffer to 512 KB. I had changed the Xkey Plus settings to Aftertouch Noise Floor = 8 (from 4, now changed back) and Aftertouch Period = 50 ms (now reverted to original 16).
The USB was disconnecting all the time before I switched to my current USB device.
If you are having disconnections it SEEMS likely it is your USB device.
When the Bluetooth firmware is available through the XKey Program? Eager to try it through bluetooth and cut out USB problems altogether. Whats the word on Beta testing of this firmware?
A Driver is still needed, if only for people who wanna make Xkey Plus changes on the fly in the claimed supported Windows platform. I’m surprized you maintain your Bluetooth SIG status allowing the huge Bluetooth brand on the device with the device not operating in Windows: https://www.bluetooth.com/develop-with-bluetooth/marketing-branding/brand-enforcement-program.
Like I said a Really GOOD driver would take the bluetooth signal and run it through a Windows API which could deliver it with its XKEY AIR 37 (or 25) name to ANY AND ALL program which take MIDI. Silently and with no stress for the user. Yamaha’s driver is good at this, with only Rare NAME CHANGES due to some programs like Ableton Live Lite and LMMS M Audio Legacy Keyboard Driver and Oxygen 8 driver (running at the same time on my system, always) are even better, with NO name change EVER.
As Apparently the ONLY person currently existing who has the experience to talk about MIDI driver value in windows I would make a checklist similar to the one at the Bluetooth.com website, but for the driver:
– Take the BLE signal (with all aftertouch at top sensitivity)
– Route it (via Windows Bluetooth API where necessary) to any and all open .exe programs which take MIDI devices