The virtual device can still be seen in the Device Manager, but it stopped functioning (maybe due to another major Windows 10 update to Ver. Unfortunately most major MIDI Apps do not (yet) support the new UWP API and therefore they cannot "see" the nanoKey device.In the past, the Korg BLE driver was bridge between the new UWP API and the old MME API (by providing the virtual "Korg BLE MIDI Device"). nanoKEY) can be seen in any App that supports the new Windows UWP MIDI API (e.g. I found that everything is working ok but the Korg BLE driver.The pairing works fine. I've done all the suggested actions with no success. How can I investigate ? Could you please give me some diagnostic steps and support ? How can I force the use of Korg drivers ? Maybe the installation fails because Windows drivers are preferred to the Korg ones, and that microsoft drivers do not manage MIDI. When I look in the configuration pannel, a new PC appears with the name "microKEY2-37 Air" only using microsoft driver files. When I try to launch programs in C:\Program Files (x86)\KORG\KORG BLE-MIDI Driver like EzSetup.exe, the message "ERROR : No device is plugged in." When I switch the keyboard off, it still appears as "connected" When I start my music software, midi ports are not detected. with not action, the light led restarts blinking I appears in connected devices as "microKEY2-37 Air and connected" the light led remains blue and stops blinking I search, find, and add it using windows bluetooth manager the light led becomes blue and blinking
I switch the blueetooth on the microkey2-37 air keyboard just installed Korg BLE driver for windows version 1.12.02.01
Intel® Dual Band Wireless-AC 8265 driver version 20.10.0.5, Bluetooth version 4.2 (up to date)
0 kommentar(er)
