Two Controllers, Separate MIDI Ports: Routing Guide
Blog Collaboration 5 min read

Two Controllers, Separate MIDI Ports: Routing Guide

Route two game controllers to separate MIDI inputs for a DAW and VJ app. Use P1/P2 labels, name each role and test for cross-routing.

By Aidxn Design

When two controllers need separate MIDI ports, the hardest question is often which pad the DAW is actually listening to. Universal Controller MIDI v3.5.0 labels connected pads P1 and P2, lets you name their roles and prints each pad's MIDI port beneath it. Use those labels to make the route visible before you start mapping.

Routing check
  • Connect both pads and name them by job, such as Drums and Visuals.
  • Select the port shown under each pad in the intended host.
  • Move only one pad and verify only its target responds; repeat with the other.

How do you identify each controller?

Connect the first pad and move an input while watching the live diagram. Connect the second and repeat. The app badges them P1 and P2. Right-click or double-click each header to name it for its actual job: Drums, Resolume or the player's name. The name helps humans; the MIDI port printed below the header is what the receiving app binds to.

A controller name alone is a poor routing test because two identical pads may show the same hardware name. A port label gives you the destination to select in the host. Write that pairing down in your session notes if you need to rebuild a live rig quickly.

How do you keep a DAW and visuals app apart?

In the DAW, enable the port shown under the music controller. In the visuals app, enable the port shown under the visuals controller. Start with only one active mapping in each host and press a button on one pad. If both apps react, inspect their input selections and any aggregate input such as “All MIDI Inputs.” A host listening to every port can defeat the separation you set up in the bridge.

Then swap pads and repeat the test. Check both a button and an axis: buttons reveal simple cross-routing, while a stick exposes whether a continuous mapping is attached to the wrong source. The two-player session guide covers two performers sharing one DAW; the Resolume guide covers the visual side.

What happens after a restart?

Restart the bridge while the hosts remain open and repeat the one-pad-at-a-time test. Some hosts remember an endpoint that no longer exists even when the same visible name returns. If the route goes silent after a restart, bind both apps to independently owned IAC or loopMIDI buses and select those as bridge outputs. The persistent MIDI bus guide shows the full recovery test.

What is the shortest soundcheck?

Say the intended route out loud: “P1 Drums to DAW input A; P2 Visuals to VJ input B.” Press one control on P1 and watch both hosts, then press one on P2 and watch again. Save both host projects after the test. The release notes document the P1/P2 and naming changes, and downloads lists current builds.

Keep reading

More setup walkthroughs