Segment Planner Settings (shared)

IAMCCS_SegmentPlannerSettings is the shared-config hub for the pack's LTX-2 segment planning family. It exists because long video workflows get messy in a hurry: you've got a first-segment planner, continuation planners, a last-segment planner, maybe a couple of SuperNode internals - and every one of them wants to know how long a segment is, what preset to use, and how many overlap frames to carry. If those are separate widgets, they drift. This node is the single place you set them, and the other planners (SegmentPlannerLinked, and anything else that links these) read from it.

Think of it as the settings file for your segmentation, published as outputs instead of written on a sticky note.

How it works

It's a small piece of the same planning engine as IAMCCS_SegmentPlanner. It normalizes your choices (a videoclip preset maps to 10 seconds, monologue to 15, and auto_profile folds into explicit-preset mode), and if planning_mode is explicit_preset_seconds it overrides segment_duration_s with the preset's canonical length - so the duration and the preset can never contradict each other. There's also auto_sync_overlap: when on, the node replaces your overlap_frames with the value recommended for the matching preset profile (9 is the recommended default across the board).

The four optional *_in inputs are the reverse-direction override: any other node can push a segment_duration_s_in, planning_mode_in, segment_preset_in, or overlap_frames_in in and it wins over the widget. overlap_frames_in uses -1 as "don't touch" so you can wire a loop variable without clobbering the manual value.

Inputs and outputs

What you actually set: segment_duration_s (default 10), planning_mode (manual_segment_seconds / explicit_preset_seconds), segment_preset (5sec/10sec/15sec/20sec/videoclip/monologue), overlap_frames (default 9), and auto_sync_overlap.

Outputs mirror the inputs so they can feed link-driven planners directly:

• segment_duration_s (FLOAT)
• planning_mode (STRING)
• segment_preset (STRING)
• overlap_frames (INT)
• report (STRING) - a one-line summary including which auto profile matched, handy for verifying the node did what you meant.

A typical setup: one SegmentPlannerSettings feeding segment_duration_s, planning_mode, segment_preset, and overlap_frames into one or more IAMCCS_SegmentPlannerLinked nodes. Change the preset here, every planner follows.

Installing

Standard pack install: ComfyUI Manager → search "IAMCCS", or

cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git

then restart. Nothing to download - this node is a pure config/arithmetic node, no model files, no pip deps.

Gotchas

The overlap behavior surprises people: with auto_sync_overlap on, your hand-set overlap_frames is silently replaced by the profile's recommendation, which is 9 for every preset at the moment. If you deliberately run a different overlap for effect, keep auto_sync_overlap off. And be aware the *_in overrides beat the widgets by design - if a loop variable is feeding overlap_frames_in, that's what wins, and the widget is just a fallback.