Windows 10 and the MIDI device issue...

[miden]

A problem that we all know has existed in Windows forever, and even in Windows 10 is still there again, as we all know; the 10 device limit for MIDI peripherals!

Now the registry fix is still available, although these days I THINK you need to do it in more than the Windows NT key, however what I am asking here is: does anyone know if a clever programmer somewhere has managed to come up with a batch file that will automate the process?

I know the Korg removal utility is handy, but after the latest windows update it doesn't work as W10 seems to make ports 3-10 unavailable (they are greyed out with NO devices noted) and any user MIDI devices and drivers installed, jump straight to 11 and up, which we all know means they will not work!

Thanks

PS: I guess failing a batch file, at least an updated method of removing the entries via Registry would be helpful. I have this nagging feeling that you need to do it in more than one place these days.

[UltraJv]

"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."

https://www.tenforums.com/drivers-hardw ... ation.html

[Scotty]

I routinely have 20+ midi devices active at any one time here on both Windows 7 64 bit and Windows 10 Pro. This includes a mixture of midi interfaces, hardware synths, drum machines and controllers both connected through midi 5 pin din and USB midi. I haven't experienced an upper limit yet.

[chk071]

So, basically, this issue doesn't exist?

What's that info the OP states then? Hailing from former Windows versions?

[Scotty]

I have heard of the issue so I wouldn't say it doesn't exist. I haven't experienced it. I thought it may be a limitation of 32 bit OSs but I can't confirm this. I vaguely remember an XP limitation of 10 ports that was remedied with a service pack update but that was years ago. For the record I am using 3 multi port Midi Interfaces ( 8 Port Midex 8 , 3 Port Mid Ex 3, 8 Port Yamaha MX256, + Two pairs of RME Midi ports from my Raydats + several synths, controllers and groove boxes all connected and available in Cubase without patching. (A total of 25 external midi devices that are simultaneously connected and available through the midi interfaces or direct though USB. )

[Acid Mitch]

I don’t have the problem in Windows 10 64bit or Windows Xp sp3 32 bit.

[ThomasHelzle]

The only driver I know to have this issue is the one from Korg. I do not know what ancient API it's based on, but it's the most clumsy and stupid driver I've ever seen this side of 2000. I have a ton of USB midi devices attached and removed all the time and Korg is the only one giving trouble.
At first I couldn't even believe it when I went on an internet hunt to find out why their own driver didn't work with our Minilogue XD when the native Windows driver did work just fine - changing the order of devices in the registry? Really?. I would have left the native one installed but each and every Kork software would complain or refuse to work... which is absolutely silly. In this day and age, Midi on Windows is not a problem at all in my general experience.
I do not know what's wrong with Korg and why they even go to all that trouble to install their absurdly outdated driver and tools and whatnot and insist on it when native drivers would work just fine but you have to jump through hoops to use them.

So I'd recommend pestering Korg support to finally get into this century and update their drivers and get rid of their silly tools and stuff.

Cheers,

Tom

[Pictus]

Psychlist1972(Pete Brown) works for Microsoft...
https://www.gearslutz.com/board/music-c ... st14636585


https://twitter.com/Pete_Brown/status/1 ... 0085701641

[Louis Prima Nocte]

The only driver I know to have this issue is the one from Korg. I do not know what ancient API it's based on, but it's the most clumsy and stupid driver I've ever seen this side of 2000. I have a ton of USB midi devices attached and removed all the time and Korg is the only one giving trouble.
At first I couldn't even believe it when I went on an internet hunt to find out why their own driver didn't work with our Minilogue XD when the native Windows driver did work just fine - changing the order of devices in the registry? Really?.

lol omg last year i had this exact problem w/ the minilogue XD module.

it turned into a month-long troubleshooting/experimenting process. It wasn't helped by the fact that Korgs own discussion forums and website were a complex, unnavigable mess that kept moving threads complaining about the issue to some older, unrelated issue.

Glad *(sort of?) to hear i wasn't the only one. I was also convinced for months that Win 10 must suffer from native 'midi device limit' issues because of it.

[ThomasHelzle]

kORk - THE MOST DEMENTED MIDI DRIVER IN EXISTENCE - AND PROUD OF IT
If you can make lots of people miserable over something solved decades ago and totally pointless, why not go all the way?
Why not build a complex infrastructure of stupidity, several tools to manage idiocy in style?
And then create Tutorials on how to be a really really good idiot.

kORk has to be first, otherwise we just won't work for you, shithead.
Deal with it, or go f..ck yourself.

kORk, the inventor of AI - Artificial Idiocy (TM)
To supplement the abundance of NI - Natural Idiocy - as gathered in spades - you know it - at kORk Head-in-Quarters.

ARGHhhhhhhhhhhhh

Today as so often the kORk Midi Driver came up after system boot and wanted so install itself. Like a couple of days ago, as every couple of days, as basically all the time. And no it doesn't need any good reason for it, it just exists to be annoying...
I don't even have any kORk hardware attached for months now...