Video OverlappingSeparation test
Split one video into two overlapping halves to test seam continuity
- video
- mask
- video1
- video2
- mask1
- mask2
- OverlappingFrame
This one's got _test right there in the class name, and I'd take that at face value - this reads as the author's own diagnostic tool rather than something meant to anchor a production pipeline, and it's honest of the pack to leave that in the name rather than dress it up. What it does: take one video and split it into two halves that deliberately share a chunk of frames at the seam, so you can check what your continuity logic does with that overlap before you trust it on something that matters.
The reason overlap matters at all: chaining video generations end-to-end almost never looks seamless on its own. The standard workaround - the same idea AnimateDiff's sliding context window popularized for generating video longer than a model's native window - is to overlap the tail of one chunk with the head of the next and blend across that shared region, so there's no hard cut where the model's temporal "memory" resets. This node doesn't do that blending. It does the reverse: it takes a video you already have and cuts it into two pieces that share OverlappingFrame frames, which is exactly the shape of input a stitching/blending step downstream would need to prove it works correctly.
How it works
OverlappingFrame sets how many frames are shared between the two output halves. The README recommends keeping both this number and your total frame count even; if your clip is shorter than the overlap you asked for, it just divides the clip evenly instead of erroring out.
The inputs and outputs that matter
OverlappingFrame(int, default 8, step 2) - how many frames overlap between the two halves. This is the only required input, and it's also passed straight through as an output - handy for wiring downstream so a later node knows exactly how many frames to expect overlapping without you hardcoding the number a second time.video/mask(both optional) - optional because you might only be testing the frame stream, or only the mask stream, not necessarily both.video1/video2- the two halves, sharingOverlappingFrameframes at the seam.mask1/mask2- the same split applied to the mask, if you fed one.OverlappingFrame- passthrough of the input value, useful for downstream bookkeeping.
How to install it
Through ComfyUI Manager: search "ComfyUI-WJNodes," install, restart. Or by hand:
cd ComfyUI/custom_nodes
git clone https://github.com/807502278/ComfyUI-WJNodes
then restart. Nothing to download - it's plain tensor slicing.
Common issues & troubleshooting
Don't expect to find this node in tutorials or example workflows - it's a test/dev harness, not a mainline building block, and the honest use for it is validating your own overlap-blend logic against a known split before you run it on a real long-video job.
If your total frame count is odd, or smaller than the OverlappingFrame you asked for, don't expect an error - per the README it just divides the clip evenly instead. If that's not the behavior you want for a particular test, adjust OverlappingFrame down rather than relying on the node to reject an input it doesn't like.
Inputs (3)
| Name | Type | Default | Description |
|---|---|---|---|
| OverlappingFrame | INT | 82–4096 | — |
| videoopt | IMAGE | — | |
| maskopt | MASK | — |
Outputs (5)
| Name | Type | Description |
|---|---|---|
| video1 | IMAGE | — |
| video2 | IMAGE | — |
| mask1 | MASK | — |
| mask2 | MASK | — |
| OverlappingFrame | INT | — |