![]() ![]() I currently use two different computers which run Windows 10, and both of them have the same problem. It worked great back when I had Windows Vista but stopped working when I got a new computer which ran Windows 8 at the time. I've got pretty much the same problem, but with a different keyboard (M-Audio KeyRig 49, which is plug-and-play). Perhaps it has something to do with xHCI handshakes or something. Not sure how long this will actually keep working though. Windows somehow started installing different/new drivers as well. #edit2: I've hooked it to my front USB controller (which is also a USB3.x port) and it suddenly started working. Lastly, I've attempted to apply the Windows registry "hotfix" as described in this Windows 8.1 thread that describes the EXACT same issue as what I've been experiencing under Windows 10, but it didn't help at all. How and why this is happening is still a very vague. There's clearly an issue in Windows that prevents MIDI controllers from sending input to the computer. I've tried different MIDI devices (over USB). I've bought Windows 10 Pro (standalone). I've tried reinstalling windows entirely - multiple times. I've tried different motherboards (switched from an MSI Z97 Gaming 7 to an ASUS z97 DELUXE). Just to answer some troubleshooting that I already did by myself: Just like any other regular keyboard or mouse. I'm not sure what changed in Windows around that time, but from what I've been reading over the internet, a lot more music producers are experiencing their hardware no longer working under Windows 10, while these devices are typically plug-and-play compliant I never had this issue on Windows 8.1 and it only started happening in Windows 10 in since the last 2 weeks ![]() Once I plug the device in and start Addictive Keys for example, the keyboard works for 3 seconds then just stops. ![]() The software that I use with the controller to play my music also has no problem detecting the keyboard. Windows 10 detects the controller perfectly (it shows up under the Sound- and USB-category in device manager). To be clear: The MIDI controller, like many others, is class compliant and doesn't have or require third-party drivers. I've been experiencing the exact same issue with my Alesis Q88 midi keyboard () ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |