IAMCCS Cine Shotboard Planner Pro Legacy Outputs

Here's a node that exists for one reason: older workflows. When IAMCCS upgraded Shotboard Planner Pro, they moved it to a single cine_linx output - clean, but it broke every hand-wired graph that expected the planner to expose its internals as separate sockets. Cine Shotboard Planner Pro Legacy Outputs is the compatibility clone that keeps those old direct outputs alive.

If you're starting fresh, you almost certainly want the regular Planner Pro instead. If you've got an existing FLFreal/PromptRelay graph that was built before the LINX contract took over, this node is how you keep it running without a rewrite. The docstring doesn't mince words: it's a "compatibility clone of Shotboard Planner Pro with classic direct outputs... Keep this clone for older hand-wired FLFreal/PromptRelay workflows that still expect direct sockets from the planner."

What you get that Pro doesn't. All the same inputs (global_prompt, timeline_data, duration_seconds, frame_rate, guide_policy, min_guide_gap_seconds, max_guides, default_force, promptrelay_epsilon, ltx_round_mode, the image controls) - but instead of just cine_linx, the outputs are the classic spread:

• flf_timeline, global_prompt, local_prompts, segment_lengths - the string bundles your old FLFreal and PromptRelay nodes want to chew on.
• max_frames (INT) and promptrelay_epsilon (FLOAT) - the numbers those nodes need for timing.
• multi_output and image_1 (IMAGE) - the processed reference image(s) the guide path expects.
• duration_seconds_int and frame_rate_int - the plan's duration and rate as integers, handy for feeding EmptyLatent-type nodes.
• width and height - the resolved canvas size.
• report (STRING) - a JSON dump of what the planner decided, for debugging.
• cine_linx - and yes, it's still there at the end, so you can use this node as a bridge into newer backends too.

The mechanism underneath is identical to Planner Pro: rows in timeline_data become timed guide frames and per-segment local prompts, and the node outputs everything in the flat format instead of wrapping it. That's the entire difference.

Install. Same as the pack: ComfyUI Manager (search "IAMCCS"), or git clone https://github.com/IAMCCS/IAMCCS-nodes into custom_nodes, then restart. ComfyUI ≥ 0.3.0, Python ≥ 3.12, no extra model downloads - the planning happens in the node, the generation happens downstream.

The honest gotcha. This node is a bridge, not a destination. The pack keeps it around so old graphs load, but every new backend in the pack speaks cine_linx. If you're building something new, prefer the modern planner and feed its cine_linx into the backend - you get the same plan without juggling nine sockets. Use Legacy to keep your existing graphs alive, and don't expect it to gain features. Also remember the shared house rule: keep the pack updated, and if a saved workflow loads with widgets in the wrong slots after an update, delete and re-add the node rather than fighting it.