Minilog USB MIDI on Windows 10 - latest Korg USB MIDI Driver

Vondragonnoggin · Post by **Vondragonnoggin** » Thu Jan 28, 2016 7:41 am

realtrance wrote:Do you have more than 16 MIDI devices listed by the Korg uninstall utility?

If so, that's your problem -- Windows (XP to 10, it's never improved!) chokes on more than 16 devices present in the registry (worst software idea ever invented, that registry thing), and unless you remove enough to allow two more to be added (i.e. you should have no more than 14, either existing or previous, entries)... the Minilogue doesn't show up.

You may have entries in the registry from previous install attempts, too, that are blocking recognition of the Minilogue. Clear out as much as you can, safely, given the instructions above.

If you've done that and it still isn't "taking," I'd take the advice of that former MCSE up-thread, and buy a Mac! <G>

More seriously, I'm out of ideas I can help you with if that's the case, I'm sorry.

... the only other thing I can think of, I had this problem with an Ultranova and the included USB Audio/MIDI drivers a few years back... see if you can find a different USB port to use. Sounds like you're on an Acer laptop? It's possible there's some sort of USB mystery, power, or conflict, or address being shared with another device, or I/O port... the mysteries of how W10 handles USB functionality allocation is a bit beyond me, unfortunately. I solved my Ultranova problem by using a different USB port, why that worked (no USB hub, power was plenty, I/O ports in device manager/registry were unique, etc. etc.) was never something I pinned down, but it did. Sometimes if you have a device that's being identified as USB 1.1 rather than USB 2.0 or 3.0 (which is the case with the Korg driver for the Minilogue), that can lead to issues, which was part of the problem for the Ultranova (on my system, at least, at the time).

I have no USB-midi devices in the list because I have nothing connected to it. I tried all three USB ports. Install of win 10 was over a win 7 OS I had previously. This is the first USB-midi device I have tried connecting. No worries on the MCSE bit, he is probably right. I use ipad 90% of the time for stuff anyway. They should just get with the times and come out with a CCK-USB-Midi app for it. I am a Sr. Network Admin and been in IT 12 years and multitracking with computer 14 years before closing the PC last year and going back to all hardware. Bored with PC multitracking and prefer the more tedious hardware methods with more limitations actually.

I'll look in the registry. I previously had a ton of USB-midi devices connected to it using Ableton. That was before upgrade to 10 though. Korg NanoKontrol, padKontrol, launchpad, M-Audio Venom, Minibrute USB-Midi utility, focusrite Scarlett interface, previous to focusrite, m-audio audiophile, waldorf blofeld utility, etc.

A ton of stuff all connected and have great familiarity with Jorg utility for uninstalling USB-midi devices (Korg or otherwise).

Like I said, all slots empty after removing the multiple minilogue entries that showed up after reinstallation of driver attempts. Can startt with seeing only one entry - minilogue (connected) in one slot and it still dorsn't recognize it.

I'll report back after going through registry looking for entries.

Vondragonnoggin · Post by **Vondragonnoggin** » Thu Jan 28, 2016 8:30 am

Just went through the system and uninstalled any programs for USB drivers on equipment I don't everconnect anymore, then opened Korg USB-midi uninstall utility with nothing connected, saw that all 9 spots were greyed out because nothing to uninstall, so hit cancel and opened it agaon with minilogue powered on in version up mode and saw that it now listed one device available to uninstall - minilogue (connected), sp canceled out of the utility, opened the updater utility and again get no device connected even though when I go to config, it shows minilogue in and minilogue out, and if automatically detect is unchecked, I can toggle between minilogue midi in and minilogue sound and minilogue midi out and minilogue kbd/knob.

Giving up on this updater. Will try my netbook on win 10 and if that doesn't work, then I will try my son's win 7 laptop which is a fresh win 7 install as of one month ago.

uglier · Post by **uglier** » Thu Jan 28, 2016 8:47 am

