NanoKontrol - Windows 7 FIXED! WORKING! 64bit WINDOWS 7~

[fennucci]

I had originally used Windows 7 64bit I think home edition, I recently upgraded to ultimate 64bit. I reinstalled reason, etc.. I plugged in my nano thinking it would just work by default after windows installed its drivers, and nothing, I downloaded the drivers from korg, and nothing, its in my device manager, it all appears right. But when I open up reason5, I dont see anything under the midi in/out. I uninstalled korg drivers, tried a older version and nothing. I know it works cause it was working before, my axiom 49 works perfectly without having to install any drivers. This is really frustrating. After I installed the editor, I can get a midi out port that shows nano kontrol 1- or something. At one point I got it to recognize something, as I was trying to assign controls in reason, and only one fader would work, and it worked under a 'breath' command. So .. idk. I've read other people having success not using the korg drivers and just plugging it in and letting windows download whatever it downloads and ppl say it works, windows does this, tells me its installing Korg NanoKontrol drivers, etc.. restart, nothing works.


*EDIT* Ok so I found the solution to get this working in Reason4 I havent tried it in anything else but I can only assume this should work for other things. Go to start, search 'midi' click CONFIGURE KORG-USB MIDI DRIVER, look under advanced you'll see a tab that says MIDI-IN and a drop down menu with the following options; 64bit, 32bit, BOTH! Mine was set to 64bit, changed that to BOTH. BAM! IT WORKS ALL CONTROLS !

[MrMajestic]

I got the same issue with my NanoPAD2 using 64-bit Ultimate Windows 7. Nothing works, doesnt even show up in the Kontrol Editor. I just bought this unit today

[snoodiloodi]

I have the same problem with my NanoKontrol. Using windows 7 64bit Pro and Resolume 3.

It worked a bit in the start before installing the drivers, but with them the controller is undetectable by Resolume. I've tried uninstalling the drivers, cleaning the registry (http://www.eqmag.com/article/fixing-win ... g-07/30616), plugging it into different ports and rebooting.

Nothing works and I'ts obvious that this is a well known problem. I'm very dissapointed with Korg and to be honest I don't think i'll ever buy this brand again.

[X-Trade]

Have any of you actually tried contacting your Korg National Distributor for support on this issue?

Sounds like a 64-bit problem to me. 64 bit programs can't access 32-bit drivers in Windows. So if your audio host is 64-bit and the drivers are only 32-bit... Then it won't show up.

Another problem is the 10 MIDI Device limit in Windows. There is an 'uninstall' utility with the Korg drivers for fixing this - any device with an index higher than 10 won't work.

[MrMajestic]

Have any of you actually tried contacting your Korg National Distributor for support on this issue?

Sounds like a 64-bit problem to me. 64 bit programs can't access 32-bit drivers in Windows. So if your audio host is 64-bit and the drivers are only 32-bit... Then it won't show up.

Another problem is the 10 MIDI Device limit in Windows. There is an 'uninstall' utility with the Korg drivers for fixing this - any device with an index higher than 10 won't work.

I havent contacted anyone yet, I just bought the unit.

I can select 32-bit, 64-bit or both drivers in the Korg utility. The problem is that it doesnt even show up in the Korg Editor, so of course in any other software.

Index of the NanoPAD2 is 1 so its not the device limit hitting.

[fennucci]

Have any of you actually tried contacting your Korg National Distributor for support on this issue?

Sounds like a 64-bit problem to me. 64 bit programs can't access 32-bit drivers in Windows. So if your audio host is 64-bit and the drivers are only 32-bit... Then it won't show up.

Another problem is the 10 MIDI Device limit in Windows. There is an 'uninstall' utility with the Korg drivers for fixing this - any device with an index higher than 10 won't work.

I havent contacted anyone yet, I just bought the unit.

I can select 32-bit, 64-bit or both drivers in the Korg utility. The problem is that it doesnt even show up in the Korg Editor, so of course in any other software.

Index of the NanoPAD2 is 1 so its not the device limit hitting.

I know it works cause I've used it for over a year on Windows 7 Home Edition 64bit. But I upgraded to Ultimate and now it gives me trouble so idk what is going on.

[snoodiloodi]

[quote="X-Trade"]Have any of you actually tried contacting your Korg National Distributor for support on this issue?

Sounds like a 64-bit problem to me. 64 bit programs can't access 32-bit drivers in Windows. So if your audio host is 64-bit and the drivers are only 32-bit... Then it won't show up.

Another problem is the 10 MIDI Device limit in Windows. There is an 'uninstall' utility with the Korg drivers for fixing this - any device with an index higher than 10 won't work.[/quote]

I'm awaiting a reply from Korg support. Tried switching from 32 bit, 64bit and the "both" option.

I've tried deleting the devices from the the registry before. However does anyone know why the graphics card (geforce gt 240) is taking up midi device slots?

[fennucci]

any luck?

[thefyn]

I am having an issue with nano kontrol.

It shows up in Win audio devices, but it does not show up in Sonars midi device list.

I have Win 7 64 and I am using Sonar X1 32 bit. I have tried all options in nano kontrol config program but it won't show up in my DAW.

I've tried latest drivers etc.

[fennucci]

This is getting so annoying and frustrating. I know for sure that this will work on 64bit windows as I have used it in the past. Only until recently when after I upgraded from home edition to ultimate is it giving me problems!

[fennucci]

OMG I FIGURED I OUT~ Go to start - search 'midi' click on Configure KORG-USB MIDI DRIVER, then under advanced you'll see a MIDI IN: menu and under that you'll have the options of 64bit, 32bit, BOTH. Mine was set to 64bit, changed that to BOTH and WALLA! IT WORKS! Atleast it works totally in reason4.

[action bell]

Same problem as everyone above. Selected "both" in the utility, newest drivers, under the 10 midi device limit etc..nothing.
In my pc's midi device section nanokontrol shows up and under driver properties there are 4 listed. Two 32 bit and two 64 bit. One of the 32 bit has an icon of a memo pad next to it. I assume if I could put this icon next to a 64 bit driver I would have success. However I cannot do that.
About to send it back but I'm so damn close..
Can Anyone Please Help?

[action bell]

right so i wasn't looking in the correct location for my midi devices, finally used the korg uninstaller instead of just doing what common sense would indicate, that is looking in one's device location
anyway, problem solved, finally making music again

[fennucci]

right so i wasn't looking in the correct location for my midi devices, finally used the korg uninstaller instead of just doing what common sense would indicate, that is looking in one's device location
anyway, problem solved, finally making music again

congrats man, I was just about to suggest maybe uninstalling it. Glad to hear its working! Felt great having more knobs and such to fiddle!

[adamribaudo]

I'm just confused as to why this is an issue with the v2 devices but was never a problem with the v1 devices. my nanokontrol v1 was totally plug-and-play. the nanokontrol v2 took a lot of configuration and reboots to finally get working.