SP_SetPipeModelType

This is a small, specific node, and it only matters if you're already using SP_Pipe. If model/clip/vae bundling isn't part of your workflow, skip it.

What it does

One required sp_pipe input, one model_type dropdown with three choices - none, flux, hunyuan_video - and one sp_pipe output. It takes your existing pipe bundle, stamps a model-type tag onto it, and hands the same bundle back out. Nothing about the model, clip, or VAE inside the pipe changes; this node doesn't touch any of that. It's metadata, not transformation.

Why you'd want that

Flux and Hunyuan Video aren't drop-in replacements for an SDXL-style checkpoint - they have different conditioning requirements, different VAE behavior, different assumptions baked into how a lot of downstream nodes handle them. If other nodes in this pack (or Group Nodes built on top of SP_Pipe) need to branch their behavior depending on which model family is riding inside the bundle, they need some way to know that without inspecting the model object itself. SP_SetPipeModelType is that flag: set it once, right after you build your pipe, and anything downstream that cares can read it off the bundle instead of guessing.

If you're not building anything downstream that actually checks this tag, setting it does nothing observable - which is fine. It's infrastructure for composing more Group Nodes on top of SP_Pipe, not a feature with its own visible effect in an ordinary workflow.

How to use it

Wire it in right after your SP_Pipe assembly, pick the correct entry from the dropdown (none if you're not running Flux or Hunyuan Video, or the matching option if you are), and take the sp_pipe output forward exactly like you would from SP_Pipe itself. It's a pass-through step, so it slots in anywhere in an SP_Pipe chain without disrupting anything else.

Installing it

Ships with the SP-Nodes pack:

• ComfyUI Manager: search "SP-Nodes", install, restart.
• Manual: cd ComfyUI/custom_nodes && git clone https://github.com/bananasss00/ComfyUI-SP-Nodes, restart ComfyUI.

No models or dependencies of its own - it's a tag on a data structure, nothing more.

Troubleshooting

There isn't much that can go wrong with this node in isolation, since it doesn't process anything - the only real gotcha is forgetting it exists. If you've got a Group Node downstream that behaves differently than expected based on model family, and the results look like it's assuming the wrong one, check whether an SP_SetPipeModelType node is actually in the chain before that point, and whether it's set to the value you think it is. Since the dropdown defaults matter here and there's no tooltip on the widget to remind you which is selected, it's easy to leave it on none by accident after copy-pasting nodes between workflows.