Why does the workflow require exactly 8 images?

It’s designed to create 7 FFLF videos from adjacent pairs. With 8 ordered keyframes, the pairs are 1–2, 2–3, …, 7–8. If you need more or fewer shots, duplicate/remove the pair-splitting path accordingly.

How do I ensure the frames are in the correct order?

Use BatchImagesNode with naturally sorting filenames (e.g., 01, 02, …, 08). If loading individually, double-check each LoadImage path. The contact sheet preview from SaveVideo is the quickest way to verify.

My images don’t match 16:9—will they be cropped or stretched?

Set the PrimitiveNode output to 1920×1080 and choose consistent image sizes. If your sources vary, add a resize/crop step before batching to avoid unwanted letterboxing or distortion in the preview and Kling outputs.

Kling 3.0 calls are failing or timing out—what should I check?

Confirm your Kling node/API configuration, rate limits, and per-shot duration. Try lowering resolution or length, queueing fewer segments at a time, and ensuring stable network connectivity before re-running.

Step 3: Contact Sheet Workflow

This ComfyUI tutorial walks you through a contact sheet workflow that turns 8 ordered images into a structured storyboard and 7 adjacent keyframe pairs for Kling 3.0 FFLF video generation. The pipeline starts with LoadImage and BatchImagesNode to ingest your files in a strict left-to-right timeline. A set of utility/custom nodes (IDs: f7abaa3a-5e87-4354-bab6-f43320cd490f, 02da9128-7c15-4c46-96bc-1dd68e5bc490, 3426003b-7b3a-4d37-8a2f-e0f8adb05712, c61d617f-c72d-4f4c-8659-bd6f884d1a1e, 4b301c11-bc16-4096-9441-e0648a04aa4d, 2ab1ef49-3518-4f71-b703-f8ef12f32214, b3fe4254-e196-429e-9f45-96c92113e406) handle layout, pairwise splitting (1-2, 2-3, …, 7-8), and packaging to downstream video nodes. PrimitiveNode exposes the core knobs—1080p resolution, frame rate, per-shot duration, and optional padding—while Reroute keeps the graph readable. SaveVideo exports a 1080p preview so you can quickly verify sequencing and framing before running the heavier generations.

For FFLF (first/last-frame–guided) generation, each adjacent image pair is passed to the Kling 3.0 node to synthesize motion constrained by your start and end frames—ideal for consistent, controllable transitions across a 7-shot sequence. If enabled, a Gemini-3.1-flsih-lite helper node can auto-summarize shot intents between each pair to keep prompts consistent (optional metadata only; it’s not required for rendering). The result is a fast, reliable way to validate continuity, then batch-generate seven cohesive clips at a clean 1920×1080 output.

FAQ

Preguntas Frecuentes

Ver todos los workflows