Nodes/SeargeSDXL/Parameter Processor
ComfyUI Node Runs on cloud

Parameter Processor

The node that turns Searge inputs into parameters

By SeargeDP·Created 3 years ago·Updated 2 years ago· 874
Parameter Processor
  • inputs
  • parameters

Parameter Processor is the hinge in the middle of the old Searge workflow. All those input nodes on one side collect your settings into a bundle; all those output nodes on the other side read individual values back out. This node is what sits between them - it takes the assembled bundle, does the actual processing, and produces the finished parameter set everything downstream consumes.

It's from SeargeSDXL, the SDXL base-and-refiner workflow pack Searge released when SDXL 1.0 landed in 2023. The node lives in Searge/_deprecated_/UI - the v4.x rewrite replaced this whole bundle-and-process design with a data stream - but understanding it is the key to understanding how the classic Searge graph is wired.

How it works

The Searge input nodes (Prompts, Advanced Parameters, Model Names, and the rest) each add their slice of settings to a growing PARAMETER_INPUTS bundle, chained node to node. That bundle is raw - just your choices. This processor is where those choices become usable: it's where the prompt-style recipe actually combines your main/secondary/style prompts, where the numbers get normalized, where the settings turn into the PARAMETERS object the output nodes can unpack.

Think of it as the "compile" step. Inputs go in as a loose spec; parameters come out ready to drive the sampler, the model loaders, the save nodes. Everything before it is configuration; everything after it is execution.

The input and output

It's a one-in, one-out node, which fits its role:

  • inputs (PARAMETER_INPUTS) - the fully assembled bundle from the end of the input chain. Required.
  • parameters (PARAMETERS) - the processed result, wired into the output nodes (SeargeOutput1, Output2, and friends) that fan it back out into individual typed values.

There's nothing for a beginner to set here - it has no tunable fields. Its job is transformation, not configuration.

How to install it

ComfyUI Manager: search SeargeSDXL, install, restart. Manual: cd ComfyUI/custom_nodes && git clone https://github.com/SeargeDP/SeargeSDXL.git, then restart. If you install by hand, run python -m pip install opencv-python in ComfyUI's Python environment first - the README requires OpenCV or the pack won't load. This node needs no models itself; it only processes settings.

Common issues

Because this is where prompt combination happens, weird prompt behavior sometimes looks like it originates here - but it doesn't. If your style prompt is ignored or a prompt seems mis-weighted, the cause is upstream: the prompt style you picked in Misc Parameters and the powers you set in Prompt Processing. This node just executes whatever recipe those chose.

The realistic gotcha is version drift. This processor and the exact shape of the PARAMETERS object evolved across Searge versions, so an old workflow JSON feeding a newer node (or vice versa) can throw type errors right around here. The fix is the same as always: load the latest workflow JSON with the latest custom-node version.

Bigger picture - this is a deprecated internal node you never place by hand; it comes as part of the workflow. And the workflow itself is a refiner-era artifact from a time before the community settled on single fine-tuned SDXL checkpoints. It still runs, but you're looking at the plumbing of a historical setup.

CategorySearge/_deprecated_/UI

Inputs (1)

NameTypeDefaultDescription
inputsPARAMETER_INPUTS

Outputs (1)

NameTypeDescription
parametersPARAMETERS