MiniMax H3 Trajectory Checkpoint Load / 轨迹续跑 (Advanced)

The resume half of the trajectory pair. MiniMaxH3TrajectoryCheckpointLoadT8Advanced takes a checkpoint saved by the Trajectory Checkpoint Save node and rebuilds everything the second sampling stage needs: the latent state, the remaining sigmas, and the resume noise. Wire those into a second SamplerCustomAdvanced and the run continues from the split point as if the first half had just happened - which, mathematically, it did.

How it fits together

The full pattern is: Trajectory Probe (split the schedule) → SamplerCustomAdvanced stage 1 on the high sigmas → Checkpoint Save → [later, possibly a fresh ComfyUI process] → this Load node → SamplerCustomAdvanced stage 2. The Load node's job is to reconstruct the state in the sampler's internal x_sigma space - the format the resume path actually samples from - instead of trying to re-derive the latent from a sigma and a noise tensor, which is where naive checkpointing loses precision.

The inputs

checkpoint_path (where Save wrote it), plus model, sampler and sigmas - the same-session T8 dual_clock_euler model and its schedule, because the checkpoint is bound to that identity. The contract check is what makes this safe: load a checkpoint with a mismatched model and it should refuse rather than silently produce garbage.

The outputs, and the exact wiring the description tells you to do

• checkpoint_latent → the latent input of the second SamplerCustomAdvanced.
• remaining_sigmas → its sigmas input (this is the low_sigmas half, so the run finishes quietly and precisely instead of re-noising).
• resume_noise → the noise input of the second sampler.
• report_json → what was loaded and whether the contract matched.

Installing:

part of MiniMax H3 Audio T8. Manager → "MiniMax H3 Audio T8", or:

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

Restart. No mandatory pip deps.

The limits, stated plainly

This resume path only supports dual_clock_euler + native_flow - the stateless T8 sampler where a clean split is even possible. DPM++, SDE/ancestral samplers and third-party wrappers are out, and you can't resume from an interruption mid-Transformer-forward; the checkpoint boundary is the step boundary. Also don't treat "resumed successfully" as "identical to a single uninterrupted run" - the pack has verified bit-exact results on a fixed 4-step contract, but that's proof of the mechanism on one configuration, not a universal guarantee. Check your ears and your eyes.