Reference-Guided Video Continuation feature
Dear SeaArt Team
It is good to see the new scene-guidance possibilities offered by the “Reference to Video” function, for instance in your Wan 3.0 and MiniMax H3 related models.
However, generating two or three connected clips that form one continuous scene still faces a major limitation: prolongation based mainly on the final frame of the preceding clip tends to induce substantial drift in reasonably complex / filmic scenes, while genuine persistent scene memory across clips would be the natural way forward – but is not yet available.
A practical intermediate solution might be to allow users to provide a separate set of Previous-Clip References, in addition to the reference images for the clip currently being generated. The former would serve as context anchors only: user-selected frames showing what has already been established in the preceding clip – characters, clothing, objects, spatial configuration, camera perspectives, etc. – without being treated as content or keyframes that should appear in the new clip.
The user would deliberately select these frames and describe, where useful, their chronological or spatial relation. A camera orbit is a simple example. Suppose Clip 1 moves roughly halfway around a scene. The user could provide several representative frames along that trajectory and indicate their approximate camera positions. One suitable frame near the end of Clip 1 – not necessarily its literal final frame – could then serve as the start frame for Clip 2. The new clip would continue the orbit from there, while the other Previous-Clip References provide visual information about parts of the room, characters, clothing, or objects that may no longer be visible in that start frame. Crucially, these frames describe the preceding clip; they are not frames that the new clip should reproduce.
In other words, the user manually provides and structures part of the scene memory that a fully persistent system would otherwise have to infer and retrieve automatically.
My concrete feature request would therefore be to add a second, clearly separated reference input for video continuation: Previous-Clip References – user-selected frames from the preceding clip that condition the continuation but are explicitly excluded from the timeline to be generated.
From a UI perspective, it might therefore make sense to separate the Previous-Clip Context (verbal description + reference images) from the actual generation prompt (generation instructions + new reference images), with each field having its own associated reference images and text description. Besides keeping “what has already been established” separate from “what should happen next”, this would also keep image referencing simple and unambiguous: @Image1 in the Previous-Clip Context field would refer to the first reference from the preceding clip, while @Image1 in the actual generation prompt would refer to the first reference image for the new clip. This avoids having to mix two sets of images serving two different purposes within a single prompt. The exact UI implementation is of course secondary; the key requirement is a clear separation between previous-scene context and current-clip generation.
This new Reference-Guided Video Continuation feature could provide a relatively lightweight bridge between current last-frame prolongation and future persistent scene-memory systems, while leaving the difficult-to-automize selection, retrieval, and description of the relevant previous-scene information to the user.
As a related feature request, allow users to specify whether each uploaded image for the clip to be generated is a start frame, end frame, or reference frame. (While there can be multiple reference frames, the start frame and end frame must each be unique.) At present, users have to choose between the “Reference to Video” option and the Start/End Frame option. As the example above illustrates, it is essential for this approach – but also useful for one-off clips – that users can explicitly assign these different roles to individual images within the same generation.
P.S. For simple linear clip prolongations, the current prolongation functionality already in place is fine. For filmic / scene-heavy scenarios that tell a coherent story, which needs to be consistently visualized, this is where this feature would probably shine.
Thanks for sharing this request with the development team, if you think it could help to improve SeaArt’s consistent-multi-clip generation capabilities.
Best regards,
Scotti
Log in to comment and vote
Comments1
H N (Scotti.Q)
Sep 21
Two important clarifications to the feature request above:
1. Previous-Clip and new generation images should be mutually addressable.
The purpose of separating the Previous-Clip Context from the actual generation prompt is to separate the two inputs formally — by means of two distinct input fields — while keeping them explicitly connected at the contextual level. (That important point was not sufficiently clear in the feature request above.) The new generation prompt should be able to directly draw on the individual images selected for the Previous-Clip Context — and vice versa. The Previous-Clip Context is intended as a relevance-focused user selection of information from the preceding clip, rather than a reproduction of its complete original prompt and image inputs. For example, in the prompt to the continuation clip, the user might ask for a facial expression or some other visual detail to match @PreviousImage5, referring to the fifth image user-selected for the Previous-Clip Context. In turn, the text description within the Previous-Clip Context field may say: “The garden party unfolds in a golden-hour setting, visually represented by @Image2”, where @Image2 refers to the second image uploaded for the continuation clip. A dedicated namespace for Previous-Clip images versus new clip images would keep such mutual cross-references unambiguous (e.g. @PreviousImageX versus @ImageY for the new clip). In a UI where image references can also be inserted by just clicking their thumbnails, this could happen automatically; the essential requirement is that images in either input field remain individually and unambiguously addressable from the other.
2. Visual inputs for the new clip should be optional — no mandatory start frame
The proposed continuation mechanism should not require either a start frame, an end frame, or reference images for the clip to be generated. (This is more general and flexible than the above feature request that assumed at least a start frame for the new clip.) In the simplest case, the user could provide a Previous-Clip Context and text generation instructions for the new clip only, resulting essentially in text-to-video mode — but conditioned on an already established, user-curated context rather than starting from scratch. A start frame, an end frame, and additional reference images — next to the prompt for the new clip — could be included by the user where both useful and available for the intended continuation.
For the purpose of this proposal, I assume that the Previous-Clip Context contains at least one image, regardless of whether that image originally served as a start frame, end frame, or reference image. This visual input is what motivates separating the Previous-Clip Context from the regular generation prompt in the first place.
(Even a purely text-based Previous-Clip Context, i.e. where the previous clip was generated via t2v, could be valuable in specific cases. One practical use case would be a more complex established setting or scene configuration in the preceding clip that the continuation clip builds upon in a focused way. Reestablishing all relevant details in the new prompt may lead to confusion between what is presupposed and what needs to be generated in concrete terms.)
***
Related work: “Context as Memory” (SIGGRAPH Asia 2025) already explores the use and retrieval of past-generation frames as memory for scene-consistent video generation. The proposed feature could be viewed as a user-guided, immediately controllable counterpart: rather than requiring the system to determine the relevant past-generation context automatically, the user explicitly selects and describes it. Such user-curated context could potentially also provide useful training data for a later automated approach.
Context as Memory – SIGGRAPH Asia 2025
***
Happy to chat more, if helpful, or stress-test, if you lean into that route (several use-cases on pile).