IP Adapter Single Settings Pipe (JPS)
Unpack the older weight-type variant
- ip_adapter_settings
- ipa_weight
- ipa_wtype
- ipa_noise
- ipa_start
- ipa_stop
- ipa_crop
- ipa_zoom
- ipa_offset_x
- ipa_offset_y
- ipa_mask
- crop_intpol
- sharpening
- ipa_model
Unpacks the bundle from IP Adapter Single Settings (JPS) - the version of this pack's single-adapter tuning menu built around the older three-option weight-type vocabulary (original, linear, channel penalty) rather than the newer nine-option list its sibling uses.
What comes out of it
One input, ip_adapter_settings - a BASIC_PIPE (JPS's own bundle, a plain tuple, not Impact Pack's object of the same type name). Thirteen outputs, matching its sibling pipe field-for-field except one:
ipa_weight(FLOAT) - overall adapter strength.ipa_wtype- original, linear, or channel penalty. This is the one field that differs from IP Adapter Settings Pipe (JPS)'s output - a shorter, older option list for the same underlying weight-distribution concept.ipa_noise(FLOAT),ipa_start/ipa_stop(FLOAT) - reference-embedding noise and the active step window.ipa_crop,ipa_zoom(FLOAT),ipa_offset_x/ipa_offset_y(INT) - reference-image framing.ipa_mask(INT) - which of six mask modes constrains where the adapter applies.crop_intpol,sharpening(FLOAT) - resize algorithm and post-crop sharpen.ipa_model(INT) - which SDXL IP-Adapter variant.
No adapter logic runs here - pure routing to whatever ComfyUI_IPAdapter_plus apply node is doing the actual work.
If you're starting a workflow fresh rather than maintaining one that already uses this three-option scheme, it's worth pausing here: IP Adapter Settings Pipe (JPS) and its matching Settings node use a newer, more descriptive nine-option ipa_wtype list, and there's no real downside to reaching for that pair instead unless something specific in your graph depends on "channel penalty" behavior. This pair earns its keep specifically for compatibility with older workflows built around the original three-option vocabulary.
Installing it
Ships with the pack. ComfyUI Manager: search JPS Custom Nodes for ComfyUI, install, restart. Manual:
cd ComfyUI/custom_nodes
git clone https://github.com/JPS-GER/ComfyUI_JPS-Nodes.git
Restart afterward, deleting any earlier copy of the pack first. No models bundled - install ComfyUI_IPAdapter_plus separately for the apply node and the SDXL IP-Adapter weights themselves.
Where people get tripped up
Without an IP Adapter Single Settings (JPS) node upstream, this pipe has nothing to unpack.
This node's input is named ip_adapter_settings - the identical name and type used by IP Adapter Settings Pipe (JPS)'s input, even though the two Settings nodes feeding them pack a genuinely different ipa_wtype field (three options here versus nine on the sibling). BASIC_PIPE isn't validated field-by-field by ComfyUI, so wiring the wrong Settings node into this pipe will connect cleanly in the UI and just produce a wrong or meaningless weight-type value once it reaches your apply node. If "channel penalty" or "original" don't show up as options where you expect, or the weight-type behavior seems off, double-check this pipe is actually fed by IP Adapter Single Settings (JPS) and not its newer-vocabulary sibling - a real, documented point of confusion for this option list even among people who use it regularly, so it's worth ruling out a wiring mismatch before assuming you've misunderstood the setting itself.
Inputs (1)
| Name | Type | Default | Description |
|---|---|---|---|
| ip_adapter_settings | BASIC_PIPE | — |
Outputs (13)
| Name | Type | Description |
|---|---|---|
| ipa_weight | FLOAT | — |
| ipa_wtype | original,linear,channel penalty | — |
| ipa_noise | FLOAT | — |
| ipa_start | FLOAT | — |
| ipa_stop | FLOAT | — |
| ipa_crop | center,top,bottom,left,right | — |
| ipa_zoom | FLOAT | — |
| ipa_offset_x | INT | — |
| ipa_offset_y | INT | — |
| ipa_mask | INT | — |
| crop_intpol | lanczos,nearest,bilinear,bicubic,area,nearest-exact | — |
| sharpening | FLOAT | — |
| ipa_model | INT | — |