H3 Project Context Latent Load

Context continuity in the MultiTrack pipeline has a practical requirement: to start a segment in Context mode, you need the previous segment's saved latent - an MP4 alone is not enough, because the continuation is seeded in latent space, not from pixels. easy h3ProjectContextLatentLoad is the node that fetches that saved latent back out of the project folder. In the project pipeline it's what makes resuming from a later segment work automatically; the easy multitrackProject node reads it internally. Used by itself, it's how you'd re-enter a project's context chain from a custom graph.

How it works

The node reads the project's project.json manifest, finds the requested segment, resolves which generation of that segment is currently active, and loads its stored context latent file from disk. That indirection - manifest → active generation → file - is the whole design. Because the manifest tracks which version is active, this node always gives you the same latent the combine node would show as the primary version; if you regenerated a segment in new mode, "active" follows the newest generation.

Two details matter:

• resolution - high (default) loads the final high-res context latent; low falls back to the first-pass context_latent_low if one was saved. In dual sampling, the second pass consumes high-res context and the first pass consumes low - that's why the project stores both.
• It's strictly read-only - it never writes or modifies the project. It also guards against path escaping (a latent path that tries to leave the project directory is refused), which is a reassuring touch for a file-loading node that takes a user-supplied name.

Inputs: project_name, segment_index (zero-based - unlike the project node's 1-based segment_start_number, another way to get confused), and resolution. Output: a single context_latent you can wire into a continuity node like easy MiniMaxH3MotionContextHard.

Why you'd use it outside the pipeline

Say you hand-built an H3 graph with Save/Resume Latent nodes, or you want to continue a project that the pipeline started. This node lets you address a saved context by project + segment instead of hunting for a .latent file path. It's the pipeline's own approach made reusable: load the previous segment's active context, feed it to a hard-continuity node, and your new segment starts exactly where the old one ended.

Installation

Part of ComfyUI-Easy-Media:

# FFmpeg first
cd ComfyUI/custom_nodes
git clone https://github.com/yolain/ComfyUI-Easy-Media

Restart ComfyUI or install via Manager (search "ComfyUI-Easy-Media"). No extra dependencies; it reads files the project node already wrote.

Troubleshooting

• "No active H3 ... context latent for segment N in project X" - that segment has no saved context (it may have been generated in Shot mode, deleted, or never completed). You can't continue from something that isn't there.
• "H3 context latent was not found" - the manifest references a file that's gone, usually because a version was deleted. Regenerate the referenced segment.
• Wrong content shows up after a regeneration - the manifest points at the active generation; if you changed versions in the combine node, make sure you're reading the generation you think you are.

It's a small loader, but it's the node that makes "resume from segment 4 of a 12-segment project" a one-setting affair instead of a path-hunting expedition. And it's a clean illustration of why the pipeline stores context latents at all: continuity lives in the latent files, not the finished videos.