Nodes/MiniMax H3 Audio T8/MiniMax H3 Accepted Context / 读取已接受上下文 (EXP/T8)
ComfyUI Node

MiniMax H3 Accepted Context / 读取已接受上下文 (EXP/T8)

Load the accepted previous segment and the exact parent identity your next render depends on

By T8mars·Created 20 days ago·Updated a day ago· 807
MiniMax H3 Accepted Context / 读取已接受上下文 (EXP/T8)
    • context
    • has_context
    • accepted_candidate_id
    • manifest_revision
    • report_json
    chain_idmy_h3_long_video
    segment_index0

    Long video in this pack isn't a magic "make it longer" button - it's a chain where every new segment is conditioned on what you've already accepted. That conditioning doesn't come from thin air: this node loads the accepted segment N-1 from the manifest and hands you two things at once - the context your next conditioning node needs, and the exact accepted_candidate_id that proves your next render is built on the current accepted history rather than a stale one.

    It's in T8/MiniMax H3/Long Video/Experimental, and it's the small node in the family that makes the big nodes behave. It's where the "no stale continuation" guarantee gets its teeth.

    How it works

    You give it chain_id (default my_h3_long_video) and segment_index - the segment you're about to render. It reads the accepted manifest and loads only segment N-1 (the one before the one you're building), not the whole history. Loading just the immediate predecessor is a memory and simplicity choice: each segment carries its own bounded AV tail, so the previous segment is all the context the next one legally needs.

    The output you'll under-value until you've been burned: accepted_candidate_id. This is the parent identity that Candidate Save must record. If you type a parent id from memory and it doesn't match what's in the manifest, the Review & Accept gate will reject your candidate as a stale continuation. Pulling it from this node's output is the fix - it's the exact value the manifest is holding right now.

    The inputs that matter

    • chain_id - must match the chain you've been building in. A typo here silently points at an empty manifest.
    • segment_index - the segment you're rendering next. The node loads index-1.

    Outputs

    context (an H3_T8_CONTEXT for Long Video Conditioning), has_context (BOOLEAN - false means no accepted predecessor, so you're effectively at segment 0), accepted_candidate_id (the parent identity to feed Candidate Save), manifest_revision (which revision of the manifest you're reading), and report_json.

    Installing it

    Pack install: ComfyUI Manager → "MiniMax H3 Audio T8", or git clone https://github.com/T8mars/comfyui-minimax-h3-audio-T8 into ComfyUI/custom_nodes, restart. No extra pip deps - it's a manifest reader. (ffmpeg on PATH is a family requirement for the save/compose ends of the chain.)

    Common issues

    has_context is false when you're sure a segment was accepted. Either chain_id doesn't match the manifest you accepted into, or the manifest lives somewhere this node isn't looking. Check the manifest_revision output - if it's stale, the manifest your Review & Accept node updated isn't the one this node reads.

    Your candidate keeps getting rejected as a stale continuation. You're not using the accepted_candidate_id output as the parent. Wire it from this node into Candidate Save's parent_candidate_id instead of hardcoding or guessing - that's literally the identity the manifest is keyed on.

    CategoryT8/MiniMax H3/Long Video/Experimental

    Inputs (2)

    NameTypeDefaultDescription
    chain_idSTRINGmy_h3_long_video
    segment_indexINT00–99999

    Outputs (5)

    NameTypeDescription
    contextH3_T8_CONTEXT
    has_contextBOOLEAN
    accepted_candidate_idSTRING
    manifest_revisionINT
    report_jsonSTRING