Windows 10: Strange MIDI-port problem (10-port-limitation-related)

I have a VOX AMP that has a USB connection uses a KORG USB midi driver.

The connection has to be made within the old 10-MIDI-port-limitation, otherwise the AMP is not seen by the KORG Tone Room software.


Now strange things (?) happen on my Windows 10 system.


The driver always gets installed to the 11th port (mid10 or higher), though the ports mid1-mid9 are still available and not taken by any other device.


How can that happen?

How can I handle the situation, f.e. manually switch the AMP to use mid1-mid9 for the connection?


Thx in advance for every hint.


Best, Adrian

:)

 

Does Win 10 Have the 10 MIDI Port limitation?


In older OS' there was a limitation of 10 MIDI ports. Does Win 10 have the same limitation?

I have a utility to list the ports but it does not work in Win 10. It only shows the Device Manager.

The utility is only a two line batch file.

set devmgr\_show\_nonpresent\_devices=1
start Devmgmt.msc

 

Does Win 10 Have the 10 MIDI Port limitation?


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.

If anyone has more information on this, please post and correct me if I'm wrong.

 

RTP midi and virtual midi ports in windows 10

Hi there!

I just watched Pete Brown discuss Windows 10 in audio over at Sonic State. Pete, you said Bluetooth midi is the next priority to be implemented in Windows 10, although you kind of acknowledged that it is more of a gadget for the masses, not a reliable low
latency way for professionals. I would urge you guys to consider RTP midi the highest priority, instead. What I always missed, when switching over from Apple OS, was the ability to create virtual midi ports (without restrictions of the number of ports) from
within the OS, that show up as midi ports in all kinds of audio programs. If those could be made low latency network ports to other Windows 10 PCs, remembering connections once setup at every start, MS could really gain the trust of so many composers and musicians
working with midi. It is a basic functionality for any DAW OS, IMHO. Please consider that! It shouldn't be to hard, as it already works decently with third party hardware. But having it as part of the OS is desirable.

Now, if you could even extend that to virtual audio ports, Windows 10 would have overtaken Mac OS X on those basic needs of DAW users.

I do realize, the tablet and smart phone crowd is the bigger one and cannot be ignored! But the professional crowd should be also taken seriously, if Windows 10 should become THE OS for audio, as you want it to.