IAMCCS Cine Info 3

The CineInfo nodes break the video plan out of cine_linx; CineInfo 3 is the one that breaks out the audio side. Its source docstring is precise about the job: "Expose BoardMaker dialogue/foley metadata from cine_linx without cluttering the writer node." So instead of dragging your whole Shotboard just to get at the script, TTS text, foley prompt, or sound-effect chunks, you drop this one node in and those fields come out on their own ports. It's the "give me the dialogue plan" breakout.

How it works

It takes the required cine_linx, reads the board's script layers, audio tracks, and payload, and extracts:

• board_json - the raw board data.
• timeline_data - the board timeline (for FLF / video nodes).
• dialogue_script - the full dialogue script as text.
• tts_text_a / tts_text_b - per-speaker lines, ready for TTS. This is the pair you'll actually wire most of the time.
• foley_prompt - the sound-effects note from the board.
• woosh_chunks_json - the planned sound-effect chunks (the pack's "woosh/foley" chunk planner output) as formatted JSON.
• duration_seconds (float) - the board's duration.
• report - JSON with the source mode and which fields were found; it also lists the cine_linx resource keys, which is a genuinely handy peek inside the state.

Because it reads from a fresh clone of the state, it's safe to chain - it doesn't mutate the cine_linx it receives.

Installing it

Part of 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.

The honest take

This is a pure reader node, and that's the whole point - it pairs with the Dialogue Duration Planner and Dialogue Line Router to keep the writer nodes clean while exposing their results. The workflow pattern to know: if your tts_text_a/tts_text_b come back empty, check that a planner actually wrote the script layers upstream and that you're reading from the right cine_linx (it's easy to grab the wrong branch in a multigen graph). And if you're running the audio side of a Cine workflow, the woosh_chunks_json output is where your planned sound effects surface - it's easy to overlook, but it's the bridge to whatever generates your foley. One opinion: the report output is underrated documentation for how this pack organizes its state, so glance at it once even if you don't wire it.