IAMCCS Cine Filmmaker

The IAMCCS Cine system stores everything about a shot in one opaque cine_linx state - the FLF timeline, prompts, segment lengths, reference images, duration, all of it. That's great until you need to see any of it. IAMCCS Cine Filmmaker is the node that unpacks that state into every output the LTX sampling chain might want, in one place: the guide plan, the timeline, the prompts, the frame math, and a couple of preview images. It's the control panel for a shot planned on a Cine Shotboard.

The name undersells it. In source it's literally a super-set of the CineInfo breakout family - the "Filmmaker backend breakout for Shotboard Planner" - so if you only remember one of these breakout nodes, remember this one.

How it works

Feed it a single cine_linx and it extracts the plan fields that the Shotboard wrote. It's a pure reader plus passthrough: the cine_linx output passes the state along so you can chain it, and every other output is a projection of what's inside. It's the node you put after the planner and before the backend, as the explicit contract between planning and generation.

The outputs that matter

There are nineteen, but a beginner only wires a few:

• guide_plan_json - the explicit guide contract the FLF Productor consumes. This is the hand-off that matters most.
• flf_timeline - the first/last-frame keyframe timeline as text.
• global_prompt / local_prompts / segment_lengths - conditioning material and per-segment durations.
• max_frames, duration_seconds_int, frame_rate_int, width, height - the frame math, for wiring into latent/length nodes.
• multi_output / image_1 / first_stage_preview - images (reference board, or a preview) when you want to eyeball what's planned.
• guide_data - the typed guide data for the guide-application nodes.
• audio_timeline_json / visual_segments_json - audio and visual segment plans, for the audio path.
• report - JSON summary of what the board contained.

Installing it

It ships in IAMCCS-nodes:

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

Restart ComfyUI, or search "IAMCCS" in ComfyUI Manager. Baseline: ComfyUI ≥ 0.3.0, Python ≥ 3.12, Torch ≥ 2.8. No models to download for this node itself - it reads state and passes it on.

The honest take

The Cine system is opinionated, and this node is where that opinion is most visible: it assumes you're running the Shotboard planner and the LTX backend chain, and it hands you a wall of outputs to prove it. If that's your setup, it's the cleanest single hand-off point in the pack - one connection and the whole plan is visible. If you're not on the Shotboard path, the Dialogue Prompt Kit's shotboard_timeline_json can feed a plan in, and CineInfo is the smaller sibling when you only need a few fields. One warning: the pack moves fast and the newest LTX-2.3 backend instructions live on the author's Patreon, so if an output doesn't quite match your ComfyUI version, update the pack first - the README changelog is the ground truth for what's current.