Korg nanoPad quit working

I have been using a Korg nanoPad for a while now to trigger BFD 2 within Cubase, and it has worked great. However, suddenly it stopped responding. I downloaded the latest driver from Korg (which I don’t think should even be necessary), and it still doesn’t work. I have selected “All MIDI Inputs” on the track channel, the nanoPad doesn’t show up as an option. I have re-booted the computer, and it still doesn’t show up.

Any help is greatly appreciated!! Thank you

I think your nanopad is dead. I had the same thing happen to mine and I scrapped it and picked up an Akai MPD18 in replacement which works great.

Thanks for the reply…it’s still lighting up when plugged in, and it seems to register with Windows (I plugged it into a different USB slot and it did a driver search and load), so it seems to still be working…

Hopefully there’s a solution to your issue. But I’ve given up trying to get the korg nano products to work with cubase. My guess is that it’s a driver issue. But as cool as those little things are I just could never get them to work with my rig in any consistent way.
I’ve not tried for over a year so maybe korg has a solution brewing.
Good luck.


FWIW, my NanoKontrol (version 1) works with my C6.00 on XP SP2. Just another data point for you, hope you get it up and running. Which version of Cubase are you running, and what OS?

Thank you for the replies…I’m running Cubase 6.0.5 on Windows 7 64-bit. I’ve tried it in both versions of Cubase (64 and 32)…it worked fine under the setup until just a few days ago.

I had similar problems with the Nano Kybd
mostly when using Finale but sometimes with C5
I found it had to be plugged in when I booted and even then it sometimes
took a couple of boots to get it going…I finally gave up
and moved to a Nocturn

It’s weird…like I said, it was working fine. Thanks for the replies, gonna try to call Korg and see if they can help.

Fixed!! Very helpful (and free!) customer support from Korg…that kind of services makes me continue to be a customer and go out of my way to do business with the particular company. Turns out, there’s a limit of 10 MIDI devices built into Windows for some reason. In case anyone has the same problem or wants to know, here are the steps he walked me through:

  1. Go Start > Run and type Regedit.
  2. Locate the HKEY_LOCAL_MACHINE key and click on the
  • sign to its left to expand it.
  1. Go down and open the tree as follows: Software >
    Microsoft > Windows NT > Current Version.
  2. Under Current Version, click on the Drivers32 key. A list
    of sub-keys will show up in the right pane (Fig. 1); locate
    the Midi sub-keys (Midi, Midi1, Midi2 . . . Midi9).
  3. At this point, you have two options. Either one involves
    deleting a MIDI sub-key by right-clicking on the key
    name and choosing Delete. One option is to delete each
    Midi sub-key (Midi – Midi9), thereby guaranteeing you’ve
    deleted any duplicates, and re-install any necessary
    device drivers from scratch. The other option is to verify
    which keys are duplicates, and delete the duplicates. If
    you delete a “wrong” driver key, worst case is that you’ll
    need to re-install the driver for that device (if that forces
    you to check the net for the latest drivers, that might
    actually be a good thing!).
  4. In Fig. 1, note how there are two entries for usbkt1x1.dll
    (both are circled in red). To verify that these are dupli-
    cates, type Ctrl+F to call up the Find function, and type
    in (for example) usbkt1x1.dll. Keep hitting F3 to find all
    occurrences of usbkt1x1.dll.
  5. Once you get out of the Drivers32 key, you’ll find individual
    instances where the drivers occur, with information in the
    right pane (Fig. 2). This example shows that Midi6 repre-
    sents the driver for the M-Audio USB Keystation. However,
    it turns out Midi1 also shows an M-Audio USB Keystation
    driver with the same characteristics — clearly a duplicate.
  6. After verifying the duplicate, return to the Drivers32 key
    and delete either one of the duplicate sub-keys. You’ve
    now freed up a MIDI device driver.