Nanopad Problems

Smileyfrea · Post by **Smileyfrea** » Mon Mar 08, 2010 10:24 pm

Hi

I bought a Nanopad 2 days ago. When I first plugged in the device he installed without errors but because I run Win7 here I checked the website for specific Win7 drivers. I found the 1.12 drivers which I installed together with the Kontrol Editor.
My findings so far is that when I open Reason or Sonar (with sfz drummer as VSTI) I'm not able to get the pads work.

Strange thing is that the X/Y controller does work without tweaking the little thing. Does somebody have an idea what I should do to get the Nanopad work?

Thanks in advance for your help!

Bart

GAPs · Post by **GAPs** » Wed Mar 10, 2010 1:45 am

Wow man, coincidence!

My Korg nanoPAD is also the same problem.
I'm from Brazil, and serached brasilian forum to find the solution for this problem but nobody know what is it...

I tested using with Windows XP (desktop) and Windows 7 but the trigger PADs does not work.
When I bought the nanoPAD it work normally, but now does not work correctly.

PS: My nanoKey and nanoKontrol operate normally on my TRAKTOR.

GAPs · Post by **GAPs** » Fri Mar 19, 2010 3:35 am

up
please help us

LordMusicide · Post by **LordMusicide** » Wed Apr 14, 2010 12:02 pm

exactly the same problem, please help, someone!

plaas · Post by **plaas** » Fri May 07, 2010 6:20 pm

hi! i'm new to this forum and subscribed for searching help to this issue...

i bought the nanoPad and nanoKey because i needed a simple interface for writing some beats without using a mice or trackpad, and when i tested for the first time they just worked perfectly!

now... i changed place, i unmounted my gears for going in the new place (all my gear have the original package, except the Kawai 1980~ synth 100 F

) and when mounted all together again, SURPRISE! it wasn't going correctly anymore! meanwhile i upgraded Ableton Live 6 to Ableton Suite 8, and my MacBook OS to OSX 10.6... i found many people having the issue, and this guy also published a video on Youtube:

http://www.youtube.com/watch?v=qObv9cHVabc

it looks like there's a NOTE ON / NOTE OFF issue, and while a NOTE OFF doesn't occur, it's impossible to trigger again a sample or something else with the pad! (the guy is using the nanoPad for triggering cue points on Traktor, i use it for triggering drum samples in Ableton Live)...
I tried it with DrumRack (Live's integrated drumming instrument) and the midi trigger indicator really remains enlightened when the pad is not working properly... also the X/Y Pad is not working fine anymore...

someone did find a fix for this? Korg is just "saying nothing" about this and about a fix to the problem...

THANK YOU

plaas · Post by **plaas** » Sat May 29, 2010 4:51 pm

solved, the problem was the velocity sensitive circuitry... they told me it's a common problem!

anyway thanks

CS5n531 · Post by **CS5n531** » Fri Jun 11, 2010 3:41 am

My XY pad works fine but none of the velocity pads work. Any reason why? I posted a thread about it, check the only topic I've started.

plaas · Post by **plaas** » Fri Jun 11, 2010 1:03 pm

CS5n531 wrote:My XY pad works fine but none of the velocity pads work. Any reason why? I posted a thread about it, check the only topic I've started.

Hi! my nanoPAD has a circuitry board problem, maybe yours too!

did you install the latest drivers from korg's website?

CS5n531 · Post by **CS5n531** » Sat Jun 12, 2010 7:57 am

plaas wrote:
CS5n531 wrote:My XY pad works fine but none of the velocity pads work. Any reason why? I posted a thread about it, check the only topic I've started.
Hi! my nanoPAD has a circuitry board problem, maybe yours too!

did you install the latest drivers from korg's website?

I did, but I decided that I've read too many negative things for one product. I returned it and spent $10 more dollars on a Akai LPD8, which is honestly great and was so easy to install.

eOdraude · Post by **eOdraude** » Sat Sep 18, 2010 12:43 pm

plaas wrote:solved, the problem was the velocity sensitive circuitry... they told me it's a common problem!

anyway thanks

Hi,
could you explain how to solve this "velocity sensitive circuitry" problem?
I have the same problem with the trigger pads. I've installed all the latest drivers and updates from Korg's website, but nothing have changed.

djraiu · Post by **djraiu** » Tue Dec 28, 2010 1:46 am

Yes please explain this issue. Is it that they need to be exchanged or repaired?

eOdraude · Post by **eOdraude** » Tue Dec 28, 2010 10:15 pm

Hi,
got the solution (at least for me).
I've tried 3 nanoPad.
The first didn't sound, except for the XY pad.
The second one had some trigger pads that sometimes didn't work.
The third one had the same problem, so I opened it and tighten the screws of the inner unit, which are more relevant than the screws of the external unit to the solution of this issue, since allow the single pads to be as closer as possible to their respective circuits.
Now the nanoPad works, but that is certainly not thanks to Korg, which says nothing helpful about this very common issue.
Be careful when opening the external unit, because screws, which are hidden by the six rubber supports, can easily get consumed.
Good Luck!

Yogev · Post by **Yogev** » Fri May 02, 2014 12:47 pm

plaas wrote:solved, the problem was the velocity sensitive circuitry... they told me it's a common problem!

anyway thanks

Can you please explain how you solved this ???

(I have the latest driver - and want to know if there is a simple fix before i start taking it apart ....)

Korg Forums

Nanopad Problems

Nanopad Problems

same problem!