MiniMax H3 Shotboard Settings → CineLinX

The IAMCCS_MiniMaxH3ShotPlanner (the Shotboard) has so many widgets that splitting the config from the planning is the obvious quality-of-life move. IAMCCS_ShotboardH3Settings is that split: it's the same settings surface as the Shotboard - same contracts, same option lists - but its only job is to package them into one cine_linx output that the Shotboard (or another consumer) can read. You can't get a cleaner separation of "configure once" from "plan each shot."

How it works

Rather than maintaining a second fragile widget schema, the node literally borrows the Shotboard's input definitions (IAMCCS_MiniMaxH3ShotPlanner.INPUT_TYPES()), groups them by category, and re-exposes them with display names like 08 · ADVANCED COMPATIBILITY · ltx round mode. That means every future option the Shotboard gains - samplers, installed LoRAs, new presets - appears here automatically. It also strips the control_after_generate auto-seed behavior, because this is a persisted configuration source, not a sampler; the Shotboard keeps the single seed control.

Practically, you get the full set of Shotboard knobs here: duration_seconds, width/height (and the image-reference variants image_width/image_height with their resize method), guide_policy, default_force, promptrelay_epsilon, ltx_round_mode, and the rest of the H3 settings groups. You set them once, wire the cine_linx output into the Shotboard's cine_linx input, and the shot inherits them.

Outputs

A single output: cine_linx, carrying the settings payload under an iamccs_minimax_h3_settings schema with schema_version: 1. The node's policy strings make the priority explicit: minimax_h3_settings_source: IAMCCS_ShotboardH3Settings and minimax_h3_settings_priority: external_cine_linx_over_local_snapshot - i.e. when both an external settings CineLinX and the Shotboard's own widgets are present, the external config wins. That's the whole contract in two lines: this node is meant to be the authority, so don't fight it by also hand-editing the same fields in the Shotboard.

Why you'd bother

Two workflows make it worth it. First, presets: build two or three of these as saved config sources (a "hero quality" one, a "low VRAM draft" one) and switch between them by rewiring a single connection instead of scrolling fifty widgets. Second, consistency across many shots: if you always render the same canvas size, guide policy and round mode, locking them here removes a whole class of "one segment rendered at the wrong resolution" accidents.

Ships with IAMCCS-nodes: ComfyUI Manager → search "IAMCCS", or cd ComfyUI/custom_nodes && git clone https://github.com/IAMCCS/IAMCCS-nodes.git, then restart. No extra models or dependencies beyond the pack.