Nodes/Plenio Music Production System/Apply Sung Check (retired)
ComfyUI Node

Apply Sung Check (retired)

Four Rules Decide Whether the Fix Survives

By jplenio·Created 2 months ago·Updated a day ago· 121
Apply Sung Check (retired)
    • record
    • report
    ◄record—►
    ◄answer—►
    ◄language►

    Asking a language model "which word was misheard here?" gets you an answer. It doesn't get you a trustworthy answer - writers hallucinate, over-correct, and cheerfully rewrite a lyric that was sung perfectly. Apply Sung Check is the gate: it takes the writer's proposal and keeps only the corrections that survive four hard rules. Everything else is thrown out, with a reason.

    This is the last node in Plenio's lyrics-checking chain, and the only one that actually changes anything on disk.

    The four rules

    A proposed fix is kept only if all four hold:

    1. It replaces a whole bracket from the prompt - a word the lyrics don't have there, or a run of words (a phrase can be heard as other words: a detour as ready to).
    2. The writer says it's at least 80% sure. Below that, the word stays as heard.
    3. The replacement has the same number of syllables as what was heard. A Chinese or Japanese character counts as one.
    4. It doesn't create a doubled word the line didn't have.

    That syllable rule is the clever bit, and it's the one that saves you. It's easy to "correct" an ad-lib into a synonym that means nothing rhythmically; matching syllable counts keeps the correction singable against the same melody. Ad-libs, words the model invented, and repetitions stay as heard, because they weren't marked in the first place.

    The honest caveat: quality tracks the writer model. On a test song with two planted mishearings, Gemma 4 12B and Qwen3.5 9B both got rowed → road and ready to → A detour. Qwen3.5 9B also turned a sung I into If - one over-eager edit out of three. The gate caught nothing wrong there; the writer simply guessed confidently and wrongly.

    Inputs and outputs

    record is required and takes Export Release's record output. answer is the writer's reply, optional and lazy - the node only asks for it when there is genuinely something to check, so the language model doesn't spin up for a song with nothing to fix. language is optional and empty by default: the brief's language, else guessed from the lyrics, and it's what the syllable comparison uses.

    Outputs are record - the same path, corrected in place - and report, which lists what was corrected and why the rest wasn't. The node is an output node, so it runs as a terminal step and prints a summary card with the changes.

    What actually gets written: each accepted fix goes into the release record at timing[].sung.corrected with line, heard, word and confidence; the sung lines and text carry the corrections; (sung).srt is rewritten so your lyric video matches what's really sung; and the figure for how closely the take follows its lyrics is recalculated. The Plenio Player then shows the corrected lines under As sung and lists the corrections on the song's page.

    One subtlety worth knowing: a record is checked once. Run it a second time and it asks no writer - the earlier corrections stand. If you want to try a different writer model, keep a copy of the .plenio.json first, because the edit is in place and there's no undo in the record itself.

    Installing it

    It's part of the pack:

    cd ComfyUI/custom_nodes
    git clone https://github.com/jplenio/Plenio-Music-Production-System
    

    Or search Plenio Music Production System in Manager and restart. No Python packages are installed by the pack - its dependency list is intentionally empty. In the templates the whole Check Sung Words block sits in the FINISH group after Export Release and uses the template's writer model; open the block to swap in Local LLM with a GGUF from models/LLM if you'd rather not use Gemma 4 natively.

    Where people get burned

    • "It changed nothing." Usually correct behaviour: check the report. A record with no sung lyrics - instrumental, subtitles off - or a take whose words the lyrics already have produces nothing to check and skips before any writer loads.
    • Expecting it to fix a take that sang different lyrics entirely. The prompt caps marked words at 120 for a reason. If the model improvised a chorus, this isn't the tool; re-render.
    • Wanting it off. Select the block and hit Ctrl+B. The lyrics as sung then stay exactly as the ASR heard them, mishearings and all. Sometimes that's the more faithful document, and it's a legitimate choice.
    • Forgetting the downstream effects. Because (sung).srt and the lyrics-adherence count both get rewritten, this node changes what your subtitles and your player show. Re-export or re-check those if you'd already built something on top.
    CategoryPlenio/Lyrics

    Inputs (3)

    NameTypeDefaultDescription
    recordSTRINGThe release record Export Release wrote (its 'record' output).
    answeroptSTRINGNever asked.
    languageoptSTRINGNot used.

    Outputs (2)

    NameTypeDescription
    recordSTRINGThe release record, unchanged.
    reportPLENIO_REPORTThat nothing was checked.