windows 10 latency in nanopad2

functionform · Post by **functionform** » Sat Oct 14, 2017 5:21 am

Testing this on two different DAWS, reaper 64 bit, and caustic windows. reaper has asio driver configured and caustic default windows.

I get very annoying latency in either environment with nanopad2 compared to my barebones m-audio keyboard. It almost feels like the nanopad2 is trying to live quantize my pad presses in a poor manner.

Any ideas? Thanks in advance.

voip · Post by **voip** » Sat Oct 14, 2017 8:35 pm

Is the Korg USB MIDI driver installed? If so, has the MIDI in been configured as nanoPAD2 1 PAD?

.

functionform · Post by **functionform** » Tue Oct 17, 2017 3:38 am

Yep. I'm using Asio driver as well. I've even tried configuring Reaper midi config to use high precision timestamp just in case just for this device which seems to improve resolution a little, but still I get dropped notes.

By comparison, I randomly hooked up My DJ Control Compact and tested its cue pads on the same kit and I get no dropped notes.

It's either Korg's midi driver or the machine doesn't output events fast enough.

voip · Post by **voip** » Tue Oct 17, 2017 8:46 pm

It might be worth restoring the factory settings. To do this, disconnect the nanoPAD2 from the USB port, hold down the "Key/Range" "Scale/Tap" and "Scene" buttons whilst connecting the nanoPAD2 back to the USB port with the other hand. Keep holding down the buttons until the scene LEDs start blinking, and wait for the process to finish. It should be complete after a few seconds.

.