IAMCCS Cine Workflow Inspector

There's a specific failure mode that long ComfyUI video runs share: you queue a 30-minute generation, walk away, and come back to find it produced garbage because you forgot to connect the reference images. The Cine Workflow Inspector is IAMCCS's answer to that - a validator that looks at your cine graph's settings and tells you, before you queue, what's going to bite you.

It's not a magic detector. It's a linter for the pack's own workflow conventions, and it knows four of them well: single_generation_flf, single_generation_promptrelay, multigen_indexed, and v2v_timeline.

How it works

Pick a workflow_mode, fill in duration_seconds, frame_rate, and reference_count, and the inspector checks the obvious things:

• Image-guided modes with reference_count at 0 get flagged - no references, no point running.
• PromptRelay mode requires promptrelay_segment_lengths; if it's empty, it tells you to connect the Cine PromptRelay Timeline output.
• If you pasted timeline_data JSON, it validates that it parses and isn't an empty keyframe/segment list.
• When segment lengths are present, it sums them and compares against total frames - a mismatch over ~8 frames gets a hint, because your segments and your duration silently disagree.
• It also has opinions: for multigen_indexed it suggests one generation per shot with concatenation for hard cuts, and for v2v_timeline it reminds you that video-to-video shines when the source already has motion or audio.

You get back a BOOLEAN ok and a STRING report with the human-readable verdict. Wire ok into a conditional if you want the graph to literally refuse to continue, or just read the report and fix things.

The inputs that matter

For a beginner, only three are worth touching:

• workflow_mode - the shape of your pipeline. Match it to what you actually built.
• reference_count - how many reference images your graph loads. This is the one people forget and the inspector's most useful catch.
• duration_seconds and frame_rate - what the inspector uses to compute expected frames.

timeline_data, promptrelay_segment_lengths, and plan_json are optional paste-ins for the modes that use them; leave them empty and the inspector simply skips those checks.

Install

It ships inside IAMCCS-nodes, so install is the pack install:

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

Or search "IAMCCS" in ComfyUI Manager. No extra dependencies; restart after install.

Gotchas

This is advisory. A passing ok doesn't mean your graph will look good - it means the bookkeeping checks out. And like a lot of this pack, the naming assumes you know IAMCCS's internal vocabulary (FLF, PromptRelay, multigen). If those terms are new, the inspector doubles as documentation: the report text essentially teaches you what each workflow mode expects.