Also had a Win 7 to 10 conversion with this sort of problem. A Dell desktop of about 3 or 4 years. Very frustrating.

I deleted a bunch of registry stuff, nothing.

Driver re-installs, nothing.

Opened up "Device Manager" and picked off (uninstalled) a couple of things from "Software Devices" section, specifically a couple of non-descript entries generically labelled "MIDI" , and a duplication of my Launchkey entries. I didn't reinstall anything and started up Ableton Live and it showed up in the midi preferences finally. It seems to be working from what I can tell now.

I've had many things connected or hooked up before..

For me it showed up in the "Sound, video and game controllers" section of device manager in Windows, as "minilogue".

Vondragonnoggin · Post by **Vondragonnoggin** » Sat Jan 30, 2016 6:23 pm

Acer netbook on win10 worked without a hitch. Still not sure what is holding it up on the laptop, but could be the launchkey drivers as mentioned previously. Novation stuff was kind of bloated.

Now patched to 1.04 at least. I'll just keep using netbook for patching.

realtrance · Post by **realtrance** » Sat Jan 30, 2016 8:14 pm

Yeah, since the connect is only for MIDI stuff, any old computer that has USB ports will do.

Pain that it's a problem, though. It can be either some weird hardware I/O issue, or USB driver device allocation in software, or a combination of both.

Perhaps the typical MS advice when anything goes wrong to FDISK and start over is really the best.

Vondragonnoggin · Post by **Vondragonnoggin** » Sat Jan 30, 2016 9:11 pm

realtrance wrote:Yeah, since the connect is only for MIDI stuff, any old computer that has USB ports will do.

Pain that it's a problem, though. It can be either some weird hardware I/O issue, or USB driver device allocation in software, or a combination of both.

Perhaps the typical MS advice when anything goes wrong to FDISK and start over is really the best.

Haha. A little drastic of a measure for just patching a synth with a non-critical patch. Think I'll leave fdisk out of the equation for now.

korguser2016 · Post by **korguser2016** » Fri Apr 15, 2016 6:32 pm

realtrance wrote:It's insanity-making, isn't it?

What I finally found out, with help from someone knowledgeable, is two things:

1. First, update to the latest version of the Korg USB-MIDI driver utilities, on the Minilogue support page now.
2. Do the following:

a) read the instructions that come with the utility carefully
b) next, unintuitively: in the Korg Utilities, select "Uninstall Korg USB-MIDI Device" (no, you're not uninstalling the MIDI-USB driver you just installed, don't worry!)
c) click the Option button
d) untick the check mark that by default only lets you uninstall Korg MIDI devices (this is to prevent you from uninstalling other MIDI devices you may have installed on your system)
e) Now: be SURE you know, in the list of MIDI devices you can remove, which ones you actually use, and which ones are "residue" in your Windows registry from previous installs/uninstalls.
f) The critical step: REMOVE all the MIDI devices, including any associated with the Minilogue, from the list. What this does is delete them from the Windows registry.
g) Next: run the "Install Korg USB-MIDI Device" in the Korg MIDI-USB utilities, with your Minilogue connected
h) NOW you can properly add the Minilogue as a USB-MIDI device.

The problem, as I understand it, is that once Windows fills up with 16 entries for MIDI devices in the registry, it gets sick and can't add any more, and so enough have to be removed to add any new ones.

This is the way to do it.

Hope that helps! Some day, it will all be perfect.

This solved my issue. It also allowed me to cleanup a whole load of old midi devices I no longer use. I am now updated to the 1.11 version and can see the midi device in DAW/etc. Thanks!

jeffa1169 · Post by **jeffa1169** » Wed May 11, 2016 10:37 pm

When I tried to update my Minilogue this week, I kept getting the error "Found No Midi Port". I followed Korg's instructions exactly and even tried the posted fix for cleaning out obsolete midi devices. I tried from 3 different computers, each one running Windows 7. Nothing worked. Then I tried with another PC, this time running Windows 10 and it worked immediately.