Generally I like this little unit a lot, when it works...
Often I'll plug it in a just get nothing from it; I can reboot, restart apps etc etc and it looks like it's recognised (Reaper, S1 v2, Reaktor) but no midi received from it (no midi activity at all). Other times I'll just plug it in and it's fine. Had to reinstall the drivers once as nothing else worked.
Any ideas? It happened again last night, wasted twenty minutes messing with it so unplugged it and plugged my Steinber cmc-pd. Worked first time...
Cheers.
Korg Nanokey2 driver issues?
-
- KVRAF
- 8150 posts since 13 Jan, 2003 from Darkest Kent, UK
-
- KVRist
- 53 posts since 23 Nov, 2022
Shoot, found this today with the exact same issue. I guess Korg didn't make any progress in recent 9 years 
It looks like it registers but it depends on existing devices whether also out and in. I need to dig deeper. Win 11 btw if someone has any ideas
It looks like it registers but it depends on existing devices whether also out and in. I need to dig deeper. Win 11 btw if someone has any ideas-
- KVRist
- 53 posts since 23 Nov, 2022
It turns out it's actually a Windows limitation. The hardcoded limit from old ages says there should be no more thant 10 midi devices. So those looking for a fix - use Korg uninstaller to remove midi devices (there's a tick box to remove also non-Korg ones) and make sure they won't appear again - by unplugging the device. Then plug Korg Nanokeys2 and it should work just fine with midi number less than 10.
-
AdvancedFollower AdvancedFollower https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=418780
- KVRian
- 1345 posts since 8 May, 2018 from Sweden
I'm not sure it's a Windows limitation. All other USB MIDI devices work just fine with ID's above 10. It's only Korg devices that don't work properly.h0g0f0g0 wrote: Fri Mar 24, 2023 1:39 pm It turns out it's actually a Windows limitation. The hardcoded limit from old ages says there should be no more thant 10 midi devices. So those looking for a fix - use Korg uninstaller to remove midi devices (there's a tick box to remove also non-Korg ones) and make sure they won't appear again - by unplugging the device. Then plug Korg Nanokeys2 and it should work just fine with midi number less than 10.
Take a single oscillator, producing a drone. Send it to the wave shaper, altering the tone.
This can be a triangle, Sawtooth or a square. Modulate the pulse width, nobody will care
This can be a triangle, Sawtooth or a square. Modulate the pulse width, nobody will care
-
- KVRist
- 53 posts since 23 Nov, 2022
Well it's a WIn spec. However if korg device registers with default win driver it will work with midi id higher than 10. So it's a limitation in Korg driver, but the driver follows the definition set by Microsoft. It's strange.
Anyway, it will work even with Korg driver installed if id is below 10. Otherwise remove Korg driver and it will work with any id
Anyway, it will work even with Korg driver installed if id is below 10. Otherwise remove Korg driver and it will work with any id
-
- KVRAF
- Topic Starter
- 8150 posts since 13 Jan, 2003 from Darkest Kent, UK
ha, my old thread...
I hadn't used the nanokey for a while, got a small arturia microlab instead which generally works fine. I do find Reaper sometimes doesn't see devices unless you do a 'reset all midi devices' so I have a shortcut to that action on my toolbar.
But; out of curiosity I dug my nanokey out and plugged it in, first time on this new-ish Win11 laptop without installing any korg drivers and it just worked, playing notes in Reaper fine without even doing the midi reset thing.
So, guess my original post is now null and void.
I hadn't used the nanokey for a while, got a small arturia microlab instead which generally works fine. I do find Reaper sometimes doesn't see devices unless you do a 'reset all midi devices' so I have a shortcut to that action on my toolbar.
But; out of curiosity I dug my nanokey out and plugged it in, first time on this new-ish Win11 laptop without installing any korg drivers and it just worked, playing notes in Reaper fine without even doing the midi reset thing.
So, guess my original post is now null and void.