How to get the KORG MIDI USB Driver to work with Windows 10
Вставка
- Опубліковано 5 вер 2024
- Here is a quick guide to how you can get the Korg USB MIDI driver to work on your Windows 10 PC or any previous version of Windows if you are having problems. Unless this driver is working correctly, you will not be able to use the Librarian software that Korg supplies for the Minilogue XD, Prologe and Nu:Tekt synthesisers.
Still needed this tutorial after 3 years. Thanks Tim and... c'mon Korg, let's do something for these drivers!
Me 2 - ridiculous - had problems after an ableton 11 crash where the driver broke and after that decided to be on page 2 -.-
Back in 2024, even now it is not fixed...
This is really bad on Korg's part. Spent over an hour trying to resolve. Thanks for your help Tim.
How much time did KORG have the pandemic and couldn't rectify it LOL!!
I wish this clip would’ve been the first I saw this long evening of solving problems😂
Thank you so much!
Priceless educational, time-saving and de-stressing work here. Thanks Sir.
October 2022 and Korg still have not fixed this issue. Thank you Tim for this, saved me so much time.
This is absolutely crucial information when debugging midi devices. I have spend several evenings trying to get a Minilogue XD to work on midi driver slot 10... Thank you SO much! 🎵❤🎶
Many thanks for this Tim. Have lots of midi gear and just can't understand the logic by Korg making such a mess of this and not extending the limit to 50. Really will put me off buying their gear in future. Other manufacturers gear took seconds, Nautilus took hours instead. What happens if more than 5 pieces of Korg gear as some of my slots the software didn't let me remove. The best gold dust in your video Tim is that you can safely delete all other entries where it's allowed and they will rebuild themselves once reconnected. Had entered my head but had reservations as literally lots of other connections I didn't want to risk screwing up. Had to reinstall a SSL UC1 but eventually got it all sorted just to keep two pieces of Korg gear happy. Bonkers design and I am still doing this 2 years after your video was released. Thanks again
THANK YOU SO MUCH SIR ..... I spend a whole day in solving but atlast your video was the only one to recover my issue.
Thanks, Tony Stark.
Haha. I need to grow a beard!
@@TimShoebridge I have manually set my midi ports to 1 and 2. it does connect to my computer. Everytime I try send and receive data it is still not reading my midi in and midi out ports. For windows 10. Any help??
Hi milkyy Waey I had the same problem and it costs me one weekend! You have to go to the registry -> find driver (windows NT) -> delete the generic windows midi driver 1 and 2 -> close the window -> install the Korg driver once again -> the minilouge appears at position one -> ready to play
More like a Simon Cowell
7:25 was the moment my issue with Korg MicroKEY 2 -> Reaper DAW was solved: I simply had too many MIDI connections without any use. The Korg uninstaller actually was able to delete these old connections as well, so everything is working as it should right now. Before this video Reaper was not able to find the keyboard no matter how many times I deleted and uninstalled it from Win10. So multiple thanks, Tim! Keep it up. 🙂
May your mixes always be clean and your project files never corrupt. Thank you!
THANK YOU SO MUCH!!!!. I bought my Minilogue XD Module half a year ago and I only decided today to connect to my PC and fool around with the Sound Librarian. Couldn't get it to work and I was so frustrated after reinstalling the drivers and the software. Reddit pointed me to this video and your instructions resolved the issue. Life saver!
Thank you for this. How in the heck has Korg not fixed this yet.
3 years later... you're a life saver. Thank you!
ive searched the entire internet and this is the first video or resource to resolve my issue!
Several hours of desperate struggling... then I found this video. Thanks a lot, Tim!!! And for your entertaining, instructional synths vids! 🙂
at the beginning, watching your video i felt so hopeless doing the procedure like you instruct. Formatted my whole system and it worked fine.
After its auto updates i saw that error coming up again. Almost before quitting, i found your video again and decide to give a try.
Cannot believe that it worked so fine. Thank you Mr Tim YOU ARE LEGEND.
finally i can use my midi on cubase.
Thank you so much for this! I was about to throw my xd module across the room but happened to stumble across this just in time. Got it working just fine😁
Oh my god! Thank you sooooo much. I got the Original Minilogue delivered yesterday and have spent all that time and today trying to get it going in Ableton. Thought I was going to send the synth back but this has worked. Unbelievable! Thank you very very much
Many thanks, Tim. That was incredibly useful. I was tearing my hair out trying to update my son's Monologue and couldn't understand why it wasn't detecting.
Fantastic tutorial, thank you so much. After using a Keystation 88 MIDI controller to learn, I have just bought a Korg keyboard, and was a little frustrated that it wasn't recognised. This is something I would never have worked out on my own. Thank you :D
Wow this quarter hour or just over, has made my life so much better. Many thanks
Thank you so much for this. I finally got my monologue updated. I was about to lose my mind.
I've got my NTS-1 today and it was driving me crazy why Windows wouldn't recognize it (while Linux did). Even with the Korg driver installed in Windows! A post on the internet brought me to this video.
What an absolute ridiculous decision by Korg!
Thanks Tim, for sharing the way on how to solve this problem.
After a couple of days search with no joy, this finally explained things - thank you so much
Having spent several hours attempting to install a Korg Nanokontrol 2 and when it was finally working in Reaper found that my Roland MIDI keyboard was no longer working, your explanation of the KORG MIDI driver uninstall utility was really helpful. All working now. Thank you.
I struggled for a month with this driver. If I hadn't found this tutorial, I would have been fighting even longer. THANK YOU!!!
You have undoubtedly saved many Korg devices from being defenestrated. Many Thanks!
Thank you so much! It worked straightaway with the Microkey...no more messing around with regedit or other things. Incredible that Korg still hasn't fixed that issue in 2024.
Thank you Tim,
My Daw was not listed my Korg as midi. I was searching for the solution in Korg forum. No solution. Then I watched your video. Problem solved.
I appreciate your time and effort for making this video.
This is the best video on this extensive problem. Thank you for the deep dive and full explanation!
I just spent way more time than I possibly ever should have trying to get these damned drivers to work, but you’re video has just saved me from pulling my hair out as a last resort. After God knows how many hours and accidentally stumbling upon your video, I now have my Korg keyboard connected and drivers running properly. Words can not emphasize how thankful I am to you kind, sir.
Thank you, thank you, thank you, smart kind man!🙏 I've spent three days trying to receive a midi-signal from my Korg, and I didn't know that the problem was in slots...After your video, it works!!!
Tim i can't thank you enough for posting this video,, after spending weeks trying to get the Korg Nano control studio to work as it did a few months ago was IMPOSSIBLE ,,,some on you tube i watched many videos some even saying go to ( reg edit etc wow way above most guys) ,the hours i spent trying to get the korg working again . At one point it was choice between throwing the korg up the wall or boxing it , even thought it was my studio one daw then i followed you video and it worked,,great work Tim ,,regards ste
Amazing!!! Thank you Tim, I was going crazy because I didnt understand why my computer didnt know my device!
My respects to you! Greetings from Argentina
3 years later this just saved me from so much frustration with my Minilogue bass
Hey Tim, thanks to you this is now also solved. I almost let myself be taken by another video, where the solution lay in manipulating the Windows registry. Wow, glad I found your video. Your explanation is so calm and without a word too much that it is very easy to understand. Will definitely check out your other videos. Thanks again.
say i did go into the registry and deleted midi1 like in the video you're talking about... is there a way to undo it? the nanaokontrol software cant find the controller anymore and neiter can arena resolume
jesus christ thank you so much i just did the thing and it works now
I bought a Korg m3 about 5 years ago and was resolved that I could not use their Editor on Windows 10…frustrating. I actually was going to sell it because it’s so difficult to use the touch screen and is very complex as far as programming anything. After finding this video, I now have a fully working editor on my Win 10 PC and it’s like I have a whole new, super powerful synthesizer to use! Just being able to see and select all the patches and combis on screen gives me a whole new appreciation for how deep this synth goes. Thank you Tim for the guidance on how to resolve the USB driver issues with Korg. (Not sure why I didn’t find this 3-4 years ago, but better late than never!)
Tim, appreciate the time you took to record this and share, without it I would have spent a long time scratching my head and more than likely giving up on finding a solution. Working perfectly now.
Tim Shoebridge saved my life. Thank you for this video
Great video Tim! Managed to get my NanoKontrol2 connected to Studio One in Windows 11 after a week of faffing around. Keep up your very helpful vids.
Thank you for this. Everything was running fine until I foolishly tried to install the latest Korg driver earlier today which made my prologue 16 USB not show in Nuendo. Thankfully I found your video Tim. Keep up the good work.
Still helpful even though I consider myself and experienced XD user. Recently I wanted to use Sound Librarian for the first time and realized I needed help. Thanks!
I might be behind in time, but this video has made my day. I have been close to throwing away my Korg Midi Controller...oh for the love of people like you.Thank you much and must also give you praise for your Dreadbox Typhoon videos...so so helpful
I've been scouting around for info on connecting a Minilogue (same driver) to my Windows-based DAW, to record a duo who use some electronica hardware synths in their sound. I found the driver, easy, but I'm so glad I found this video, too - Thank you
Bless you Tim. The Korg / Win 10 driver problem has driven me half bonkers. Now I can use my little Nanokontrol Studio again. Cheers.
Thanks Tim. Such an informative and easy to follow tutorial. I remember following this tutorial about 4 years ago. I sold my monologue a year or so later but I really missed it. I purchased another last week and had exactly the same problem. You would think in 2024 that Korg may have put a fix in place for this issue but no! Also mine was shipped with the first firmware and I needed to update it to version 2.0. Again in 2024, I would have thought it would ship with the latest firmware. All good now. Thank you again ✌️
One More SUBSCRIBER Here! Blessed to find this Video! My mind was boggling trying to figure out why I couldn't connect the Minilogue with Ableton. Gracias!
Excellent video as always. I think I can offer some small insight as to why this can become a problem. This is NOT a Korg driver problem. This is a Windows problem and it's been one for a very long time. Windows (going back a long way) has a limit of a total of 10 USB midi drivers . Normally, this isn't a problem because when a midi device (connected via USB) is disconnected, it 'deactivates' that driver and frees up a slot. This doesn't always happen though and can lead to easily having more than 10 drivers installed and active. The results is that you connect a class compliant midi USB device and it's not visible to whatever software you're trying to connect it to. Very frustrating and often hard to troubleshoot. The ONLY solution to my knowledge is to use the Korg driver uninstall tool - exactly as you describe. It's the ONLY tool I know of that can remove these drivers, regardless of manufacturer.
I have a ton of USB midi devices and run into this problem regularly. I use driver uninstall tool so much that I have it pinned to the Windows toolbar all the time. Korg could charge for this tool and I'd pay!
I hope lots of people bookmark this video because it's the only reasonable explanation of this tool I've seen.
Hopefully, Microsoft will address this issue at some point. OSX and Linux have had no limit for years. Windows should be able to handle this more elegantly. At the very least, Windows should give you a warning, indicating that you've hit the 10 driver limit. Instead, it acts like the device is working - usually even visible in the Windows Device Manager. It just doesn't work when you actually try to use it.
Hi Gregory, Thanks a lot for commenting. There's something I am confused about, when I look at the list of MIDI driver slots using the Korg tool I see USB midi drivers and non-USB midi drivers. My impression of Windows 10 is that you generally see more non-USB drivers in the list which is why I guess it is more of a problem with Windows 10 as these non-USB drivers never get removed? But also, regarding this 10 driver limit, if it really is a hard limit in Windows itself then why can I successfully use drivers that are not in that top 10? I don't recall any other driver ever having an issue other than Korg's.....?
@@TimShoebridge I'm not sure how you would see a non-usb midi driver here - or anywhere else for that matter. What I'm used to seeing is two types of things in here: instruments (your Minologue XD for example) and midi I/O from USB connected devices. I use a couple of Saffire Pro 40 interfaces and for example, each of their midi I/O sets show up here. If you connect an instrument to their DIN connections, there's no driver related to that instrument. You're just passing midi back and forth over the midi I/O driver for the device you're connecting with. I'd be curious to know what non USB drivers are showing up on that list.
Regarding the visibility of more than 10 drivers. I should be more clear. It's not that Windows can only have 10 USB midi drivers active. It's that it can only address 10 USB midi drivers. This is what I mean when I say that Windows should handle this more elegantly. You can often see more than 10 items in this list (or in Windows Device Manager) but that doesn't mean they work. In fact, the only indication that a device isn't working is typically that it doesn't work! I know that sounds silly, but it's often the case. They look fine and the more you drill down into them, they continue to look fine. But when you try to connect to software, nothing happens. Superbly frustrating at times. The only answer I've ever found is to remove drivers till you get below the limit of 10 and letting your device reinstall its driver and this Korg tool is by far the easiest way to accomplish this.
@@TimShoebridge You may find this article interesting. www.harmonycentral.com/articles/modules-and-midi/solving-the-windows-midi-port-problem-r309/ It's older. Really about Windows 7. According to Craig Anderton, the limit was upped to 32 (I've not seen that myself) but it may well explain why you see more than 10 items in the list - even if many don't work. I have a theory now though. Perhaps the Windows dev team upped the limit for installed drivers to 32 but didn't change the number of addressable drivers from 10. That would lead to having loads of drivers installed with only some working at a given time.
@@geebake The list contains MIDI device drivers not just USB ones. It is of course very common for external devices to connect by USB but that's not the only way. And you also have hardware internal to your PC, either integrated into your PC motherboard or else installed into a PCIe slot. Many advanced video graphics cards for example will have multiple MIDI interfaces for playing in-game music and these MIDI interfaces all require drivers which will show up in the list.
the uninstall tool will not let me delete or move any of the other drivers except the ones related to Korg
Hey, thank you so much! You saved me HOURS of searching forums to get my driver to work.
Man thank you so much, I was more stuck than a stuck person in stucksville!
Thanks a lot Tim, finally solved the problem of my Krome not being recognized by my DAW or the Krome Editor !
My man! It's 2023 and this problem live on, now on Windows 11.... Thank you!
just got this unit, and i had so much trouble with this issue, not to mention the unreadable fonts in librarian. Thanks for the help man !
Super useful. I was about to give up on my NTS1 prior to finding this vid
dude. dude!! i burned some quality hours this weekend pulling my hair out as to why i couldn't get korg's own software to see my NTS-1. turns out all i needed was this video.
THANK YOU!!!!!!
This 2019 advice still applied in 2022 with the Korg USB Midi driver version 1.15 r45e - Tim, thank you soooo much for this.
Not for me.
I followed all steps. My Monologue is now properly listed in Ableton Live 11 but neither sends nor receives any MIDI data.
Before i trash my PC's registry I'm gonna sell the lil bas(s)tard.
man you saved my life with that goddam korg editor that didn't show up my sv-1 library, thank you so much!
This video still saves me to this day. What a pain with this Korg NANO studio. I have MANY MIDI devices, and as this process is the way to go, I would think KORG would have fixed by now.
Hi Tim. Terrific but simple explanation. I was using My KORG Pax76 with no problems on my iMac but when i decided to connect it to a new Windows PC I couldn't understand why it would not work on my PC in the same way I do have a lot of USB midi gear in my home studio so i could see the problem as you outlined it straight away .All is working great now with my Pax appearing as a Sound Source and as a Keyboard in my DAW as it should. I'm a little surprised and disappointed that Korg don't mention this issue as far as I'm aware but thank goodness for people like you who are willing to share your knowledge. Regards. Alan
Omg.... after so much messing around trying to get my device working... I had no idea about this device list issue...
You're a Life saver.
This helped me to easily get my Kronos and PC playing together nicely over MIDI again, and saved me from having to mess about with the registry. Thanks very much.
I spent 2 days on this with the Korg Kross 2. I got the new Software editor update, The new system update, The new driver. I used the configure driver software. Nothing worked. Until you located the midi driver uninstall location. There I found 15 drivers, some from obsolete Mbox software, which i deleted & also 3 Korg Kross drivers. I deleted the old ones. This freed up some space in the list allowing the Korg driver to go higher...And it worked. Yaay😄 I then managed to reinstall my user bank & Favourites which I had wiped out with a web sound file. !! phew. You are a Korg God.
Hello, I'm Brazilian, I understand almost nothing in English and I used the translator in your video, I spent exactly 3 hours writing down everything you said, I came back to the video all the time and I was able to update my korg X50, your explanation of the midis channels were fantastic, I read in a forum that the x50 had to be on channel 1. Well, thanks, it helped a lot someone here in south america, BRasil!
Thank you so much for this super helpful video! I’ll take this opportunity to express my gratitude to your inspiring and informative videos throughout the years. ✨
thank you so much. thought i was going crazy but your explanation was the only one that worked for me.
Thanks, Champ! I appreciate you for existing and creating this content. VERY USEFUL!!!
In my computer I just
1. Removed all korg drivers using the midi driver uninstaller (had a few from my previous attempts)
2. Uninstalled the iriun webcam app (uses your phone as a camera), it had like 5 entries in the midi list
The Korg driver monitor immediately popped up asking to install the X50 after uninstalling Iriun, I clicked install and my X50 editor software worked like charm after that.
Thanks heaps! This was quite the pain
You Sir are a life saver, Thank you so much!! I've been trying to fix my connection issues for months, had no idea it didnt work if the minilogue was higher than 10th in the list :O !!!
I had this working fine for over a year. Windows 10 recently updated and I thought maybe it screwed something up. I updated the Korg drivers but still the error. Turns out an Automap utility that came with my Novation Impulse controller is now hogging up the three of the first ten slots! So I removed those and disabled Automap (haven't used it in the last 5 years). Glad I found this video again! :-) Don't ever delete it!
You saved my life! Would never have guessed it myself and was so desperate to get my old M50 working. Thanks!
I have an M50 for many years and have never gotten the editor/usb midi driver to work. I'll download the driver, reboot, and it will say "driver not installed". I've gone through several versions of windows with no luck. I'm now running win 11. The biggest reason I'd love for this to work is to be able to use the M50 as a vst and choose the banks and patches for prog and combi sounds. I was able to find an instrument definition file for the M50 someone had created a while back but unfortunately, it only had the prog banks and patches, none of the combi's. Hard to believe after so many years that there isn't a complete, correct .ins file for the M50, but I've searched like crazy and cannot find one. Since I read your comment that you had success with the M50 following the instructions in this video, I might go ahead and give it a shot. If there's anything else you think I'd need to know, I'd appreciate if you could let me know. Thanks very much.
Fantastic. Fixed my issue. You saved my weekend and potentially an XD :)
How do you know this??? I wandered on youtube for 5h just waiting for someone like you who say "just check there, if it's not on the first list then put it in. else it won't work..." thank you so much!!!
I almost got convinced that my midi was meant to get back on my bookshelf for another 5 month at least.
This is really a game changer. Thank you Tim. makes my old Korg Pad Control work in win 10
Wau !! I had actually a problem and spended two day trying to get a solution for my nanoKey studio then I discover this tutorial that changed my life. Thanks Tim for your videos always interestings
Thank you so much Tim, quite happy I came across your video quickly, otherwise I think I would've struggled for long
Thank you Tim. You saved a lot of time for me! It is absolutely not obvious why it works once and after driver reinstall suddenly not. You described the reason why. Really helpful tutorial.
Thanks! I was going crazy because my Korg Kontrol Editor couldn't recognize my new Nanokontrol and this was the solution. You are an angel
Thank you, Tim. I've no idea how you worked this out but I'm very grateful. I've been trying to get my SV-2 connected to my Windows 11 PC for over a month. Korg Support were unable to offer any advice. I have referred them to your video.
Thanks for this! I was trying to get the Korg MicroAir2 to show up/work on Bluetooth. I must have had about 20 drivers ahead of it from other products. Removed them - Finally it is showing up!
Thank you, Tim Shoebridge! I was getting pretty frustrated, trying various approaches to correct this issue that weren't working for me. You demonstrated it clearly and it worked great!! I was especially concerned that I might never get it worked out because I have the original version of the Korg nanoKontrol and it seems that no one had advice as to how to get that one working with Cubase. It is on that long list of Korg products that the current driver covers but still I was not too hopeful. It's working perfectly now, thanks to your video. Much appreciated!!
Thanks, you saved my day! After disabling a few devices my three nanos are finally working.
Thanks for this video, Tim. You saved my sanity today as all my Korg’s stopped talking to my PC, yet audio links were still active. Thanks again.for this excellent explanation.
Just came by to say a hearty thanks for this. Like so many others, I was gurning at the screen with frustration, but here you are, with your Zen like calm. *Salute*
THANK YOU!!!!! This was the difference between enjoying my SQ-64 or sending it back....
Thank you so much! Needed this to get my Kronos to connect with my computer. Struggled for a bit, found this quickly and it did the trick...perfectly!
Thank you Tim for this video. My driver worked for ages on my Korg Kronos. I added some other USB kit, moved house and when I pluged in the Kronos the USB driver was gone! Great fix and it reminds me of the old DOS IRQ's that only allowed 16 devices and some had to be at a specific Interrupt address. Also great channel, thanks for all the excellent content.
Thank you very much. I tried everything to get my Windows 10 PC detect my nanoKontrol2 and this was the information that worked. I had several instances of things like Yamaha Steinberg USB drivers and uninstalling them was the trick.
Well, I spent 2 days trying to solve this issue therefore I blew some fuses, it was a great help, Thanks.
Very helpful. Was trying to find a way of doing this without directly hacking the registry. All my devices are now working correctly. My PadKontrol has been sitting in the drawer for over a year because of this Window midi issue.
Great - this fixed my issue - I had midi0 to midi13 used up - So unplugged the game controller / usb webcams / headset / external soundcards which were all using midi device channels - uninstall them once they were unplugged using that Korg uninstaller and then plugged in my Korg which then put it on midi5 and now it works again - Nice work!
Saved hours of my life with this video. Nicely shot too
Just bought an SQ_64 sequencer and as with your synth, it wouldn’t connect to update. MIDI driver had installed into the 11th slot on page 2. Followed instructions in video and hey presto! It worked. Updated to version 2.02. Thanks for the tip Tim. 🙂
Thank you so much
I would never have found it without you, thank you so much
This was the best and clearest explanation that I have seen!! Thank you so much for your efforts, this solved my issues with a newly acquired Korg Kross 88
Thanks very much Tim for posting this video. I couldn't figure out why I didn't seem to be getting midi out from my Korg EK50 but after following the steps in your video I was able to resolve the problem.
Thank you so much! Trying to update my SQ 64 was driving me nuts. This was the only legit answer I found
You just saved me hours of headache. Thank You for sharing.
This is so helpful Tim, thank you.
I had been running the Korg Minilogue XD fine for months, then got a MOTU microlite interface, and an arturia beatstep... and next thing i knew, the Korg driver was no longer recognized. Their user-forums and help pages are utterly useless in helping explain what the problem is. They allude to this "10 devices" thing but don't explain exactly the process and the reasoning. I really appreciate someone like you explaining this for the (admittedly few) that may experience problems like this. Its not the sort of thing that gets a lot of hits but its an invaluable resource.
I had been banging my head against the wall for the last 2 days. I finally saw this vid and then deleted a bunch of old USB midi devices, uninstalled my MOTU microlite, reinstalled the korg, then installed the MOTU again, and voila, it all worked again
they should seriously just link to you in their Support page
Piece of advice re: "Registry Editing" - an easier thing to do when you've got some kind of complex driver conflicts is just use CCleaner, which scans the registry for broken links/bad entries and will clean them out for you. Its just a good tool to use periodically when you're uninstalling/reinstalling things and running into problems.
ABSOLUTELY GREAT - i have to say. Bought the NTS-1 and cant update, because of hundreds of midi drivers....with your help, i fixed it ;) THX a LOT