VRGDG Video Editor Session Loader

The VRGDG Video Editor saves your whole project to a session JSON, and the Remake Clip Queue walks that session scene-by-scene automatically. But sometimes you don't want the queue - you want one scene, precisely, now. VRGDG Video Editor Session Loader is the direct-access version: you give it the session path and a clip number, and it hands you everything you need to render that exact clip into a fresh workflow.

Think of it as the "load this specific shot" node for when a single scene needs rework and you want to work on it in isolation instead of inside the full editor. It's the surgical counterpart to the queue's automated sweep.

The three inputs

• session_path - path to vrgdg_temp/editor_session.json saved by the VRGDG Video Editor UI. This is your project state; without it, nothing loads.
• clip_number (default 1, up to 999999) - which clip in the session to pull.
• clip_path - an optional exact path that, if set, wins over clip_number. The tooltip is explicit: "If set, this is used before clip_number." So if you know the file, you can skip counting.

What it outputs

Everything a scene render needs, in one bundle:

• t2i_prompt and i2v_prompt - the text-to-image and image-to-video prompts the editor generated for this clip. Feed them straight to conditioning.
• captured_frame_path - the reference frame from the session, the starting image for image-to-video. This is the scene's visual anchor.
• selected_for_remake - whether this clip was flagged in the editor for a remake. Wire it into a switch if you only want to re-render clips that actually got marked.
• clip_name and clip_path - the clip's identity and its video file, so you know what you're replacing and where the original lives.

The clean shape of it is the point: load the session, get a bundle, render, and send the result back into the project. No hunting through JSON by hand.

How it fits

This node is the "open in its own workflow" escape hatch from the Video Editor. The editor is great for the whole-project view, but per-clip rendering gives you room to do something different with one scene - drop in a different LoRA, a different sampler, a manual touch-up - without rebuilding everything. That's genuinely useful when one scene is the weak link and you don't want the auto-queue to just regenerate it with the same settings and hope.

Install and the usual cautions

Standard pack install: ComfyUI Manager → search vrgamedev, restart, hard-refresh the browser. The session JSON is only as fresh as the last time you saved it in the editor - edit scenes, forget to save, and this node loads stale prompts. That's the classic gotcha, and it produces confusing output: the clip loads fine, the prompts are just old. Save from the editor, then load. And remember the session path lives under vrgdg_temp/, which the pack creates inside your ComfyUI install - if you've moved or renamed things, the default path won't exist.