β» Fade To Black
Fade a clip out instead of letting it stop cold
- frames
- frames
Fade To Black [DVB] is the mirror image of its sibling Fade From Black: it takes a frame set and ramps the last fade_seconds of it down to black instead of ramping the first frames up. One input frames, one fade_seconds float (default 1.0, min 0.1, step 0.1), one frames output. If your video ends and it's not fading out, it's probably not really over - this is the node that gives a clip a proper landing.
How it works
The fade length is computed from the set's framerate, so fade_seconds means what it says regardless of whether you're at 24 or 60 fps: one second of fade is one second of fade. The node applies a linear brightness ramp from full down to black across the last fade_length frames, leaving the front of the clip untouched. It's a brightness fade - darkening the actual pixel values - not an alpha overlay, so the end frames genuinely hit black rather than just compositing toward it.
Because it's computed in time rather than frames, this node is resilient: change the framerate on your Create Frame Set upstream and the fade still lasts one second. That's the behavior you want in a timeline-driven workflow, and it's the same convention Fade From Black, Blended Transition, and the rest of the transitions category use.
Where it belongs
The standard pattern is fades on both ends: Fade From Black into the start, Fade To Black out of the end, and the clip reads as intentionally framed instead of abruptly starting and stopping. It's also the go-to for a dip-to-black between two scenes - fade out to black, then let the next segment fade in - which reads more gracefully than a hard cut when the two shots are very different. Pair it with Frame Set Append to build a full multi-segment timeline and you've got a poor man's editor, entirely inside the pack.
The usual trap
Like every frame-set node in this pack, the output is the custom FRAME_SET type, and vanilla ComfyUI has no idea what to do with it. Trying to wire a faded set into Save Video or an encode node just fails to connect - this is the recurring complaint with the pack, and the fix never changes: pass it through Unwrap Frame Set [DVB] to get a plain IMAGE batch plus the framerate, then continue with standard nodes. Unwrap is also where you decide how gaps are handled, so if your set has been through splits and merges, that's the moment you'll know.
A small honesty note: it's a brightness fade, not a dissolve. Fading to black between scenes is a deliberate, cinematic choice - but if you wanted the two scenes to overlap and crossfade instead, that's Blended Transition [DVB], which does the dissolve properly.
Install
Search "Dream Video Batches" in ComfyUI Manager, or:
cd ComfyUI/custom_nodes
git clone https://github.com/alt-key-project/comfyui-dream-video-batches.git
cd comfyui-dream-video-batches
pip install -r requirements.txt
Restart ComfyUI after. No models to download - this is a brightness ramp over pixels, and it runs anywhere the pack runs.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| frames | FRAME_SET | β | |
| fade_seconds | FLOAT | 1.0 | β |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| frames | FRAME_SET | β |