MIDI LOADER (JOV_MIDI)

Let me save you some time: as of the current release, MIDI LOADER doesn't do what its name promises. It's supposed to load a .mid file and convert its events into the pack's JMIDIMSG list - the README says exactly that ("Load MIDI files and convert their events into a ComfyUI parameter list"). But check the shipped source and you'll find the class is declared with its two outputs and no actual run logic wired up. Its info_schema shows zero inputs. There's no file picker, no path field, nothing to point at a file. A helper function that opens a MidiFile and logs the messages exists in the module, but it isn't connected to the node.

This is the least finished node in Jovi_MIDI, and it looks like scaffolding carried over when the MIDI section was split out of the author's bigger Jovimetrix pack at 1.0.0. Don't build a workflow that depends on it, and don't spend an evening wondering why it errors - you're not missing a setting.

When it does ship, the intent is clear from the design: the same MIDI (JMIDIMSG) and TRIGGER outputs as the filter nodes, so a file could drive the exact same gate-and-decode chain as a live controller. You'd load a performance, let its note events become the JMIDIMSG bus, and run them through MIDI FILTER / MIDI MESSAGE just like hardware input. That's a genuinely useful idea - MIDI files are just event lists, and event lists are exactly what this pack's message type wants to carry.

If you need that capability today, the honest answer is: use something else. The mido library (which this pack depends on anyway) can read .mid files from a small script, and other packs cover file-driven sequencing. Jovi_MIDI's loader just isn't there yet.

Install is the same as the rest of the pack either way - ComfyUI Manager, search Jovi_MIDI, or:

cd ComfyUI/custom_nodes
git clone https://github.com/Amorano/Jovi_MIDI.git
pip install -r requirements.txt

If you grab it and the loader is still a dead end, that's not a broken install - it's just the most honest answer I can give you about this node: it exists, it has a clear plan, and the plan isn't implemented yet. Check the pack's GitHub issues for updates before you count on it.