IAMCCS Cine Shotboard Planner V4

Shotboard Planner V4 is the pack's "here's where we're going" node. The docstring is refreshingly honest about it: V4 starts from the stable V3 timeline/meter UI and backend contract, then emits a neutral multi-track contract for future video, IC-LoRA, retake, camera, and audio-inpaint backends. In other words, it's the current planner shell that's deliberately future-proofed - the data it emits is designed to survive backend rewrites, so the plan you make today doesn't break when the pack's backend engines evolve.

How it differs from V3. Two things, both about the timeline contract:

1. Alias tolerance on the way in. timeline_data for V4 accepts IAMCCS shots/shotClips/motionClips/audioClips aliases and normalizes them. If your JSON uses the newer shot-clip vocabulary (or an older one), V4 parses it and exports a consistent structure.

2. Backend-compatible output on the way out. It exports segments/motionSegments/audioSegments - the exact structure the V4 backend consumes. Visual, motion, and audio tracks get their own normalized segment lists, which is what lets one timeline drive video guides, motion guides, and audio conditioning at the same time.

The inputs otherwise mirror V3: global_prompt (default "one continuous cinematic shot with coherent motion, stable identity, video-aware timing and cinematic-grade camera continuity" - note the new "video-aware timing" phrasing), duration_seconds (20s), frame_rate, guide_policy (default every_checked_row), min_guide_gap_seconds, max_guides, default_force, promptrelay_epsilon, ltx_round_mode, the image resize controls, and the optional cine_linx input for chaining. Output is the single cine_linx socket.

The workflow it belongs to. Planner V4 → the Cine Shotboard V4 Backend, which takes the cine_linx plus your model and clip and produces the actual conditioned model, video/audio latents, guide data, and motion guide data. V4 is the authoring side of that pair; the backend is the execution side. (The Tail Trim Policy node and the V4 Crop Guides node sit in the same pipeline to handle the LTX 8n+1 tail after decode.)

Install. Same pack, same everything: ComfyUI Manager (search "IAMCCS"), or git clone https://github.com/IAMCCS/IAMCCS-nodes into custom_nodes, restart. ComfyUI ≥ 0.3.0, Python ≥ 3.12, no bundled models - you're bringing the LTX-2.3 stack.

Gotchas. V4 is the newest planner, and "neutral contract for future backends" means you're somewhat at the mercy of the pack's release cadence - keep it updated or a saved V4 workflow can reference a contract the installed version doesn't speak. Also don't over-rotate on the future-proofing: today, the reliable path is V4 into the V4 backend. If you're on an older hand-built graph, the Legacy planner might be the better fit until you're ready to migrate.