Luma Ray 3.2 Extend Video

The Luma Ray 3.2 Extend Video node is how you keep a Ray 3.2 generation going. You take a clip you already made with a Luma Ray 3.2 node and extend it - either forward, so the new 5-second piece continues after it, or backward, so it becomes a lead-in before it. It's the node for turning a good 5-second moment into a longer, coherent sequence without restarting from scratch.

The key mechanic is that you don't feed it the video file. You feed it a generation id. Luma's Ray 3.2 nodes output a generation_id string alongside the video, and this node takes that id, tells Luma's servers which clip to continue from, and generates the extension. That's why the input is a string field rather than a video input - connect the generation_id output of another Ray 3.2 node (text-to-video, image-to-video, keyframes-to-video, or even another extend) and you're set.

The inputs that matter:

• source_generation_id - required. The generation_id output of a prior Ray 3.2 node. If it's empty, the node throws a clear error telling you to wire one up.
• direction - a dynamic combo with two options:
  • Forward (continue after) - appends the new clip after the source. This option also exposes a loop toggle so the extended video can loop seamlessly, forward-only.
  • Backward (lead-in before) - prepends the new clip before the source.
• prompt - text describing the new content. Up to 6,000 characters.
• resolution - 540p, 720p (default), or 1080p.
• seed - the Luma stub: controls whether the node re-runs; results are nondeterministic regardless.

Outputs are VIDEO and a fresh generation_id, so you can chain extensions off extensions.

The one rule that catches people: extensions are always 5 seconds. There's no duration control here - that's how Luma's extend API works. And the loop toggle only exists on the forward path, so don't go hunting for it in backward mode. Beyond that, the usual partner-node things apply: this is a paid API node billed to your Comfy account credits, you must be signed in, and if the partner-node family clogs your search, --disable-api-nodes removes it.