MiniMax H3 Load Latent Checkpoint (TJ)
Reading yesterday's clip back into today's — the resume-friendly half
- latent
If Save Latent Checkpoint is the pen that writes a clip's latent to disk, MiniMax H3 Load Latent Checkpoint (TJ) is the hand that picks it back up. Because H3 can't carry tensors between separate queue submissions, a multi-clip shoot has to round-trip the previous clip's latent through a file, and this node is the read half: it loads a <name>.h3lat.safetensors from output/one_minimax_h3/_latent_checkpoints/ and hands you back a proper H3 AV latent to feed into continuation logic.
The inputs are where the useful intelligence lives:
checkpoint_name- must exactly match the name the Save node used (clip001,prev_clip, whatever). Mismatched names mean "file not found," loudly.strict- ON (default): a missing checkpoint is an error. OFF: missing meanslatent=Noneand you carry on.index- connect the MiniMax H3 Prompt Queue'sindexoutput here, andstrictbecomes irrelevant: on index ≤ 1 (the first clip of a sequence) a missing file is fine and silently skipped; from clip 2 onward a missing file is a real error no matter whatstrictsays.
That index behavior is the part people underestimate. It exists because leftover checkpoint files from a previous, different-resolution session are junk - if you're starting a fresh sequence at clip 1, you don't want a stale file poisoning the first clip. So clip 1 never reads the file at all, by design. This is also why "stop the shoot, come back tomorrow, resume" just works: clip 2 onward read the checkpoint from disk, and as long as it's there, the sequence picks up where it left off.
Output is a single latent (the two-stream NestedTensor, cloned off the file's memory map so nothing holds the file open). It's meant to feed prev_latent on the Sequencer or Latent Continuation node.
Like its Save sibling, this is mostly an internal cog: the One-Take Sampler loads and saves checkpoints itself, so casual users won't wire this pair manually. It exists for the people hand-building a custom H3 sampler chain - and if that's you, the index wiring from the Prompt Queue is what makes the first-clip grace work without touching the strict toggle.
Install
Ships in ComfyUI-TJ_NODE:
cd ComfyUI/custom_nodes
git clone https://github.com/designloves2/ComfyUI-TJ_NODE
or via Manager, then restart. No extra deps beyond ComfyUI's H3 support and your own H3 model files (weights, video VAE, audio VAE) - and the license reminder applies as always: the H3 local-weights path excludes the US, EU, UK and South Korea.
Troubleshooting
- "체크포인트를 찾을 수 없습니다" on clip 2+ - a genuinely missing file. The Save node didn't run, or the name differs between Save and Load. Check
_latent_checkpoints/for what's actually there. - It errors on clip 1 - you're on an old version that predates the
indexauto-grace, or you haven't wiredindex. Wire the Prompt Queue's index and it stops demanding a file on the first clip. - Resolution mismatch later in the chain - you loaded a checkpoint from a different resolution session. Delete it and restart the sequence; the Sequencer will tell you if the shapes don't line up.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| checkpoint_name | STRING | clip001 | TJ_H3_SaveLatentCheckpoint가 저장할 때 쓴 이름과 동일해야 합니다. |
| strict | BOOLEAN | true | index를 연결하지 않았을 때만 쓰이는 수동 설정. ON(기본): 체크포인트가 없으면 에러. OFF: 없으면 그냥 latent=None. index를 연결하면 이 값은 무시되고 index<=1 여부로 자동 판단합니다. |
| indexopt | INT | 00–100000 | MiniMax H3 Prompt Queue (TJ)의 index 출력을 연결하세요. 연결하면 index<=1일 때만(첫 클립) 파일이 없어도 에러 없이 넘어가고, 2번째 클립부터는 파일이 없으면 진짜 에러로 알려줍니다 — strict 위젯을 수동으로 안 바꿔도 자동으로 이렇게 동작합니다. |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| latent | LATENT | — |