mio10 and Microsoft Midi drivers

edited July 7 in MIDI
I've had a mio10 for a couple of months... it is great for simple sequencing and midi controller use, etc. It falls short when handling large volumes of sysex data or when trying to use a hardware synthesizer with a software editor and DAW at the same time.

Large volume sysex dumps:
The Microsoft midi drivers choke on large volumes of sysex data. I spent many hours trying to get a Wavestation SR performance bank (which consists of a bank of performances, bank of patches, bank of wave sequences) to load, but without success. Several different programs were used, including Midi-Ox with many different buffer settings, but it was not successful. Since then I purchased a used Edirol UM-880 midi interface and the patch banks loaded into the Wavestation first try, and have loaded successfully every try since. The UM-880 uses custom midi drivers that are written to handle large sysex dumps, and anything else you might need to do.

Multi-client midi:
Another significant shortcoming of the Microsoft midi drivers is the inability for two applications to access a midi port at the same time. This is especially frustrating when you want to use your DAW and a software patch editor at the same time. You can overcome this by using the free loopMIDI virtual cable utility as follows:

Synth midi out ---> Synth editor software  ---> loopMIDI virtual cable ---> DAW ---> Synth midi in

I name the loopMidi virtual cable the same as the synth with the word "Virtual" after, so for the Roland JD-990 it would be "JD-990 Virtual" and is setup like this:

JD-990 synth editor:  midi in - mio10 port, midi out - JD-990 Virtual
Cubase DAW: midi in - JD-990 Virtual (or all midi), midi out - mio10 midi out port

In Cubase you need a midi track that takes the JD-990 Virtual input from the editor and routes it to the mio10 midi out port that the synth is connected to. This track must be active (selected) for it to send data from the software editor to the synth. In Cubase, Device Manager must have the mio10 midi in port set as inactive so that it does not lock the port. In the synth editor it must use the virtual cable for midi out so that it does not lock the mio10 midi out port.

One nice thing about this setup is that it allows you to send midi clock to the synth since Cubase has access to the mio10 midi out port.

Hopefully, this will help anyone trying to get around the multi-client issue. Unfortunately, there is no getting around the large bulk sysex issue. You need to buy an interface that has better drivers than what the Microsoft midi drivers provide.



  • We are hoping to have new Windows drivers very soon that should solve most of these problems. Watch this space.
  • I hope these new MIDI drivers will also support the iConnectMIDI 4+ ? This device is also crippled by having single-client drivers.
  • That's the plan.
  • Sorry to hijack the thread, but a question for Rodney about the new drivers mentioned earlier...  Are these going to be custom device drivers for the mio series that will replace the Microsoft "class-compliant" generic ones?  If so, will this allow for the proper operation of multiple mio10 units to be installed on the same machine so that all the ports show up "uniquely named" in Windows for applications that aren't very strict about their port enumeration?  That would save my life, as I have two mio10 units but I am unable to take advantage of the second one in most applications...

    Any further info would be greatly appreciated...and I'd be more than happy to help beta if you need another tester :)

  • That's the plan. We might have a first beta release sometime in the next week if all goes well.
Sign In or Register to comment.