Korg RK100S II Editor

Discussion relating to the Korg MS2000, MS2000B & microKorg.

Moderators: Sharp, X-Trade, Pepperpotty, karmathanever

Post Reply
pjnoxon
Posts: 18
Joined: Sun Aug 06, 2023 3:05 pm
Contact:

Korg RK100S II Editor

Post by pjnoxon »

I downloaded all the software from the Korg website, The Editor is Version 1.
I tried to follow all the directions to install the Korg USB MIDI driver properly. When I turn on the RK100S II my Windows 10 computer makes that little melody that indicates a USB device has attached. If I run the Korg USB driver Uninstall utility (without uninstalling anything) I can see that the Korg RK100S II is listed as being attached.

When I run the Korg RK100S II Editor, and click on MIDI menu "Receive All Data" the program says "Are you sure to receive all data" and I click on "OK" it says "MIDI port is not specified" but I don't see any way in the Editor to specify the MIDI port? I am stumped, how do I get the Editor to work? Does it not work with the USB port on the keytar?

I never found a manual for the Korg RK100S II Editor, but I did find a manual for the previous Korg RK100S Editor (without the II). It references a "Communications Menu" but there is no such menu in this Editor?
OpAmp
Platinum Member
Posts: 1179
Joined: Fri Jun 07, 2013 10:26 pm
Location: Brussels, BE

Post by OpAmp »

Hi,

Go to the Options|Preferences... Menu. When you disable autoscan, you should see the RK100S USB driver listed when it is connected with USB.

Furthermore the RK100S should be one of the first 10 MIDI devices to make it work properly. To check that run the Korg MIDI driver uninstall utility. If the RK100 is not listed there and all 10 slots are occupied, you need to uninstall first another MIDI device to make room for the RK100S.

Good luck.
microKORGXL, Kaossilator Pro, monotribe, SQ-1, volca fm, Kross 88 BK
Alesis SR18, Akai Miniak, Fender Strat, Line 6 Spider II 112, Zoom MS-50G
pjnoxon
Posts: 18
Joined: Sun Aug 06, 2023 3:05 pm
Contact:

Post by pjnoxon »

When I click on Auto scan to make it 'unchecked' the box below it says

MIDI IN
"Not use MIDI IN device"

MIDI OUT
"Not use MIDI OUT device"

and it doesn't load All Data when I try to do that.

If I open the Uninstall utility, without uninstalling anything, it shows the
Korg driver is #10 and it says "connected"

Why doesn't it work?
voip
Platinum Member
Posts: 4002
Joined: Thu Nov 27, 2014 2:07 pm

Post by voip »

Does that mean it's actually the 11th in the list, since the list starts at #0.

Try using the uninstall utility to remove one of the driver instances.

.
pjnoxon
Posts: 18
Joined: Sun Aug 06, 2023 3:05 pm
Contact:

Post by pjnoxon »

That really doesn't make sense to me. Why would that be necessary?
It says the Korg is connected, did I mention that?

The other 9 instances are all one driver - my Yamaha MODX7 has an extensive USB implementation.
voip
Platinum Member
Posts: 4002
Joined: Thu Nov 27, 2014 2:07 pm

Post by voip »

Have a look at this link. It might help:

https://support.korguser.net/hc/en-us/a ... on-Windows

.
pjnoxon
Posts: 18
Joined: Sun Aug 06, 2023 3:05 pm
Contact:

Post by pjnoxon »

This is getting really difficult now. I noticed a driver that I didn't recognize, a tevirtualMIDI driver in the position #3, but I couldn't find any uninstall for that. I did remember something called loopMIDI that I think I never needed so I uninstalled it.

When I run the Korg Uninstall again, now instead of that tevirtual MIDI there is now a second Korg RK100S II driver preceded by the work "corrupted"in position #3! The other driver for the keytar is still in position #10. If I delete either of these drivers in the Korg driver uninstall utility, they always come back.

If I delete them and then try to use the Korg MIDI driver install, it always says "unit not connected" so I guess the keytar must be connected and turned on to use the install, but as soon as I turn the keytar on, it seems to restore the driver in position #10 AND this "corrupted" keytar driver in positon #3. How is this supposed to work?
pjnoxon
Posts: 18
Joined: Sun Aug 06, 2023 3:05 pm
Contact:

Post by pjnoxon »

No matter what I do the driver is now installed in position #3 but it always says corrupted and it does not work. I can uninstall it, but when I try to install the software always says "Device is not connected, connect device first" but as soon as I connect the Keytar, it will install the 'corrupted' driver again!

Is there any way to use the Korg editor?[/img]
pjnoxon
Posts: 18
Joined: Sun Aug 06, 2023 3:05 pm
Contact:

Post by pjnoxon »

Since I have not received the help I need here on this forum, I kept trying to find some better help on the Korg website. I went back and forth with several tech people at Korg without success.

It is clear to me that the current version of the Korg MIDI driver installer does not work the current version of Windows 10 Home 22H2 so the Editor program will not communicate with the keytar and thus I can not edit the programs.

