Add reference-aware no-reencode video joining

This commit is contained in:
2026-10-12 09:05:22 +00:00
parent a4063ef60a
commit 69d93e685a
3 changed files with 119 additions and 34 deletions
+17 -13
View File
@@ -4,25 +4,29 @@ Generic ComfyUI utility nodes under the Dumas brand. The repository contains
image, JSON and video utilities and intentionally has no model-specific video
sampler dependency.
## Video nodes
## Sequential video assembly
### Dumas Standalone Video
Encodes an IMAGE batch and optional AUDIO into two files:
- `full_clip`: every generated frame, including any continuation overlap
- `complete_clip`: the same clip with `overlap_frames` removed before encoding
The full clip is the source for the next sequential generation. The complete
clip is the assembly-ready segment. Removing the overlap before encoding means
the final join does not need to re-encode an already assembled film.
`DumasStandaloneVideo` saves both the complete generated clip and a full copy.
For a continuation clip, set `reference_frames` to the number of frames taken
from the previous clip for continuity. The value is returned as the final
`reference_frames` output so it can be wired directly into
`DumasJoinVideoClips`.
### Dumas Join Video Clips (No Re-encode)
Accepts up to six completed clip paths and concatenates them with FFmpeg stream
copy (`-c copy`). It validates codec, dimensions, frame rate, pixel format and
audio compatibility before joining. The input clips must already have their
continuation overlap removed.
`DumasJoinVideoClips` accepts one reference-frame input for each clip. It trims
that many frames from the beginning of any clip whose value is greater than
zero, then concatenates the resulting files with FFmpeg stream copy. This
avoids a full re-encode of the assembled video. Clip 1 normally remains at
zero; continuation clips receive the reference-frame output from their
standalone nodes.
Stream-copy trimming is codec/keyframe-aware: the requested boundary is
converted using the clip's frame rate, but a codec may choose the nearest safe
packet boundary. For exact frame cuts, use the existing `complete_clip` output
or accept a re-encoded workflow.
## Other nodes