AU+IMG2VID Project Timeline Planner (legacy alias)

The sibling you reach for when one segment's worth of math isn't enough. IAMCCS_AUIMG2VID_ProjectTimelinePlanner is the same family as the AU+IMG2VID Planner (both are legacy aliases of the Ltx2HelperModules classes), but instead of describing one segment it lays out the entire project timeline up front - total frames, total seconds, segment count, and the exact frame range of every segment - as one JSON document.

You'll recognize most inputs from the single-segment Planner: goal1_preset (custom / lowram_safe_videoclip / lowram_fast_videoclip / normal_quality_videoclip / lowram_monologue), fps, segment_seconds, target_duration_seconds, duration_source, planning_mode, content_profile, overlap_frames, ltx_round_mode, surface_profile, and backend_binding. The functional difference is in the outputs. Where the per-segment planner hands you current_segment_start_frames and current_segment_unique_frames, this node gives you the whole map:

• total_frames, total_seconds, segment_count - the project-level numbers.
• segment_seconds_out, unique_segment_frames - the per-segment contract.
• segment_ranges_json - the key one: the start/end frame range for every segment, which is what lets downstream nodes or an external tool place each chunk correctly.
• project_timeline_payload - the JSON the rest of the chain consumes (this replaces planner_payload; downstream helper modules read it the same way).

Why use this instead of the per-segment planner? Because for a long project you want one authoritative source of truth for where every chunk lands, computed once, rather than re-deriving it per segment and hoping the loop stays in sync. It pairs naturally with the runtime bridge and the audio timeline helpers, and it's also the node you'd put behind a frontend that displays the whole timeline before you commit to a long generation.

Same caveat as its sibling: the presets encode the author's pipeline assumptions. ltx_round_mode (up/nearest/down) matters because LTX-2 chunks live on the 8n+1 frame lattice - rounding up everywhere quietly inflates your project length, which is why nearest is often the more honest choice for a full-project plan. And if you're not feeding audio in and duration_source is set to audio, you'll get a plan that ignores your track entirely, which is confusing until you spot it.

Installing: part of IAMCCS/IAMCCS-nodes - one install covers it. ComfyUI Manager → search "IAMCCS", or cd ComfyUI/custom_nodes && git clone https://github.com/IAMCCS/IAMCCS-nodes.git, restart. No models or extra dependencies; it's pure planning math.

If the project-timeline concept sounds like overkill for a 5-second clip, it is - use the single-segment planner. But the moment you're trying to hold a 30-second, multi-shot video in your head, segment_ranges_json becomes the thing you build the rest of the graph around.