MiniMax H3 Repair Segment Select / 重做段选择 (Advanced)

Long H3 generations fail in segments. Maybe shot 4 of 8 has a face wobble, or a chunk of dialogue landed wrong, and the rest of the timeline is fine. Re-rolling the whole chain to fix one segment is a waste of hours of sampling. The Selective Repair system in this pack is built for exactly that, and this node is the moment you point at a segment and say "this one." It selects one item out of a non-destructive repair plan and exposes the exact generation inputs for it - prompt, seed, length, mode - so the rest of your graph can re-generate just that segment.

The important word is select. This node doesn't generate anything, doesn't queue anything, and doesn't accept anything. It reads a H3_T8_REPAIR_PLAN (produced by MiniMaxH3SelectiveSegmentRepairT8Advanced), picks the entry at repair_index, and hands its compiled prompt and parameters back out. Acceptance is a separate, later, explicitly human step in the chain - this is purely "here's what a redo of this segment would look like."

Inputs and outputs

Just two inputs: repair_plan and repair_index (default 0, up to 100000 - index into the plan's segment list).

Outputs, all meant to be wired into your existing generation graph:

• compiled_prompt and negative_prompt - the text for the redo.
• length - the segment's frame count.
• seed - a repair seed (derived from the plan, deterministic per segment).
• repair_mode - how the plan wants this segment redone (e.g. auto).
• repair_json / report_json - the machine-readable detail and the human-readable report.

Installing and using it

In the T8mars MiniMax H3 Audio T8 pack:

cd ComfyUI/custom_nodes
git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8

or ComfyUI Manager → "MiniMax H3 Audio T8", restart. No pip deps. It's a pure planning/selector node - no models load, no VRAM cost.

The take

Think of the repair chain as a pipeline with distinct stages: SelectiveSegmentRepair builds the plan, this node selects from it, SelectiveRepairBind binds it to an accepted-manifest revision, SelectiveRepairStage verifies a candidate, SelectiveRepairAccept commits it, and SelectiveRepairCompose renders the final with the overlay. This node is the "which one" step - the one you bump repair_index on until the compiled prompt matches the segment you're actually mad at. If you only ever regenerate whole chains, you don't need any of this; if you've ever stared at one bad segment of a 200-frame timeline and thought "I am not re-rolling all of this," this is the doorway into a saner workflow.