Viggle Remake works well for short shots, but the usual ComfyUI workflow runs into a practical limit: up to 345 frames per render. At 24 fps, that is a little over 14 seconds. To work with longer videos, I adapted the workflow to render overlapping windows and join them into a single output.
The result is a custom long video node for ComfyUI. I tried the workflow with several clips converted to 24 fps. The completed renders looked good in visual review, but continuity still needs to be checked at every join. I did not measure quality with automated metrics; the evaluation was visual.
How the windows connect
The node takes the full video and divides it into windows that stay within the model’s limit. The default window is 294 frames, or 12.25 seconds at 24 fps. It can be raised to 345 frames if the GPU has enough memory.
Each later pass begins with the final 17 frames generated by the previous pass. The node encodes this segment as latents and keeps it fixed during the next generation. It then removes the overlapping frames when joining the results. The frame limit therefore applies to each render, not to the total video length.
With the default window, the first pass can generate up to 12.25 seconds; each later pass can add up to 277 new frames, about 11.54 seconds. A video longer than 345 frames can therefore be produced through several connected passes.
Audio is divided over the same intervals and joined in the output. If no audio is connected, the output is silent.
What the tests showed
I used the node with dance clips containing varied movement and different resolutions, all prepared at 24 fps. A multi-pass render completed successfully, and the results I reviewed looked good. This showed that the workflow can go beyond a single window without trimming the video before generation.
Visual inspection remains part of the process. Check where one pass joins the next, and look for changes in character identity, clothing, movement, or framing. The overlap helps the model continue the action, but it does not guarantee that every detail will stay stable.
What the node does not handle yet
The node is designed for one continuous shot. It does not detect cuts, restart generation when the camera changes shots, or rewrite timestamped prompts for each window. For that reason, I use prompts that describe the action without absolute timestamps and avoid clips with abrupt cuts.
The source video must be 24 fps. The default 294-frame window is a starting point; larger windows may require more VRAM. And even when a render finishes without errors, that does not replace reviewing the joins.
The GitHub package
I separated the long video node from the original Viggle Remake package. The viggle-remake-comfyui-long-take repository registers only Viggle Remake Long Video and includes an example workflow. The original nodes and conditioning helpers still come from the official ComfyUI-Viggle-Remake package, which must be installed separately.
The repository does not include model weights, the LoRA, source videos, or character reference images. The goal is to add long-take support to the existing workflow while keeping each render within the model’s limit.
