Connecting KP3 to editor: KP3 is not found.

[Indreamslikethese]

I am running x64 Windows 7.
I'm connecting via USB slot on the back of the KP3.
I have got the latest drivers and latest update.

When I open the KP3 Editor, it runs correctly but when I click RECEIVE I get the message: KP3 is not found. If I click MIDI menu up the top and click Preferences... there are no other options for MIDI in and MIDI out other than "No use MIDI In port". I have also tried with Auto Detect on.

The computer recognizes it as an external hard drive when I use USB mode though so the USB port is functioning fine.

I've spent hours trying to fix this. If anyone can help it would be amazing.

Edit:
If I plug from my USB port to MIDI out on my Kaoss Pad I get more options in the MIDI in and MIDI out on KP3 Editor. There is Microsoft GS Wavetable Synth and GH MIDI Interface. If I change to these and click Receive, it says that the USB driver is not installed, which it is. Regardless, if i click the program to install it, it says there is no device connected so it cannot install anything.



Edit:
The solution has been found.
The steps below to clear the midi registry and uninstall and reinstalling the driver were successful once I changed the settings in KP3 Editor to "Auto-Detect" the device.

Thanks for your help.

[Marxon]

Hi Indreamslikethese,

please check if the sysex option in kp3´s midi-filter menu (shift+4)
is set to enabeld.

best regards
marxon

[djzachtyler]

Hello.

I am having the same exact issue.. I have verified midi settings on the KP3 and still get the "KP3 not detected" issue.

Was just about to start a new thread, but will hijack this one. I read somewhere else this is a known issue with Windows 7 64 bit, regardless I need to get my KP3 working as I just bought it yesterday and want to verify it has the latest OS, etc before I get too far along wth using it in my recordings.

I do have the latest Driver and editor downloaded from the Korg website as well.

[mesoboy]

This could be due to how many MIDI ports Windows has already assigned. The Korg USB MIDI drivers cannot recognise more than 10 MIDI ports. Check in Control Panel to see if you have more than 10 (you may have a bunch of virtual ports assigned via MIDI-OX or something), delete some of them and then reinstall the USB MIDI driver. These should then 'assign' themselves to the freed up ports and, being lower than 10, these should now work. Afterwards you can hook back up any other MIDI gear which will get assigned to MIDI ports 10 and upwards.

[neotechtonics]

what mesoboy said: have a look at threads on MIDI driver issues for the nanoseries controllers cos on numerous occasions I have posted replies about the 10-slot problem (which is a problem I had with the KPRO and KP3 as well as the nanokontrol1) but the first step is making sure Sysex is enabled on the KP3/KPRO so that your pc can communicate system exclusive data to and from the pad.

[djzachtyler]

I'll check that when I get home as that may very well be my issue as I have numerous devices I have used.

[djzachtyler]

Ok being a windows sys admin I feel like a total knob head for nort knowing this, but does anyone know where the Midi device data resides in Windows 7? I have looked all over in the device manager and only see the info for my automap devices etc.. if that is what you are referring to there are only a couple items listed, and nowhere near 10..

[Skelten]

This is the exact same problem I've had for quite a while, seems to be a consistent error in Windows 7 64-bit. I've forwarded my system specs to Korg Tech Support weeks ago and have yet to hear back, and due to living in a different time zone and conflicting work schedules I've been unable to contact them directly and all e-mails I've sent have gone unresponded.

The midi device location mentioned earlier is in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32 and the registry values in question are named midi1, midi2, midi3, etc.

Another location to check is the Korg MIDI/USB Uninstall Tool located by default at Program Files (x86)\KORG\KORG USB-MIDI Driver\UnInstDrv.exe" I believe, after clicking along the dialog boxes it will bring up a list of currently installed USB midi drivers that are installed. In my case I show the drivers installed but labeled as corrupted.

In the Device Manager do you see the KP3 listed? Does it pop up as attempting to install device and then say unable to find drivers when plugged in via USB or are you even able to install the USB drivers for the KP3? You might want to try manually installing the drivers for the KP3 by going manually pointing the drivers to install from the INF located in Program Files (x86)\KORG\KORG USB-MIDI Driver\ when I do this I'm actually able to install the drivers for my KP3 but am then greeted with a This Device Cannot Start. (Error Code: 10) message, and still the same problems as before.

Do you have any other USB midi devices hooked up? Perhaps something by Native Instruments or Akai? As I said before I've had absolutely zero luck fixing what seems to be the same problem you have, these are just steps I've attempted to fix my situation and perhaps they will be helpful for you. But at this point it seems to me like it's some sort of issue with Windows 7 64-bit handling USB-Midi that is causing a conflict somewhere, at least that's my absolute last guess... I've honestly exhausted myself on the search for this fix.

[djzachtyler]

Hey man I agree wwith this possibly being a 64 bit win 7 issue... I tried updating the OS on my KP3 today and had to pull my old 32 bit laptop out of mothballs to get that done as the updater is absolutely not 64 bit compliant.

