IAMCCS WAN CineInfo PURE

If you've ever stared at a huge IAMCCS shotboard and wondered what's actually inside it, this is the node for you. IAMCCS_WanCineInfoPure ("IAMCCS WAN CineInfo PURE") is the translator in the PURE shotboard pipeline: it takes a IAMCCS_WAN_SHOTBOARD in one end and hands you a tidy, typed IAMCCS_WAN_TIMELINE_PLAN object out the other, plus plain FLOAT/INT values you can wire straight into other nodes.

Why bother? Because the shotboard is a dict-shaped blob of timeline order, first/last-frame pairs, and prompt-relay chunks. Downstream PURE nodes (notably IAMCCS_WanFLFPairFromTimeline) want a single, well-formed plan object, and you want to see the frame rate, chunk count, and duration as plain numbers - not by squinting at a JSON dump. When a 40-chunk sequence is misbehaving, this node is the first place you look.

The "PURE" in the name means native ComfyUI, no WanVideoWrapper dependency. That's the whole design philosophy of this corner of IAMCCS-nodes: everything runs on stock ComfyUI primitives.

How it works

The node reads the board's timeline_order, flf_pairs (the start/end image pairs that define each chunk), and promptrelay_chunks, then packages them into a timeline_plan dict carrying the board's frame rate, total duration, and image dimensions. The chunk count is just the number of FLF pairs. If you have two or more pairs, it also logs a continuity check between pair 0's end image and pair 1's start image - a nice early warning when your storyboard has a gap in it.

Inputs and outputs that matter

There is exactly one input, cine_linx (type IAMCCS_WAN_SHOTBOARD). That's it - you feed it the shotboard and get back:

• timeline_plan - the object you wire into IAMCCS_WanFLFPairFromTimeline and IAMCCS_WanRelayOrBypassPure.
• frame_rate, chunk_count, duration_frames - plain numbers for anything downstream that needs pacing or count info.
• timeline_order_json and report - both are STRING JSON dumps you can park in a ShowText node to eyeball the structure. The report includes promptrelay_enabled and how many relay chunks exist, which is the fastest way to confirm your prompt-relay setup actually registered.

Install

It's part of IAMCCS-nodes, so you install the whole pack once:

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

Then restart ComfyUI. Or just search "IAMCCS" in ComfyUI Manager. There are no model downloads and no extra pip dependencies for this node - the heavy lifting is a pure in-memory transform. Note the pack's stated floor: ComfyUI ≥ 0.3.0, Python ≥ 3.12, Torch ≥ 2.8.

Gotchas

Because the plan object is a custom dict type, it has no graph preview - if you want to see it, read the report output, not the wire. Also remember this node is introspection only; it doesn't load images or encode anything. If your board looks empty (chunk_count of 0), the problem is upstream in whatever built the shotboard, not here. Keep the pack updated - this "PURE" family is moving fast between releases.