Windows 10 May 2019 Update(version 1903) and Korg Midi

kronoSphere · Post by **kronoSphere** » Fri Jun 14, 2019 6:58 pm

it seems that it takes a long long long time just to update a driver : please wake up Korg ! $\:D/$

Koekepan · Post by **Koekepan** » Sat Jun 15, 2019 1:48 am

RichardTRelayer wrote:Good point about HW studio, if only I could play well enough to survive in one.

You honestly don't need to.

What you mostly need is a sequencer that's really friendly, or easy to edit.

The king of linear sequencing at the moment is the Krome. Step entry, live entry, pianoroll, it's just a very flexible beast.

Alternatively, if you're more dance oriented, there's a lot to be said for the Electribe 2 as a sequencing master, especially now that it has had some updates.

In fact, it's pretty cheap (by the standards of our activities) to buy an Electribe and practice synthesis on it just to prove to yourself that you can, before then buying some external synths for it to drive. An electribe is a good master for a small pack of Volcas.

Gargamel314 · Post by **Gargamel314** » Sat Jun 15, 2019 8:47 pm

I'm frustrated with the Korg MIDI driver. It seems that every other month I go through the whole song and dance of uninstalling the device within the driver because it's "corrupted," and wow, such a pain! Since I don't really use the editor program, I'm thinking I'll dig out my old M-Audio MIDISport. I seriously had to check to make sure the KRONOS had MIDI In/Out ports!

Traubitz · Post by **Traubitz** » Sun Jun 16, 2019 3:46 am

Here's the fix. It seems to be a bug when the Korg gets assigned above midi9 internally to W10. The registry edits described allow you to move the Korg into the lower midi device numbers.

https://thedigitallifestyle.com/w/index ... 19-update/

Derek Cook · Post by **Derek Cook** » Sun Jun 16, 2019 4:59 am

Thanks for sharing

kronoSphere · Post by **kronoSphere** » Sun Jun 16, 2019 7:33 am

Big BIG thanks Traubitz ! It works fine !

Yuma · Post by **Yuma** » Sun Jun 16, 2019 5:38 pm

When I first checked the driver uninstall tool, I only had midi0 occupied by the Realtek Audio on my motherboard.
After adding Alias midi1 to the Korg Kronos driver and a restart of my PC, midi1 was suddenly assigned to the AMD HDMI audio driver of my videocard (which I have disabled through the Windows sound settings).
So I had to change the alias of the Korg driver to midi2 to actually make it work.

Funny thing: after changing the Korg driver alias to midi2 and a reboot of my PC, the midi1 "AMD" occupation disappeared:

PS) When I scroll down in the list, I do see the midi10 allocation too:

Couldn't find any midi10 alias in the registry though (did a registry wide search).

I did find the following quote on this subject on another website:

I did a little code diving, and it appears that a MIDI program natively coded for Windows 10, using the new application interface, has at least 64 MIDI ports available to it, using 64 bit Windows.
I could be wrong on this, but it looks like the MIDI interface in WIN 10 will enumerate these ports. However, the code must use the new libraries. Older DAWs and software that hasn't been coded to use the new APIs won't access (probably) more than 10 ports, though Vista had a theoretical limit of 32, and I assume 7 did as well.
I looked at both the driver code, and the API for the MIDI interface, and it appears to have unlimited ports, though this is not possible realistically. Hence my limit of 64, which is my best educated guess, based on Microsoft's documentation of the driver and API.

kronoSphere · Post by **kronoSphere** » Sun Jun 16, 2019 7:32 pm

little add : I did not even have to use the first part of the fix. I simply add midi2 and the name of the driver and it works fine, and with no need of a restart. Lucky I am
Thanks again

Diederik99 · Post by **Diederik99** » Sun Jun 16, 2019 8:18 pm

kronoSphere wrote:little add : I did not even have to use the first part of the fix. I simply add midi2 and the name of the driver and it works fine, and with no need of a restart. Lucky I am
Thanks again

I did not have to create an Alias either, it already had a midi5 Alias in the registry, so I added midi5 in \Drivers32.
After that, it was visible in the Korg Uninstall tool.
Unfortunately it is still not recognized by Korg Kontrol Editor or Ableton Live.
Hope a new driver arrives soon.

Gargamel314 · Post by **Gargamel314** » Mon Jun 17, 2019 4:42 pm

Traubitz wrote:Here's the fix. It seems to be a bug when the Korg gets assigned above midi9 internally to W10. The registry edits described allow you to move the Korg into the lower midi device numbers.

https://thedigitallifestyle.com/w/index ... 19-update/

It worked! What's a little misleading is when I did this, the Korg Driver Uninstaller showed a different device name (showed a separate audio interface named in the new port), but my DAW listed the Kronos. Thank you for posting this, you are showing up the quality control people at Korg.

Akdmeh · Post by **Akdmeh** » Mon Jul 08, 2019 9:32 am

Finally the patch has been released!
https://www.korg.com/us/support/download/product/1/305/

StephenKay · Post by **StephenKay** » Mon Jul 08, 2019 7:15 pm

Akdmeh wrote:Finally the patch has been released!
https://www.korg.com/us/support/download/product/1/305/

That does not appear to be the USB-MIDI Driver required for most of the Korg keyboard products.

Yuma · Post by **Yuma** » Tue Jul 09, 2019 6:46 pm

The more generic KORG MIDI driver can be downloaded here, but hasn't been updated yet.

Synthee · Post by **Synthee** » Fri Jul 19, 2019 1:34 pm

Finally the new update is out.
https://www.korg.com/us/support/download/product/1/285/

HardSync · Post by **HardSync** » Fri Jul 19, 2019 4:21 pm

Synthee wrote:Finally the new update is out.
https://www.korg.com/us/support/download/product/1/285/

Thanks for letting us know. :) As for the update, for me, it wasn't enough to simply update the driver. I had to completely uninstall all the Korg drivers first, then perform a fresh install to get it to work.