Frames Slice Latent Raw

If you've got a longer WAN video latent and only want a chunk of it - a specific span of frames to refine, re-guide, or feed into a separate branch of your workflow - this is the node that grabs it. Frames Slice Latent Raw takes a batch of frame latents and a start/stop range and hands back just that slice, indexed straight out of the latent tensor. The "Raw" in the name is the tell: it's operating on latents directly, no VAE decode/encode round-trip involved, so it's cheap and it doesn't cost you any quality the way slicing after decoding to pixels and re-encoding would.

The practical use is trimming a clip down before doing more work on it - pulling out just the segment you want to run through RES4LYF's vid2vid editing, isolating a range to upscale or re-sample, or grabbing the frames you actually need as guide input for something downstream instead of dragging the whole latent batch through every subsequent node.

Inputs and output

• frames (LATENT) - the full batch you're slicing from.
• start (INT, default 0, min 0) - where the slice begins.
• stop (INT, default 1, min 1) - where the slice ends.
• Output: latent (LATENT) - the resulting sub-range.

The default start=0, stop=1 grabs just the first frame - worth noting if you drop this node in and get a single-frame latent back and weren't expecting it. Set both values to bracket the range you actually want before wiring it further downstream.

Installing it

Comes bundled with RES4LYF, no separate install:

• 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.

Nothing extra to fetch for this node specifically.

Common issues

Getting one frame when you wanted a range. This is almost always the default stop=1 catching people out - bump it up to cover the frames you actually want.

Slice comes back empty or errors. If start is set at or past stop, or past the actual number of frames in your frames input, there's nothing valid to slice. Check your frame count against both values before assuming the node is broken.

Guide frames or conditioning don't line up after slicing. If your workflow references frame positions elsewhere (a temporal mask built with Frames Concat Masks, for instance), remember slicing shifts everything's effective index - frame 10 in your original batch becomes frame 0 in the sliced output. Anything downstream that assumes the original numbering needs to be re-indexed to match the slice, not the source clip.