Windows
miditool runs on Windows over WinMM. The one platform gap is virtual ports: Windows has no native way for an application to create a MIDI port that other applications can open, so the default output virtual="miditool Out" cannot work there. The standard fix is loopMIDI, a small free utility that creates loopback MIDI ports.
- Install loopMIDI and create a port. The default name works; this page assumes a port named
loopMIDI Port. - Point miditool’s output at it with
device=instead ofvirtual=:
input "MPK" // substring of your keyboard's port nameoutput device="loopMIDI" // substring of the loopMIDI port's name
shuffle-lock seed=42- In your DAW, select the loopMIDI port as the MIDI input.
miditool doctor checks for this setup and warns when no loopMIDI port exists:
warn no loopMIDI port; install loopMIDI and create one, then use `output device="loopMIDI"`hide=trueon theinputnode is a CoreMIDI feature; on Windows it is ignored with a note. Use a DAW with per-track MIDI input selection instead: see Other DAWs.miditool benchneeds virtual ports on both ends and cannot run on Windows.- Everything else, including scenes, hot reload, and the web remote, works the same as on other platforms.