A
ASTsinger
Hello!
I have been working on this ALL NIGHT! I finally found to look under device manager where Windows says Casio USB Midi is working properly yet it does not show as an input device in either Audacity or Darkwave Studio.
In device manager, under the EVENTS tab it has a device not migrated note. After plugging in this CASIO LK-165, then trying an Oxygen 49 midi keyboard (not mine) which also has this migration note and also does NOT show as an input device in either program, making sure the USB port works (one of the 3 I have has the same issue of not being migrated--SIGH), not finding a fix through Casio, I am finding this is a Windows Issue.
After turning them off, unplugging, plugging, back on, all in correct sequence, I now get a Kernel PnP message from Windows about this. There are a few "FIXES" out there but I do not download stuff from unknown sources.
Here's the notice (event 442 if that's relevant):
I even used the online help option in this event notice and found 0 answers on almost every post like this.
Is there not a fix in 2020? I see alot of issues from 2015 but why is this still an issue? I updated the driver, disabled/enabled it, Windows is up to date. What?????
Need some help here Windows!
Continue reading...
I have been working on this ALL NIGHT! I finally found to look under device manager where Windows says Casio USB Midi is working properly yet it does not show as an input device in either Audacity or Darkwave Studio.
In device manager, under the EVENTS tab it has a device not migrated note. After plugging in this CASIO LK-165, then trying an Oxygen 49 midi keyboard (not mine) which also has this migration note and also does NOT show as an input device in either program, making sure the USB port works (one of the 3 I have has the same issue of not being migrated--SIGH), not finding a fix through Casio, I am finding this is a Windows Issue.
After turning them off, unplugging, plugging, back on, all in correct sequence, I now get a Kernel PnP message from Windows about this. There are a few "FIXES" out there but I do not download stuff from unknown sources.
Here's the notice (event 442 if that's relevant):
| + | System |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| - | EventData |
| DeviceInstanceId | USB\VID_07CF&PID_6803&MI_00\6&7488438&0&0000 |
| LastDeviceInstanceId | HDAUDIO\FUNC_01&VEN_10EC&DEV_0236&SUBSYS_103C84B2&REV_1000\4&1034be17&0&0001 |
| ClassGuid | {4d36e96c-e325-11ce-bfc1-08002be10318} |
| LocationPath |
| MigrationRank | 0xf000fffffffff122 |
| Present | false |
| Status | 0xc0000719 |
I even used the online help option in this event notice and found 0 answers on almost every post like this.
Is there not a fix in 2020? I see alot of issues from 2015 but why is this still an issue? I updated the driver, disabled/enabled it, Windows is up to date. What?????
Need some help here Windows!
Continue reading...