All the posts one might find online are not valid with this current version of the Korg MIDI Driver and the current version of Windows 10. They both are a couple years old now so Korg is entirely remiss in not providing the level of support meeting customer's expectations.

Korg just doesn't care. Anyone want to buy a RK100S II?
pjnoxon
Posts: 18
Joined: Sun Aug 06, 2023 3:05 pm
Contact:

Post by pjnoxon »

Hello,

I was on vacation and now I am back but things still did not work.
I will attach information that I got from YouTube videos.

It says on Windows 11 you don't need to install anything and it will
work, but I tried uninstalling the Korg USB driver and it shows an
Audio Device when I connect and turn on the RK-100S II but in the
Editor program it still says "MIDI Port is not specified" when I try to
get all the data from the keyboard. I have Windows 10, not 11.

It also says that with the 'latest driver' once you install this one it no
longer has the limitation of only the first 10 USB slots working with
Windows 10. I had tried to access this "latest driver" but it was not
available the many times I tried to access it. Today this "latest driver"
was found at the location mentioned in the video:

https://www.korg.com/us/support/downloa ... /285/3541/

Since this was a newer driver, I downloaded it to try. When I plug in the
keyboard and turn it on, the driver launched a window asking about what
to install, and this never happened with the older driver (which was the
only one available before today). But when I run the editor and try to get
all the data from the RK 100S II, it still says "MIDI Port is not specified".
Now when I look into the USB driver slots with the Korg Uninstaller (I don't
try to uninstall anything), where previously slot #3 was empty, it now says

"midi3: Corrupted (Korg RK-100S <Connected>"

So I was back to exactly where I was before. It didn't work.
However, I decided to try looking at the RK-100S II Editor again since it may
be different from before. Eureka! The Preferences were defaulted to
MIDI IN "not use MIDI In device" but I could NOW change to RK-100S 1 KBD/RIBBON
and MIDI OUT "not use MIDI OUT device" but NOW I could change to RK-100S 1 MIDI OUT
but that wasn't it so NOW I could also change to RK-100S 1 Sound and now the data will download!

If I look with the Uninstall Utility, it still says

"midi3: Corrupted (Korg RK-100S <Connected>"

but it seems to be working?!?

I wonder how things are going to go now, with some things working, but in all windows
it refers to my RK-100S 2 as one of the older RK-100S 1 keyboards? The Editor is new
showing RK-100S 2 Sound Editor in the title bar.

- PJ

here are the notes from the YouTube video:

Ian Dixon - The Digital Lifestyle

first video was 2019 use RegEdit (included at end of other two videos)

HKEY_LOCAL_MACHINE
SYSTEM
CurrentControlSet
Control
Class
Find "Korg"
in video was {blah blah blah}
0021
Drivers
midi
KORGUM64.DRV
then "New" Alias with value "midi2"
in video repeated process in 0022 for another Korg device
then "New" Alias with value "midi3"

second part

HKEY_LOCAL_MACHINE
SOFTWARE
Microsoft
WindowsNT
CurrentVersion
Drivers32
then "New" String Value name = midi2 value = KORGUM64.DRV
in video repeated process in 0022 for another Korg device
then "New" String Value name = midi3 value = KORGUM64.DRV

second video from 2022 with Windows 10 says new driver has more slots:
https://www.korg.com/us/support/downloa ... /285/3541/
https://www.youtube.com/watch?v=GPceeevyMnU
this didn't work for me either, says "MIDI Port is not specified"
BUT within the Editor I could now Change the MIDI IN and OUT!!!
previously that could not be done, there were no other options!!!

third video from 2023 with Windows 11 says no driver need be installed
https://www.youtube.com/watch?v=p62LI4KrY-k&t=0s
when I removed all Korg drivers, the editor still didn't work
in Settings "Bluetooth & other devices" shows RK-100S audio device
OpAmp
Platinum Member
Posts: 1179
Joined: Fri Jun 07, 2013 10:26 pm
Location: Brussels, BE

Post by OpAmp »

Hi,

Good to hear you have made some progress and reported back here.
It is indeed a bit weird that your RK is reported as corrupted. I can not comment further. But if it works, it is just a name for the MIDI port the RK offers.

As a side note, I've been looking at my mKXL and the USB protocol. I can not get my head around it. The USB descriptors that I sniffed under Windows when plugging the XL really look like USB MIDI class compliant. Still it seems that Windows 10 does not accepts it as such. On the other hand, in my Ubuntu VM, there is no need to install a driver at all. My mkXL is simply immediately recognized and MIDI communication works fine. Unfortunately Korg does not deliver linux versions of the editors... Anyway, it confirms for me that the Windows MIDI USB stack has some particular quirks for which a driver is required. (But no longer for 11 as you indicate.)

Have fun!
microKORGXL, Kaossilator Pro, monotribe, SQ-1, volca fm, Kross 88 BK
Alesis SR18, Akai Miniak, Fender Strat, Line 6 Spider II 112, Zoom MS-50G
Post Reply

Return to “Korg MS2000 & microKorg”