Kaossilator Pro - ERROR: device not found

k0va5 · Post by **k0va5** » Fri Apr 09, 2010 10:12 pm

Mr36 wrote:I'm pretty sure (though not completely) that the readme or some such file that I read in conjunction with this said that it would work with XP...

thats cool then.. to be fair, all ive done with the kpro so far is jam.. not bothered using it in tunes so havent needed to link it up to the comp

SMK · Post by **SMK** » Mon Apr 12, 2010 8:51 am

OKay this is out of control here! now my KP3 is not found. Last time I got at least the ability to transmit midi changes now I cant even do that. What is the deal????? why wont any of this work any more?????

SMK · Post by **SMK** » Mon Apr 12, 2010 9:08 am

yep this still sucks!!!! My Korg midi states that the KP3 is "connected". Also when I hook up the KoPro it also show it is "connected". But neither editor will see the damn things. I even deleted the K25 drivers just to be sure. so what the hell is going on here? Please someone with solid midi experience respond, I am on Windows XP 32 bit service pack 3. thanks!

crofter · Post by **crofter** » Mon Apr 12, 2010 11:07 am

Check that SysEx is not disabled in the midi filter, that's the problem I had

SMK · Post by **SMK** » Mon Apr 12, 2010 3:00 pm

crofter wrote:Check that SysEx is not disabled in the midi filter, that's the problem I had

Ok since I can't use the computer to check for this...how do I do that on the KoPro and the KP3? Thanks!

crofter · Post by **crofter** » Mon Apr 12, 2010 5:05 pm

On the KP3( I don't know about the KoPro), press shift and button 4 (midi filter) scroll to "SYS.E" , press the programme/bpm button, if the display reads "dis" turn it to read "EnA",then press write , then try to connect to the editor, hope this helps.

SMK · Post by **SMK** » Mon Apr 12, 2010 9:14 pm

crofter wrote:On the KP3( I don't know about the KoPro), press shift and button 4 (midi filter) scroll to "SYS.E" , press the programme/bpm button, if the display reads "dis" turn it to read "EnA",then press write , then try to connect to the editor, hope this helps.

Thanks I'll try that later.

SMK · Post by **SMK** » Wed Apr 14, 2010 8:20 am

crofter wrote:On the KP3( I don't know about the KoPro), press shift and button 4 (midi filter) scroll to "SYS.E" , press the programme/bpm button, if the display reads "dis" turn it to read "EnA",then press write , then try to connect to the editor, hope this helps.

FRAKK!!!! I tried this and still does not work...damn this sucks!!! is there some one else that has better input on this. This a real problem!

Radian · Post by **Radian** » Wed Apr 14, 2010 10:21 am

Mr36 wrote:You're welcome, Mr. Radian.

Are you still returning it then?

It's still hanging on here (by a thread). I think I'll give it a while to see if there's a firmware update and if not ebay it. In the meantime I've begun a little electronics project specifically for external midi control. I'll be posting about this later.

Radian · Post by **Radian** » Wed Apr 14, 2010 10:46 am

SMK wrote: FRAKK!!!! I tried this and still does not work...damn this sucks!!! is there some one else that has better input on this. This a real problem!

My problem that prompted this thread was evidently a bug in the Korg midi driver utilities circulating at the time of the KPRO launch. The link Mr36 provided to the KorgUSB-MIDI_DRV_PC_1_12r2.zip driver utilities was only recently put up by Korg and uninstalling the earlier driver and installing using this latest version finally made the KPRO play ball.

You may already be aware of the limit of 10 midi drivers in windows which gets used up if you have lots of drivers or swap your gear between different USB ports. Because of this you may need to use the supplied utility to uninstall some driver instances that aren't used and then plug in and install the driver again. This is the usual reason people get the "device not found" error and was the only problem tech support knew about.

So in summary, plugging in a KP3 or KPRO to a particular USB port for the first time causes windows to load default midi drivers for that connection. If this is the tenth or more time this happens you will need to uninstall a previous driver instance. Any device showing default windows drivers (as seen by using the uninstall utility to view the devices) needs to have Korg drivers loaded using the install utility. If the utilities are those supplied in the zip file mentioned above, and not a previous version, it should work for you like it did for me (XP, SP3)