Scene Maker Result - pipe(TJ)

The boring node that makes Scene Maker usable

Scene Maker (TJ) returns seven outputs, which is a lot of wires to drag across a graph if you're using its results more than a few nodes away. This node exists to fix exactly that: it takes Scene Maker's single TJ_SCENE_PIPE bundle and unpacks it into six named text outputs right where you need them. There's no LLM inside, no model loading, no thinking - it's a pure unpack-and-display node, and it's an output node, so it also shows you all the scene values on the canvas at once.

If you've ever built a workflow where the prompt composer sits at the top-left and the KSampler sits at the bottom-right, you know the pain it's removing: a tangle of six multi-line text wires crossing the entire graph, impossible to follow, impossible to keep tidy. With the pipe pattern, Scene Maker hands one wire to this node and you place the Result Pipe next to whatever actually consumes the prompts.

What it does

One input, pipe (type TJ_SCENE_PIPE), plugged straight into Scene Maker's pipe output. The node splits it back into:

• Scene brief
• Visual Beat
• Visual anchor
• Scene prompt
• Scene prompt line (a list - wire this into a batch or per-shot consumer)
• Translated result

It's an output node, so it renders the values in its UI when the workflow runs - handy for eyeballing what the LLM actually produced before you commit to generating from it.

Where it fits in a real workflow

The pairing is simple and it's the intended usage: Scene Maker → this node → your CLIP/KSampler chain. Because Scene prompt line comes out as a list, you can fan it into a batch workflow (TJ_NODE has Batch to Multi Image Output and friends for exactly this) and generate one image per shot without hand-joining text.

You don't need the Result Pipe if you're using Scene Maker's outputs right next to the node itself - its own slots are right there. Reach for it the moment the scene outputs have to travel, or when you want one readable spot that shows the whole storyboard. It also plays nicely with the pack's wireless philosophy: since the pipe is a single typed socket, you can pass it through a Set/Get wireless hop instead of routing six strings, and unpack here.

Install and gotchas

No extra dependencies - it's part of the TJ_NODE pack. Install the pack (Manager → search TJ_NODE, or git clone https://github.com/designloves2/ComfyUI-TJ_NODE.git into custom_nodes/), restart ComfyUI, and the node appears under ✨ TJ_Node/LLM.

The one real trap: if you connect this to a pipe from anything other than Scene Maker, it'll silently render empty values - the pipe type is just a dict under the hood, and this node reads the scene_brief, visual_beat, etc. keys. No error, just blanks. And since it's a strict pipe-type input, ComfyUI will also refuse a plain string where the pipe goes, which is the actual symptom people hit first. Feed it a genuine Scene Maker output and it just works.