novation launchkey 49 keyboard controller driver

Naturally, the troubleshooters cannot identify the problem (most have nothing to do with hardware and devices other than keyboards, mice, and wireless things anyways), and the 'Add a device' option seems only to work with wireless devices, Instead, they use generic, Microsoft-provided midi ones. Here, Alesis claims that the V series controllers they make (including the V61) are However, since Windows does not recognize it as a MIDI device, it cannot be used for MIDI applications (an easy one to test is at ). I know the keyboard still can communicate, as I used an Alesis program to test it. In the device manager, it is listed under 'Sound, Video, and game controllers.' When I plugged it in via USB, it told me that it was 'Setting up the device,' but it ended up classifying it as a 'Generic USB Audio Device' which is It worked last summer, around July, but I've updated Windows since then. Specifically, I'm using an Alesis V61 MIDI Controller: Alesis V61 the result is that I cannot use the device as a MIDI controller, which is, well, pointless. TL DR: can I force Windows to use a MIDI driver when it mis-recognizes a device?īasically, Windows will see the device, think it is a Generic USB Audio device instead of a MIDI controller, and installs the wrong drivers (without errors). Windows 10 not recognizing class-compliant MIDI Keyboard Controller

Novation launchkey 49 keyboard controller driver