H3 Context Load Latent

H3 Context Load Latent is the other half of the save/load pair that moves a clip's latent across runs. The Save node writes the previous clip's AV latent to disk; this node loads it back and hands it to H3 Context, where the tail audio gets sliced out and pinned so the next clip continues the sound rather than starting a soundalike. If you're using the latent path (the pack's default), this is how "the model still knows what the last clip sounded like" actually happens.

There's a temptation to skip it because the Hub node also emits a context_latent. Don't get confused: H3 Project Hub resolves the approved tail's latent from the project manifest - that's the project way of doing chains, and it's the one you should use if you're building with the Hub. H3 Context Load Latent is the file-based way: you wire it up when you're hand-building a graph with H3 Context alone and pointing it at a specific saved latent.

How it works

It reads a .safetensors file written by H3 Context Save Latent and returns a single LATENT. That latent is only for H3 Context's context_latent input. It is not a decodable latent - do not wire it into a VAE decode, you'll get garbage. The node also keys its cache off the resolved file's mtime, so when the file behind the path changes (a new save, an overwritten slot) the next run picks it up instead of serving a stale latent forever.

The inputs

• latent_path (default h3_context) - a file, a folder, or the same filename prefix you gave the Save node. Relative paths resolve against the ComfyUI output directory. Pointing at a specific file always loads that file, ignoring clip_index.
• clip_index - the clip to continue from: that clip's slot is loaded. Generating clip 2 from clip 1: set 1 here and 2 on the Save node. At 0 it loads the newest file in the folder instead - simpler, but not retry-safe: a re-roll's newest file is the rejected attempt's own save, so your retry gets conditioned on the audio you just rejected. Once you're past clip 1, always set it explicitly.

Install

Same shared pack install as the rest of the suite: ComfyUI Manager → search "H3 Project Suite", or cd ComfyUI/custom_nodes && git clone https://github.com/Adudeguyman/ComfyUI-H3-Project-Suite, restart, hard-refresh. Reading relies on safetensors, present in any standard ComfyUI.

The pairing rule is the one thing to internalize, and it's the mirror of the Save node's: Save gets the clip you're making, Load gets the clip you're continuing from. Clip 2 continuing clip 1 = Save 2, Load 1. Get the pairing right once and it becomes the most boring, reliable part of your chain - which is exactly what you want from a loader.