A few months ago we released our very own Virtual MIDI Cable Driver for Microsoft Windows.

In the Audio MIDI Setup app on your Mac, choose Window Show MIDI Studio. In the MIDI Studio window, click the Choose MIDI Configuration pop-up menu (it may show Default), then choose New Configuration. Enter a name for the new configuration, then click OK. To add a new external MIDI device, click the Add button in the MIDI Studio toolbar. VirtualMIDISynth is a software MIDI synthesizer implemented as a Windows multimedia user driver, accessible as a standard MIDI Out device. It works on Windows XP (SP3) / Vista (SP1) / 7 (SP1) / 8 (both x86 and x64), and is based on the great BASS library from un4seen. MUSICLAB VIRTUAL MIDI DRIVERS FOR MAC If you have a habit of creating a system restore point before installing a new program, you can roll back to this system restore point if this new piece of program is not up to your expectation or cannot be uninstalled from your computer properly. RealEight 8-string guitar virtual instrument. In this example, select “IAC Driver MH-out harmonize” as MIDI output port in the MIDI Harmonizer. 3: select the virtual port as input port in the receiving application In your receiving application, select the virtual port as MIDI input port. A Free Virtual MIDI Driver LoopBe1 is an internal MIDI device for transferring MIDI data between computer programs. Basically LoopBe1 is an 'invisible cable' to connect a MIDI outport of an application to any other application´s MIDI inport. All MIDI data sent to the program´s output is channeled to the receiving applications in realtime.

Some users quickly reported that it was not recognized on the latest versions of Windows 10 (build 1607), because Microsoft now requires a different certification level than the one we had. We’re now proud to announce that we did what was required from Microsoft to solve the problem, and that is now working very well on those systems too 🙂

So if you had downloaded the previous version and encountered this kind of error:

Be sure to checkout the latest release. Uninstall the previous version, and install this one instead.

But what does Springbeats Virtual MIDI Cable do exactly?

Glad you asked. It’s a Windows driver which installs 8 new MIDI devices on your system. Each of this device can be used to carry MIDI data from one application to the other. Just like a cable would do if you were dealing with hardware instead of software.

A typical example would be to route MIDI notes from your MIDI controller, that were first transformed by an application, to your DAW. You’d then be able to record the transformed notes. This is how AutoTheory works for instance. It takes the notes from your USB MIDI keyboard, changes them, and lets you get these changes in another app, via our Virtual MIDI Cable.

The good thing is : it’s totally free for personal uses! More than that, it is also opensource. The only restriction being you can’t embed it with your own app if you’re a developer, without our agreement.

Checkout the product page to read more and download.

Virtual MIDI driver for Windows 7 up to Windows 10, 32 and 64 bit with the ability to dynamically create and destroy freely nameable MIDI-ports.

The necessity for virtualMIDI came along when I implemented my rtpMIDI-driver. Later I also used this driver when I created loopMIDI for people who only need simple loopback MIDI-ports.

I had some pretty specific requirements:

• Compatibility from Windows XP to Windows 10
• Both 32bit and 64bit operation
• On-the-fly creation (and destruction) of freely nameable virtual MIDI-ports
• Only one side of the ports was supposed to be visible to the public
• The other side only visible via a private interface
• Multi-client-capability

Since I had been hanging around on the wdmaudiodev mailinglist for quite some time due to my interest in kernel-streaming, I had already read quite a bit on the topic over there.

All of the people there suggested to use the DMusUart and the MPU401 sample as a starting-point. So that’s what I did and creating the actual driver had been not too hard after getting enough insights at the WDK-documentation.

Virtual Midi Driver Mac

Nevertheless all the stuff people had done prior to my attempts would not quite achieve what my requirement were.

All of those other virtual MIDI miniport driver implementations actually developed simple static “loopback” MIDI-ports. Loopback meaning that both ends of this port would be public. Static meaning that the number of ports and their names would be fixed at install-time of the driver (via the inf-file of the driver).

This was not satisfactory, so I looked some more and I found references to dynamic creation of sub-devices. But this was a hard nut to crack. Finally I had been able to locate a guy who was doing something similar for a virtual soundcard-driver for digital-audio-broadcast.

His insights have been invaluable. It still took quite some time to get everything going smoothly, but I finally succeeded in creating this driver.

One problem remained: Since Microsoft introduced Vista, all drivers for 64bit need to be code-signed. Though the idea itself is pretty nifty – to know the specific company that the code running in the kernel comes from – it had a severe drawback:

Only companies incorporated could apply for such a code-signing-certificate. Many people in the driver-development-community urged Microsoft to rectify this. And finally in May of 2010 it has been done. Since that time it is also possible for individuals to get their own code-signing certificate to be able to run their drivers on the 64bit versions of Vista and Windows 7.

Virtual Midi Controller Mac

The driver is currently part of the rtpMIDI-driver network-MIDI driver and the loopMIDI virtual loopback MIDI cable. But it can be used for other tasks as well.

Virtual Midi Driver Download

If you have a music-application that needs to create its own freely named MIDI-devices on-the-fly – virtualMIDI is exactly the right tool. I have prepared a small & simple to use SDK with bindings for C/C++, Delphi, Java and C#.