DaSiWa AutoLong Stream Writer

This is the pack's most honest node: it exists so your old workflows don't break. DaSiWaAutoLongStream is the backward-compatible stream writer from the ComfyUI-DaSiWa-AutoLong pack, kept around for workflows built before the SVI Pro writer shipped. In the source it's literally the same class as DaSiWaAutoLongStreamSVIPro, called with overlap_frames pinned to 1 and interpolation_multiplier pinned to 2. No new behavior, no surprises - which is exactly the point.

If you're starting fresh, skip this and reach for the SVI Pro writer instead. But if you have a saved DaSiWa workflow JSON that uses this node, updating the pack won't strand it, and that's worth something. ComfyUI's workflow-sharing culture runs on "drag the PNG back in and it rebuilds," and it hurts when an update quietly orphans a graph you've been running for weeks.

What it does

It's the writer half of the AutoLong loop. DaSiWaAutoLongStart gives you the session info; this node takes the current segment's interpolated frames, writes them into a single persistent FFmpeg process, and re-queues the workflow until the last segment, at which point it finalizes the file and hands you the MP4. One encoder, one file, no concatenating clips afterwards.

Inputs and outputs that matter

The bookkeeping inputs - index, total_segments, session_id - all come straight from the Start node, and you should wire them, not type them. The ones you actually touch:

• frames - the current segment, already run through your RIFE interpolation stage.
• last_frame - the raw tail frame(s) to carry into the next segment. With overlap 1, that's the single final frame before interpolation.
• frame_rate - default 32; whatever your workflow renders at.
• crf and preset - H.264 encoding quality and speed tradeoff, defaults 17 and "medium". Leave CRF alone unless you know why you're changing it.
• filename_prefix - defaults to video/DaSiWa_AUTO_LONG inside your output folder.

Outputs are filenames (a VHS_FILENAMES object, so it plugs into the usual VideoHelperSuite-style preview/save chain) and video_path (the absolute path to the finished MP4). Because it hardcodes overlap_frames=1 and interpolation_multiplier=2, the node knows the second segment begins with duplicated frames, skips exactly 2*(1-1)+1 of them, and keeps the interpolated transition from the last overlap frame into the new content.

Install

Standard pack install - ComfyUI Manager, search "ComfyUI-DaSiWa-AutoLong", or:

cd ComfyUI/custom_nodes
git clone https://github.com/kokotu/ComfyUI-DaSiWa-AutoLong.git

Restart ComfyUI afterwards. No pip requirements, no models to fetch; just needs ffmpeg on the system, which any VideoHelperSuite install already provides.

Where people get burned

Same rules as the rest of the pack: don't queue the same workflow while an auto-run is in flight, and if you interrupt a run, reset iteration on the Start node back to 0 or the session state goes missing. Keep every segment at the same resolution and frame rate - the encoder refuses to keep going when the frame size changes mid-stream. One more, specific to this node: since overlap is fixed at a single tail frame, it can't carry a real motion state forward, so fast or dramatic motion can still jump at the seam. That's the limitation the warm-up writer exists to fix; it's also why new workflows moved on.