IAMCCS TakePackage
The guardrail that makes multigen 'takes' actually line up
- cine_linx
- cine_linx
- take_package_json
- report
In the IAMCCS Shotboard/multigen system, a "take" isn't just a clip - it's a contract: a specific timeline position tied to a specific audio package, so that when you regenerate take 3 of shot 4, everything downstream knows exactly what it belongs to. Take Package is the node that exposes and validates that identity before anything gets routed.
Its job in the graph is positional and strict. It sits after the multigen bridge (the thing that picks which take you're rendering) and before the router. It pulls the take package out of the cine_linx metadata object, verifies it's a real, complete take with a valid index and timeline, and hard-fails if it isn't - the only strict_mode option is literally called hard_fail, which tells you the author's philosophy: better to stop loudly than to generate 500 frames against a broken identity.
Inputs
- cine_linx - the
IAMCCS_SUPERNODE_LINXmetadata object carrying the take's identity, resources, and payloads. This is the thing the whole Shotboard system threads through the graph instead of discrete wires. - strict_mode - only
hard_failis available. If no valid TakePackage is found, it raises an error rather than proceeding.
Outputs
- cine_linx - the cloned metadata, stamped with
iamccs_take_packageso later nodes can see this step ran. - take_package_json - the take identity as JSON: index, timeline, audio pairing. Wire this into anything that logs or needs the take ID.
- report - a status string describing what was validated.
Install
Ships with IAMCCS-nodes:
cd ComfyUI/custom_nodes
git clone https://github.com/IAMCCS/IAMCCS-nodes.git
or via ComfyUI Manager (search "IAMCCS"), then restart. No models or downloads - it manipulates graph metadata only.
Where it fits (and where it doesn't)
If you're not using the IAMCCS Shotboard multigen pipeline, this node has nothing to do - it demands a valid TakePackage in the linx, and a plain SuperNode graph won't have one, so it'll hard-fail by design. That's not a bug. It exists to enforce the "immutable take identity" discipline that makes multi-timeline/multi-take video projects reproducible: the error message even tells you the fix ("Bridge/TakePicker must provide immutable T/A identity before generation"). So reach for it when you're assembling a multigen Shotboard graph and want a hard checkpoint between the take picker and the backend. If you're hand-building a one-off video, you can skip it entirely.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| cine_linx | IAMCCS_SUPERNODE_LINX | — | |
| strict_mode | COMBO | hard_fail | 1 options: hard_fail |
Outputs (3)
| Name | Type | Description |
|---|---|---|
| cine_linx | IAMCCS_SUPERNODE_LINX | — |
| take_package_json | STRING | — |
| report | STRING | — |