IAMCCS CineInfo

Every IAMCCS Cine workflow funnels its plan through one opaque cine_linx connection, and sooner or later you need to grab something out of it - the timeline, the prompts, the duration, a preview image. IAMCCS CineInfo is the small breakout node for exactly that: one input, fifteen outputs, nothing to configure. The source sums it up as a "small breakout node: one cine_linx input, classic workflow outputs." It's the least intimidating node in the Cine stack and a good place to start poking at what the Shotboard actually planned.

How it works

Connect a cine_linx (from a Shotboard planner, the Cine Filmmaker, or anything that produces the state) and it reads the plan fields out of the payload. It also passes the cine_linx through untouched, so you can drop it into a chain just to inspect without breaking anything. The report output lists what it found - a genuinely useful debugging surface when a field comes back empty.

The outputs that matter

There are fifteen; the ones a beginner will actually wire:

• flf_timeline - the first/last-frame keyframe timeline as text.
• global_prompt / local_prompts / segment_lengths - the conditioning material and per-segment durations.
• max_frames, duration_seconds_int, frame_rate_int, width, height - the frame math for latent/length nodes.
• multi_output / image_1 / first_stage_preview - images from the board (reference previews or first-stage outputs).
• cine_linx - passthrough, for chaining.
• report - JSON rundown of what was extracted.

The rest - promptrelay_epsilon, segment_lengths, local_prompts - exist for the PromptRelay conditioning path; leave them until you're building that.

Installing it

Part of IAMCCS-nodes:

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

Restart ComfyUI, or install via ComfyUI Manager by searching "IAMCCS". Baseline: ComfyUI ≥ 0.3.0, Python ≥ 3.12, Torch ≥ 2.8. No models to download.

The honest take

CineInfo and Cine Filmmaker are the same family of node - Filmmaker is the superset with guide_plan_json, guide_data, and the audio/visual segment JSONs added. If you only need the classic fields, CineInfo keeps the output list shorter and the graph cleaner. The real gotcha is expectations: this node only extracts what's actually in the cine_linx it receives. If a field comes back empty, the answer is almost always upstream - the planner never wrote it - not a bug in the breakout. Read the report before you go hunting in the wrong place.