Page 1 of 1

USB-MIDI Driver Info

Posted: Wed Nov 13, 2019 6:49 pm
by Ron
I probably missed earlier posts on this subject but thought I would mention my recent experience in case anyone else is having similar problems.

Seems the Win10 1903 upgrade earlier this year screwed up the Korg USB-MIDI driver as evidenced by neither SONAR or BIAB recognizing my 4X or KRONOS as MIDI in/out devices. Lots of info on line about what went wrong and how to fix with register editing.

Since then Korg issued an updated driver (v31) to solve the problem. However, this new driver did not seem to solve my problem.

While poking around more on line, I learned that v33 was available on the Korg Japan support page. Removed v31 and restarted, installed v33 and restarted … all seems OK again.

For info - file transfers never quit working … only the MIDI I/O.

Posted: Thu Nov 14, 2019 4:03 pm
by keith-helen
Hi Ron
If this solves a problem . would it be possible for you to provide the link so that other members may download.

Best wishes

Keith Lawton

Posted: Fri Nov 15, 2019 11:02 am
by Ron
Hi Keith - good idea.

This link below is for the Korg USB-MIDI Driver for Win10 v1903. It is from the Korg Japan Support web site. Scroll down to near the bottom of the page for the download.

https://www.korg.com/jp/support/downloa ... /200/3540/

I checked the Korg US Support site just now and the latest driver shown for Win10 is still V31. Did not check Korg UK.

Not sure why only Korg Japan has v33 but it did solve my problem. Be sure to remove the old driver and restart before loading the new.

Ron

Posted: Fri Nov 15, 2019 7:46 pm
by Tom04
Hi,
two more things, that can cause problems with the USB Driver:

1. connect the keyboard directly to the pc, I had made a connection over a USB-Hub, and this DIDN'T work.

2. check your USB-cable, it should not be longer than 2,5 m to avoid problems.

In my case, I installed,de-installed and re-installed the driver 3 times and in the end it was the "usb-hub".

Posted: Sat Nov 16, 2019 6:09 pm
by Snoopy
Hmm, strange,

in my Win10 1903 the driver 1.15.r31e worked.

And he does also in Win10 1909 ( available since a few days... )