Korg Forums

I've downloaded the latest driver, editor, and OS for the K, everything loaded in nicely, but...
Editor says Kronos isn't 1.6 (Kronos says it IS!)
PC sees Kronos, says driver is a-ok.
Sonar also doesn't sense K, nor does Project 5

I have checked the midi page on global, on the K. Everything is ticked, as per editor manual.

Any thoughts?

zzz wrote:
Any thoughts?

Reinstall the OS. Scooby had a problem that it wasn't fully installed (I think), but the Kronos' screen showed up as 1.6... worth a try.

i had similar problems with the editor, but suddenly it worked. Only thing is that i cant select midi channels even though i have installed the USB software..have you done that?

I've installed the lot. I'll reinstall the OS tomorrow morning, when I can see the back of the K better - it's in a dark corner - and when I'm fresher, see if that sparks something off.
Incidentally, I'm on Vista 32 bit with an EMU 1616 soundcard/ box, for those hardware fans.

Had the same issue: reinstalled the OS, and suddenly everything was "seen".

I had the same problem, I reformatted the usb drive(fat 32). Then re-copied the extracted files to the drive, re-installed and it worked. Don't know if the reformat was necessary but i did just in case.

Thanks for the replies, but now it's nearly time for bed, so I can attack the problem fresh tomorrow.

I had the same problem.
In my case I had the old Triton Extreme driver still installed. I uninstalled that with the driver utility that came with the editor.

OK, still no joy. I've reloaded the OS, which took in seconds, as the first time, and the K insists it is 1.6. It plays and performs as usual.
The latest driver is go, and the PC reports that the Kronos is plugged in, and working ok.
The editor falls down on autosense, can't find a compatible K, and justs tells me to check if its OS is up to date. It also gives me the option to set the midi preferences manually, and when you go to that, there's a single button, already checked, for "use all available midi channels", both in and out.
I have a sneaky feeling that the editor wants me to plug midi cables into the back of the EMU 1616, instead of using the usb connection, which is weird, because every other device I've used, whether synth, controller keyboard, nanopad etc, has all been picked up and worked out of the box.
I won't lie, to get the 1616 working with vista was a bitch, but, since two of us managed it, it's worked like a dream (about four years, now), so I'm tending to think editor here. When I loaded up Project 5, because that generally sees everything, what should pop up but the soundquest autosense button. Any suggestions?

Have you tried opening preferences in the editor. The manual states that some systems will not be auto detected. You may have to manually set up the control channel. Have a look…

I got that failure on my Windows7/32 Desktop PC (not on my Windows7/64 music notebook) and found out that the USB Midi device driver did not install properly.

The bad thing is that all efforts to get it installed afterwards with help of the Korg USB midi driver tools fail with an error message.
I have checked all the obvious things, like celaning the PC midi drives, with help of the Korg ulility. Still the USB driver does not install to a direct PC USB port (no Hub). I have no idea, what prevents the USB midi driver from installing.

Lou - all the pref boxes I could find were one each for midi in and out. They were literally blank, except for a (ticked) box that had written under it use all available midi channels.

Jim - my PC says the korg usb driver is fine, and that its own is the best available. With the editor receiving so many disappointing comments, I'd almost certainly not use it in it's current state, but I would like to use the K as a vst within Sonar and Project 5. Auto detect even stops that from happenning, although I havn't tried double clicking the kronos.dll from within the vst folder yet.

I thought I had the latest Midi Driver becuase I had downloaded the Korg driver for the nanopad recently. Couldn't get the editor to connect with Kronos. Went to the driver update on the Kronos page and all is well.

Can't see what all the fuss is over the editor. It doesn't do anything that can't be done directly on the Kronos, from what I see. I have a desktop computer that's a few feet away from the Kronos and I have to turn around to use it too. Probably ok for laptop users.

Had same problem, editor not seeing the K in the port setup.
Using the 'midi driver uninstall program' in windows, removed (uninstalled) one of the 2 (SV-1 and M3) still installed devices, SV-1 in this case and there was the K present for the editor!
Hope it helps

Thanks for the tip, Motic, I'll check to see if there's any other midi drivers causing a conflict. Given the current state of the editor, while I won't be delving into that as much as I'd imagined, I'd still like to use the K as a master keyboard for sonar and project 5, and use it on vst/midi tracks, rather than pure audio in. We'll see.