Nodes/ComfyUI-Easy-Media/H3 Segment Save End
ComfyUI Node

H3 Segment Save End

The 'your clip is on disk' bell at the end of every segment

By yolain·Created 4 months ago·Updated about 23 hours ago· 184
H3 Segment Save End
    • video_path
    video_path
    project_name
    segment_index

    easy h3SegmentSaveEnd is the mirror image of easy h3SegmentSamplingStart: another dev-only, no-op node that the easy multitrackProject expansion drops into the graph at a lifecycle boundary - this one at the point where a segment's video has just been saved. Like its sampling-start sibling, it changes nothing. It takes a video_path, tells the frontend "segment N is saved," and hands the path back out.

    What it does

    Two inputs do real work: project_name and segment_index identify which segment just finished, and the node fires the project-refresh event (after_save) so the MultiTrack Project Video Combine widget reloads its timeline preview with the new clip. That's why, mid-run, you can watch segments appear in the combine preview one by one rather than waiting for the whole project to finish. The video_path input and output are pure pass-through - it's there so the node can be threaded into the graph without interrupting the flow of data.

    The point of a notification node

    ComfyUI's caching model means a plain node won't reliably announce "this happened" - it only reruns when inputs change. A segment that regenerates the same path twice in a row needs something that always fires, which is exactly what this non-idempotent dev node guarantees. So the visible behavior - the combine widget refreshing after each segment - is real, and it's the whole job.

    The practical takeaway for you: this node is why the combine node's "preview" feels live during a long project run, and why the queue logs a clean "after_save" marker at each segment boundary. If a segment saves but the preview doesn't update, the notification path is the first suspect - though in headless/API use the node silently falls back to doing nothing at all, which is harmless.

    You will not add this node to your own workflow. It arrives with the project expansion, and there's no reason to bypass it: it costs nothing and keeps the project UI honest.

    Installation

    It ships inside ComfyUI-Easy-Media:

    # FFmpeg first (the README's hard requirement)
    cd ComfyUI/custom_nodes
    git clone https://github.com/yolain/ComfyUI-Easy-Media
    

    Restart ComfyUI, or install via Manager (search "ComfyUI-Easy-Media"). No models, no dependencies.

    Troubleshooting

    • Preview doesn't update after a segment saves - check you're on the same project name in the combine widget, and that the frontend is connected. In API/headless runs this is expected; the files are still saved correctly.
    • Segment saved but the queue seems stuck - the node is a pass-through; look upstream at the actual save/artifact nodes. This node can't block or corrupt anything.

    It's a bell, not a mechanism. Knowing it exists means the "segment saved" moment in your logs and the live-updating preview are both explained - and if either stops, you know where the seam is.

    CategoryEasyUse/H3/dev

    Inputs (3)

    NameTypeDefaultDescription
    video_pathSTRING
    project_nameSTRING
    segment_indexINT

    Outputs (1)

    NameTypeDescription
    video_pathSTRING