How to Route Audio Mixers for Virtual MIDI

Virtual MIDI routing is one of the most powerful and underutilized tools in a modern drummer's workflow. Whether you are triggering software instruments from an electronic kit, sending drum patterns from a DAW to a hardware module, or layering samples in real time, understanding how to route MIDI without physical cables opens up possibilities that were impossible just a decade ago.

This guide covers the fundamentals of virtual MIDI routing on Windows and macOS, common pitfalls, and practical configurations for popular DAWs including Ableton Live, Logic Pro, FL Studio, and Reaper.

What Is Virtual MIDI Routing?

Traditional MIDI requires a physical 5-pin DIN cable (or USB-MIDI) connecting an output port to an input port. Virtual MIDI eliminates the cable by creating software-only endpoints that applications can read from and write to as if they were hardware ports.

On macOS, this is built into the operating system via the IAC (Inter-Application Communication) Driver. On Windows, you typically need a third-party utility such as loopMIDI by Tobias Erichsen or MIDI-OX combined with a virtual cable driver.

Setting Up Virtual MIDI on macOS

Apple's IAC Driver has been part of macOS since the Classic era, yet many users never touch it. Here is how to enable it:

1. Open Audio MIDI Setup (found in Applications > Utilities).
2. From the Window menu, select Show MIDI Studio.
3. Double-click the IAC Driver icon.
4. Check Device is online.
5. Click the + button under Ports to add a new bus. You can name it anything descriptive, such as "DrumDash Bus" or "E-Kit to Ableton."

Once active, the IAC bus appears as both a MIDI input and output in every audio application on your Mac. You can now send MIDI from DrumDash (or any other app) into Ableton Live by selecting the IAC bus as the output in one app and the input in another.

Setting Up Virtual MIDI on Windows

Windows does not include a native virtual MIDI driver, so you will need to install one. The most reliable and widely used option is loopMIDI.

1. Download loopMIDI from Tobias Erichsen's website.
2. Install and launch the application.
3. At the bottom of the window, enter a name for your virtual port (e.g., "Virtual Drum MIDI") and click the + button.
4. The port now appears in every MIDI-capable application on your system.

Unlike macOS's IAC Driver, loopMIDI ports are unidirectional. If you need bidirectional communication, create two ports and route them accordingly. For most drum workflows—sending pad hits from an e-kit to a sampler—a single port is sufficient.

Configuring Your DAW

Every DAW handles MIDI input slightly differently. Below are the specific steps for the most common platforms.

Ableton Live

1. Open Preferences > Link/Tempo/MIDI.
2. Under MIDI Ports, find your virtual port in the Input list.
3. Toggle Track and Remote to On for that port.
4. Create a MIDI track, set its MIDI From dropdown to your virtual port, and arm the track for recording.
5. Load a drum rack or instrument on the track. Incoming MIDI notes will now trigger the instrument.

Logic Pro

1. Open Logic Pro > Preferences > MIDI.
2. Ensure your IAC bus is visible under Input Devices.
3. Create a Software Instrument track.
4. In the track inspector, set the MIDI input to your IAC bus.
5. Load Drum Kit Designer, Ultrabeat, or a third-party AU instrument.

FL Studio

1. Open Options > MIDI Settings.
2. Under Input, find your virtual port and enable it.
3. Set the Controller Type to Generic Controller.
4. In the Channel Rack, add a VST instrument such as FPC or a third-party drum sampler.
5. Right-click the instrument, choose Piano roll > Receive notes from, and select your virtual port.

Reaper

1. Open Options > Preferences > Audio > MIDI Devices.
2. Right-click your virtual port under MIDI Inputs and choose Enable input.
3. Create a new track and click the IO button.
4. Under MIDI Hardware Input, select your virtual port.
5. Insert a VSTi on the track. Reaper's routing is extremely flexible; you can also use ReaRoute for audio if needed.

Practical Use Case: Layering Samples in Real Time

One of the most common reasons drummers set up virtual MIDI is to augment a hardware drum module with software samples. For example, you might want the punch of a Roland TD-50's snare trigger combined with the room ambience of a Kontakt drum library.

Here is a typical signal chain:

• Electronic drum kit sends MIDI over USB to the computer.
• DrumDash or a MIDI utility receives the MIDI and forwards it to a virtual port.
• DAW listens to the virtual port and triggers a software instrument.
• Audio interface sends the mixed output (hardware module + software samples) to headphones or monitors.

The key advantage is zero additional latency compared to routing audio out of the computer and back in through a hardware loopback. The MIDI data itself is tiny—just a few bytes per note—so it travels through the virtual pipe almost instantaneously.

Troubleshooting Common Issues

Even with the right tools, virtual MIDI can be finicky. Here are the problems we see most often and how to fix them.

"No MIDI Input Detected"

This usually means the sending application is not actually writing to the virtual port, or the receiving application is not listening on the correct channel. Double-check that:

• The virtual port is online (macOS: IAC Driver is enabled; Windows: loopMIDI is running).
• The output device in the sender matches the input device in the receiver.
• No other application has exclusive control of the MIDI port (some drivers allow only one client).

Double Triggers or Note Doubling

If you hear two hits for every pad strike, you likely have both the hardware module and the software instrument receiving the same MIDI data simultaneously. Mute the hardware module's internal sounds or set its Local Control to Off so it only sends MIDI without generating audio.

Dropped Notes Under Heavy Load

If notes disappear during fast rolls or dense passages, increase your audio buffer size temporarily. While this adds a small amount of latency, it gives the CPU more headroom to process MIDI and audio together. A buffer of 256 or 512 samples is usually a safe compromise.

Conclusion

Virtual MIDI routing is an essential skill for any drummer working with hybrid setups. Once configured, it becomes invisible—you simply play your kit, and the sounds you want come out of your monitors. Whether you are practicing with DrumDash, recording in a DAW, or performing live with layered samples, the ability to move MIDI data freely between applications is what makes modern electronic drumming possible.

If you are using DrumDash's WebGL version, note that browser-based MIDI access is handled through the Web MIDI API. Chrome and Edge support it natively; Safari support is improving but still limited. For the lowest latency, we recommend the native Android app or a desktop browser with a dedicated audio workstation setup.