DIGIT Video Saver
Save Veo clips to a VFX pipeline — batch siblings included
- video
- video_paths
- filepaths
The DIGIT pack's video generators (Veo, Seedance, H3, Omni) hand you videos in a custom ComfyUI VIDEO type, and the stock save nodes don't really know what to do with those. DIGIT Video Saver is the intended landing pad: it takes a single video or a batch of video paths and writes them into the same PROJEKTS/project/shots/shot/subfolder/task/ structure as the Image Saver and Uber Saver, with auto-incrementing frame numbers and a workflow sidecar.
If you've got one DIGIT video node, this is the natural next node after it - it's the half of the pipeline that turns "a video exists in ComfyUI's temp folder" into "a properly named clip in the right place."
The inputs
projekts_root/project/shot/folder- the destination. Project folders use the#####_namepattern to appear in dropdowns; type a new shot/folder and use the + buttons to create it.filename- leave empty and it becomesPREFIX_SHOT_TASK; frame number and extension are appended.start_frame(1001 default) andframe_pad- the frame numbering.save_workflow-ui,api,ui + api, ornone. Writes the metadata sidecar that lets you trace a saved clip back to its prompt and settings.video- a singleVIDEOinput, straight from a generator node'svideooutput.video_paths- a batch of paths from the generator'svideo_pathsoutput. This is the batch path: connect it and every clip from the run saves with sequential frame numbers. For asample_countof 4 from DIGIT Veo Video, that's four files in one queue.
Output: filepaths - the saved paths, as a string.
How it works
The interesting bit is batch handling. When a DIGIT generator produces multiple clips, they land in ComfyUI's temp folder as siblings sharing a timestamp prefix (veo_…, dance_…, h3_…). The saver recognizes those prefixes, globs the sibling files, and saves them all - so batch output doesn't require you to wire up four separate save paths. If you feed it a plain single video, it just saves that one.
Setup and gotchas
Same pack install as everything else: ComfyUI Manager, search comfyui-digit, restart. Set DIGIT_PROJEKTS_ROOTS to your mount points or let it auto-detect and fall back to ~/PROJEKTS.
The same failure guards as the rest of the saver family apply: a placeholder (no shots found) shot raises rather than creating junk folders, and path segments with / or .. are rejected. Files always save as MP4. One thing worth knowing: the batch-sibling recognition keys off the generator's filename prefixes, so it works with DIGIT's own video nodes out of the box - if you hand it a video from some other pack, save it as a single clip rather than expecting sibling magic. It's a narrow node, but it closes the loop on every DIGIT video workflow.
Inputs (12)
| Name | Type | Default | Description |
|---|---|---|---|
| projekts_root | COMBO | 1 options: /root/PROJEKTS | |
| project | COMBO | 1 options: | |
| shot | COMBO | 1 options: | |
| folder | COMBO | 1 options: comfy/comp | |
| filename | STRING | What to name the file. Leave empty for PREFIX_SHOT_TASK. Frame number and extension are added. | |
| start_frame | INT | 10010–99999999 | — |
| frame_pad | INT | 41–8 | — |
| save_workflow | COMBO | 4 options: ui, api, ui + api, none | |
| videoopt | VIDEO | — | |
| video_pathsopt | VIDEO_PATHS | — | |
| subfolderopt | STRING | comfy | — |
| taskopt | STRING | comp | — |
Outputs (1)
| Name | Type | Description |
|---|---|---|
| filepaths | STRING | — |