Frames Masks ZeroOut

Once you've built a temporal_mask with something like Frames Concat Masks - a per-frame stack that tells RES4LYF's temporal conditioning which frames belong to which zone - you'll occasionally want to knock one frame out of it without rebuilding the whole stack. Frames Masks ZeroOut does exactly that: give it a temporal_mask and a frame index, and it zeroes that one frame's slice while leaving everything else untouched.

The obvious use is a transition frame - one spot in a WAN clip where you don't want any zone actively guiding, maybe because it's a cut point, a blend, or just a frame you'd rather leave neutral rather than force into whatever zone assignment the surrounding frames got. Rather than re-authoring your entire ten-frame mask stack to fix one frame, you patch it after the fact.

Inputs and output

• temporal_mask (MASK) - required. This is the same MASK type Frames Concat Masks produces, so this node slots in right after it in the chain.
• zero_out_frame (INT, default 0, range 0-10000) - the index of the frame to zero out. Zero-indexed, so frame 0 is the first frame in your stack.
• Output: temporal_mask (MASK) - the same stack, with the specified frame's slice zeroed.

You can chain several of these if you need to zero out more than one frame - each instance handles one index.

Installing it

Part of the RES4LYF pack:

• ComfyUI Manager - search "RES4LYF," install, restart.
• Manual - cd ComfyUI/custom_nodes && git clone https://github.com/ClownsharkBatwing/RES4LYF, then cd RES4LYF && pip install -r requirements.txt, restart.

No models or extra dependencies specific to this node.

Common issues

Nothing seems to change. Double-check zero_out_frame is actually within the frame count of the temporal_mask you're feeding it - if you built a 6-frame mask and set the index to 8, there's no frame 8 to zero out, and the node has nothing to act on. Count your frames before setting the index; it's zero-indexed like most frame counters in this pack.

Wrong frame got zeroed. This is almost always an off-by-one on the index itself, or a mismatch between the frame order you assumed when building the mask (via Frames Concat Masks) and the order it actually ended up in. If frame 3 looks zeroed but you meant frame 4, recount from zero rather than assuming 1-indexing.

You need to zero out a range, not one frame. This node only takes a single index per call. For a run of consecutive frames, either stack multiple ZeroOut nodes in sequence or reconsider whether it's simpler to just leave that range out of the mask when you build it with Frames Concat Masks in the first place.