| midi_path | STRING | | A .mid file: a full path, or just the name if it sits in ComfyUI's input folder.
What it needs to contain is a melody. Everything else — tempo, time signature, key, and section labels from MIDI markers — is read if present and reported if missing. |
| vocal_track | STRING | | Which track becomes the sung line. A track name, or its number counting from 0. Leave empty and the node guesses: a name containing vocal / lead / melody wins, otherwise the first track with notes.
The report lists every track with its note count and pitch range, so one run tells you what to type here. |
| ins_track | STRING | | Which track becomes the instrumental line. Same rules. Leave empty for the first track the vocal did not take; leave it pointing at nothing and the Ins voice is written as rests, which is perfectly valid. |
| style_prefix | STRING | | What the MIDI cannot know, put here: language, genre, vocal character, mood. The node appends what it CAN know — the tempo and the instruments General MIDI names — and hands back one style string.
YuE2 asks for 'Language + Genre + Vocal Character + Tempo + Instruments', and a MIDI answers the last two exactly. It has nothing to say about the first three, and guessing them from note data would be making things up.
Leave it empty to get the tempo and the band on their own, and join them to your own text however you like. |
| grid | COMBO | | The note grid everything is quantised onto — ABC's L: value.
auto picks the coarsest grid the music actually fits, which keeps the plan readable: a 1/32 grid can write any rhythm and produces a line nobody can check. Set it by hand when the guess reads wrong, and read the report either way — it says how far the notes had to move to land on it.
A MIDI quantised in a DAW converts exactly. A live take does not, and the report says so rather than pretending. |
| verbose | BOOLEAN | true | Print the report to the console. The same text is always on the 'report' output. |
