Where Does loopMIDI Store Port Config?
loopMIDI keeps virtual MIDI port definitions in its config and recreates them at startup. Ports are live routes, not files; back up the config.
Last updated
loopMIDI creates virtual MIDI cables between Windows music apps. Port definitions persist in its configuration and rebuild automatically at startup. The ports themselves exist only while running; no audio or MIDI data ever rests in them.
Exact config paths may vary by version, so manage ports inside the loopMIDI window rather than the filesystem. Latency stays low because nothing touches disk. Keep port counts modest; dozens of idle ports clutter every device menu in every app. Session persistence survives reboots, but running projects reference names live.
Where loopMIDI stores this, by platform
%appdata%\loopMIDI\
Port definitions persist in config and rebuild at startup. Exact paths may vary by version. Name ports by purpose and enable auto-start before the DAW.
Frequently asked questions
How do I keep MIDI ports after reboot?
Create persistent ports in loopMIDI so they rebuild on every boot. Name them by purpose like DAW Keys rather than Port 1. Apps connect to the names, so renaming mid-project breaks routings silently.
My DAW sees no loopMIDI ports. Why?
Enable auto-start so loopMIDI builds ports before the DAW launches. A DAW that starts first sees no ports and caches their absence. Order matters: loopMIDI, then instruments, then the project.
Notice an outdated path? Let us know.