VRGDG_PromptSplitter4
The four-scene splitter, for when a section is exactly four beats
- text_output_1
- text_output_2
- text_output_3
- text_output_4
VRGDG_PromptSplitter4 is the four-output member of VRGameDevGirl's splitter family: JSON in, four scene prompts out. Same DNA as the rest of the pack's splitters, just cut for a section that always has exactly four chunks.
If you've seen VRGDG_PromptSplitter2, you already know this node - it's the same fixed-output pattern with twice the ports. That's the design philosophy across this whole family: instead of one adaptive splitter that scales to any scene count, the pack ships a handful of fixed-count variants so each section of the music video workflow gets exactly the ports it needs, no more, no less.
How it works
One required input:
json_string- the prompt-map JSON as text (defaults to{}). Paste it or wire it from an upstream node like the pack'sVRGDG_PromptMapJsonFixer.
Outputs: text_output_1 through text_output_4, all STRING. Wire each into its scene's video-generation chain. Like the other fixed splitters, the node reads the JSON and fills the ports it can; extra prompts beyond four simply aren't surfaced here.
Why fixed counts
The rationale shows up the moment you look at a shipped workflow: ComfyUI graphs get noisy fast, and a splitter with 50 output ports sitting next to a sampler that needs 4 creates visual noise and accidental mis-wiring. Fixed-count splitters keep each section's graph readable and make the wiring self-documenting - four ports, four scenes, obvious. The cost is that you need the right variant for the job, which is why the pack ships so many.
Installing it
Same pack, same install:
cd ComfyUI/custom_nodes
git clone https://github.com/vrgamegirl19/comfyui-vrgamedevgirl
restart, or ComfyUI Manager → search vrgamedev. No models, no special dependencies.
The honest take
You'll probably never add this node to a graph you built yourself - but you'll meet it constantly if you open the pack's workflows, and understanding that it's just "the four-output splitter" is all you need. Don't fight the family; pick the variant the workflow already uses and move on.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| json_string | STRING | {} | — |
Outputs (4)
| Name | Type | Description |
|---|---|---|
| text_output_1 | STRING | — |
| text_output_2 | STRING | — |
| text_output_3 | STRING | — |
| text_output_4 | STRING | — |