Krea2 Two Style References
Krea2 Two Style References
- reference_latent_1
- reference_latent_2
- style_refs
- debug
What it is
A small connector node with exactly one job: take two already-prepared style reference latents and bundle them into the single package that Krea2 Two Style Transfer needs to run. If you've set up the single-reference workflow already, this is the piece that lets you graduate to two references without the two-reference node needing a wall of new inputs of its own - it just takes one STYLE_REFS bundle instead of two separate latents.
It's also, quietly, where the "two references only" rule in this pack gets enforced. There's no third slot to plug an image into. The author found that three or more references start competing rather than blending - weaker style transfer, quality loss, one reference randomly winning out, results nobody could fully explain - and capped the route at two on purpose rather than exposing a limit users would inevitably push past. This node is that cap, structurally.
How it works
Nothing algorithmic happens here - it's pure plumbing. Each of your two reference images needs to go through its own Krea2 Style Reference node first (VAE-encoded, resized to match your target latent, the whole prep step that node handles), and this node takes the two resulting latents and packages them as style_refs. What does matter is which one you plug into which slot: the order you feed them here is what primary_reference on the downstream Krea2 Two Style Transfer node refers to when it says "1" or "2". Get your reference images backwards here and you'll be selecting the wrong one as primary no matter what you set on the transfer node itself.
Inputs and outputs that matter
Two required inputs, both LATENT: reference_latent_1 and reference_latent_2. Each should be the reference_latent output of a separate Krea2 Style Reference node - one instance per reference image, both built against the same target latent size so they stay compatible with each other and with your generation.
Two outputs: style_refs (type STYLE_REFS) is the one that matters - it plugs directly into Krea2 Two Style Transfer's style_refs input and nowhere else, since it's a custom type unique to this pack. debug is a STRING output for troubleshooting; wire it to Show Text if you want to confirm what got bundled.
Installing it
Ships with the rest of the pack. ComfyUI Manager, search "ComfyUI Krea2 Style Transfer," or manually cd ComfyUI/custom_nodes && git clone https://github.com/jieg9341-lab/ComfyUI-Krea2-StyleTransfer and restart. This node itself doesn't touch the VAE or the Krea2 model - it's just bundling latents that were already built elsewhere - so there's nothing extra to configure for it specifically beyond having a working Krea2 setup for the Krea2 Style Reference nodes feeding into it.
Where people get burned
The most common mix-up is treating this as a merge or an average - it isn't. All it does is package two latents in order; the actual blending logic (and the order-sensitivity that comes with it) lives entirely in Krea2 Two Style Transfer. If your two-reference results feel backwards from what you expected, check the order you plugged references into this node before you start tweaking sliders downstream - swapping reference_latent_1 and reference_latent_2 here has the same effect as flipping primary_reference on the transfer node, and it's an easy thing to get turned around when you're iterating on which image should lead.
And don't go looking for a third input slot. That's not an oversight to route around - it's the pack's own tested conclusion that two is where this technique stops working cleanly.
Inputs (2)
| Name | Type | Default | Description |
|---|---|---|---|
| reference_latent_1 | LATENT | — | |
| reference_latent_2 | LATENT | — |
Outputs (2)
| Name | Type | Description |
|---|---|---|
| style_refs | STYLE_REFS | — |
| debug | STRING | — |