As far as the device manager... it actually shows the device as connected and the driver as installed when it is powered on and connected.

All I see in the list is "Novation automap", "HUD Automap", & "Reason Automap" all of which would be related to my Novation 49SL Mk2 controller.

In all honesty I cannot fathom having more than 10 devices connected anywhhere as I just recently rebuilt this system and to date have only connected the Novation Keyboard and now the KP3.

Thanks for the update in the registry location... that will definitely be helpful for others who stumble across this problem. Hopefully with this thread we can help others get a definitive answer to this issue cause nothing out there completely covers all aspects to troubleshooting this...

SIDE NOTE - regarding windows Registry I am going to recommend that unless you ABSOLUTELY know what you are doing in there I personally do not recommend making changes. Ask for help!!! (I am always glad to assist with windows issues so PM me if needed.)

[djzachtyler]

Ok so what fixed the issue for me was as follows.

First launched regedit.exe from the run dialog & navigated to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Drivers32

before making changes I went to "file" > "Export" and save a copy of my registry to my desktop titled "Midi_FIX.reg"

Next in the registry location above I deleted the values midi4 - midi9

going to the folder location C:\Program Files (x86)\KORG\KORG USB-MIDI Driver and run "UnInstDrv64.exe"

here you should see a list of ports. select the KP3 entry...
(In my case it was assigning itsself to ports 10 & 11) now connect the usb cable for the KP3 and power it on and wait for drivers to reinstall.

Last Launched the KP3 Editor and clicked "All/Receive" button and no longer had an issue KP3 was recognized.

Please keep in mind this modifys the system registry and can delete your other deviices... I experienced an issue with Reason no longer seeing my control surface corretly and had to make some adjustments.

first I clicked my exported registry file mentioned above to restore my registry... rebooted computer...

When you run the UnInstDrv64.exe from the KORG folder in program files you will get to see a list of installed devices... listed from midi1- midi10 (or greater)

In order to get around deleting all my devices I looked for an generic entry for "USB audio device" which presented itself on midi3 & midi4

after identifying those I then went back into regedit and deleted the string value "midi3" then made sure I had deleted the KP3 from the UnInstDrv64. exe utility.

next I went back to regedit and right clicked on the folder on the left "Drivers32" then selected "New" then "String Value" and named it "midi3" to replace the value previously deleted.

I then powered up the KP3 let the computer detect it and launched the editor. KP3 connected with no issues.

Just to verify all of this I rebooted again after the computer booted back up powered up the KP3 launched the editor and was able to transmit and receive data.

***NOTE*** where as I reference "midi3" could be any of the midi strings in registry... I Highly recommend you use the driver uninstaller to determine which string is attached to a generic device (M-Audio Uno can reserve these spots for example) The important thing to note is that the KP3 MUSTt be attached to the midi1 to midi9 string... even in my case with it attached to midi10 it failed to get seen by the editor.

Thank you to all that helped add to this post and I hope this solution helps others resolve this problem in the future. I also did a factory reset to my KP3 and without changing any settings on the device itself was able to connect.

for info on factory reset

1. Press 1 and 2 and Sampling while powering on the KP3.

2. PrLD will appear in the LED.

3. C will be on, D will be flashing.

4. Press D.

5. urt will flash in the LED.

6. P.off will then appear in the LED.

7. Power off and on the KP3, enjoy factory reset goodness.

Cheers and thanks a million to all those of you whom helped me get this fixed

[neotechtonics]

maybe now i can dig a little in the registry to get my NI-S4 working again cos after i uninstalled its drivers to get my nanokontrol and KPRO working... computer says NO! no matter what I do with the drivers the audio works fine but the midi drivers for it dont work now... so its basically a massive, expensive, audio-interface at the moment. I'm inches away from just formatting the whole damn thing and starting again.

I hate software sooooo much.

[djzachtyler]

agreed... it gets to being a real nightmare to sort some of these things out...

This is why I also HAD to mention that registry changes can become a convoluted nightmare ti get sorted...

sometimes deleting isn't the best answer.. deleting and recreating a blank entry is what is needed. Especially in the registry as it effects Windows on a global scale.

If you do go the format and reinstall route.... go 32 bit lol... what with all the issues I run into with trying to run a DAW & device drivers, editors, etc. on a 64 bit platform.. I wish I was still running XP as with older gear they just do not focus on supporting it, or at the very least developing legacy support for new systems.

[neotechtonics]

just another reason I'll always stick to hardware. TRUE plug and play.

[djzachtyler]

just another reason I'll always stick to hardware. TRUE plug and play.

"LIKE"

[Owundubbelyew]

i too try to keep my music creations separate from my inevitable issues with my computer. but the hardware seems to still be dependant on the software and the firmware that i apparently need to buy a new computer to install. correction: i need to buy an old computer.