When a bridge publishes its own virtual MIDI port, that port belongs to the running process. Restart the bridge and the host may still display the old port name while receiving no new messages. If your MIDI port stops working after an app restart, bind the host to a bus that stays alive independently of the bridge.
- Create an IAC bus on macOS or a loopMIDI port on Windows.
- Select that existing destination in Universal Controller MIDI's Output menu.
- Select the same bus in your host, then restart the bridge to verify recovery.
Why can the port name remain while MIDI stops?
Some hosts remember a port by an internal endpoint identity as well as its visible name. When an app-created endpoint disappears and is recreated, its identity can change. The old name in a settings panel can make the connection look healthy even though the host is listening to the former endpoint. The bridge release notes describe the persistent destination option added for this problem.
Check the bridge's own MIDI monitor first. If it shows events and the host shows none, the break is between output and host input. If the bridge shows nothing, check the gamepad connection and mapping instead. The port troubleshooting guide walks through those checks.
How do you create a bus on macOS?
Open Audio MIDI Setup, show MIDI Studio, open IAC Driver and enable it. Create a bus with a name you can identify in both apps. In the bridge's Output menu, choose that existing bus. In your DAW, select the same IAC bus as the incoming MIDI port. Avoid leaving both the old bridge-created input and the IAC input enabled for the same mapping, or one press may arrive twice.
How do you create one on Windows?
Create a named virtual port in loopMIDI. Choose it as the bridge's output and your host's input. Keep loopMIDI running while you perform. The port is persistent across a bridge restart because a separate app owns it. If you hear the Windows built-in synthesizer but the DAW gets no MIDI, confirm the bridge is sending to the loopMIDI port rather than the synth fallback.
What should you test before a show?
Save the host project, then restart only the bridge. Press a button and sweep a stick. Watch the host's MIDI activity indicator and the actual mapped parameter. Reconnect the controller and repeat. A soundcheck that only confirms the device name exists does not prove a working route.
If changing the route is impractical during a set, the bridge also offers Output → Republish MIDI port as a recovery action. It can restore a published output, although a host may still need to refresh its input. The persistent bus is the cleaner setup for a planned performance. See how virtual ports work for the underlying routing model and current download availability to try the app when the free option returns.