VRGDG Overlap Preset

Video models have a hard ceiling on frames - MiniMax H3 natively wants windows in a 17n+5 pattern (5, 22, 39, 56, 73, 90, 107, 124) and doesn't care that your source clip is two minutes long. So if you want to process a long video with such a model, you chunk it, and if you naively chunk it you get visible seams where one chunk ends and the next begins. VRGDG Overlap Preset is the first node in the pack's four-node answer to that: it hands you validated, in-rule window settings so your chunks overlap and can be blended back together seamlessly.

Think of it as the spec sheet for the whole overlap rig. It doesn't process a single pixel. It computes three numbers - window, overlap, stride - and a blend mode, and it makes sure those numbers are legal for H3 before you waste a render discovering they weren't.

The three numbers and why they matter

For a given batch you need to know:

• window - how many frames the model actually sees per pass. Must follow 17n+5, hence the preset names: H3 Near 41 (39/5), H3 Balanced (73/17), H3 Trained (124/22), or Custom H3 where you enter your own.
• overlap - how many frames each window shares with its neighbor. That overlap is where the crossfade happens, so the same content gets seen twice and blended instead of cut.
• stride - how far the window advances each batch (window − overlap). This is the number you wire to the VHS Batch Manager's frames_per_batch input.

The node validates the nasty failure modes up front: a window that isn't 17n+5, an overlap smaller than 1, or an overlap ≥ half the window (which would mean a batch emits nothing) all raise clear errors before you queue.

You also pick the blend_mode here - cosine (default, the smoothest crossfade curve), smoothstep, or linear - and it's carried along in the config.

Inputs and outputs

Inputs are just the four settings: preset, custom_window / custom_overlap (only used on Custom H3), and blend_mode.

Outputs:

• overlap_config - a VRGDG_OVERLAP_CONFIG bundle carrying window/overlap/stride/blend. Wire it to the VRGDG Build Overlap Window node.
• window / overlap / stride - the same numbers as plain INTs. stride goes to the VHS Batch Manager's frames_per_batch. The other two are there for display or for any custom node you want to read.

The full rig (so the wiring makes sense)

1. VRGDG Overlap Preset → stride to the VHS Batch Manager frames_per_batch; overlap_config to Overlap Window.
2. VHS Batch Manager feeds source frames in strides (it's VideoHelperSuite, which this pack leans on heavily - you need VHS installed).
3. VRGDG Build Overlap Window turns each stride into a full window-sized model input (prepending the previous tail, padding the final batch).
4. Your enhancement model processes each window.
5. VRGDG Blend Overlap Output crossfades the processed overlap regions and emits every source frame exactly once.

So this preset node is step 1, and the reason it exists as its own node is that the window math has exactly one right answer per use case and it's easy to get wrong.

Install & note on the deprecated sibling

One clone gives you the whole overlap set plus the rest of the pack:

cd ComfyUI/custom_nodes
git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl.git

via Manager: search "VRGameDevGirl", restart, hard-refresh. You'll also need VideoHelperSuite installed (Manager finds it) since the standard VHS Batch Manager is a hard dependency of these workflows. Heavy requirements.txt applies as always - Windows portable: Cython + scikit-build-core first, Python 3.12 preferred.

If an old workflow you downloaded contains a node named "DEPRECATED – VRGDG Overlap Meta Batch Manager", that's the previous, broken version of this same job. Swap it for this Preset node plus a standard VHS Batch Manager - the deprecated node's VHS-compatible manager stopped getting requeued by VHS, which is why it was retired. This one plays by VHS's rules instead of replacing them.