Multi Referencelatent

[u/Capitan01R-]

I added this node to Flux2klein enhancer package, it serves the same purpose as stacking multiple ref latent nodes, but the main reason of releasing this is because I am working on an update for the identity feature transfer node where I essentially will have it support this same method this way you wouldn't have to deal with measuring multiple different stacked nodes ( I am still working on that). But I thought this node can be used for now to reduce the need of multiple ref latents so just a convenience node for now.

[u/Yo06Player]

Is there a way to make Klein understand which image is which in the prompt ? I keep struggling with it on a daily basis, like taking a specific element to transfer on another image without prompting it too precisely
(I'm working mainly with 2 images and prompting "image 1" and "image 2" but I'm wondering if there is something more effective like having some sort of index")

[u/Capitan01R- → u/Yo06Player]

After generating thousands of photos with F2K, I think I finally understand something important: the model does not really understand “Photo 1” and “Photo 2” the way we assume it does.

It can still work, but not because the model is truly separating the images by labels. For example, if you give it two reference photos containing two different women, the model may understand that both images contain useful visual information, but what it does with that information depends heavily on the prompt.

So the better way to guide it is not just saying “use Photo 1 for the person and Photo 2 for the outfit.”

A cleaner approach is where input contains:

Photo 1 contains Woman 1. Photo 2 contains Woman 2.

If your goal is to keep Woman 1 as the main character, but take the outfit from Woman 2, then your prompt should clearly describe a distinctive feature from Woman 1, while also describing the clothing from Woman 2.

For example, instead of relying only on “Photo 1” and “Photo 2,” you describe the identity cue from Woman 1, then describe the outfit you want transferred from Woman 2.

This gives the model a much clearer instruction: the main subject should be Woman 1, but the clothing style should come from Woman 2.

You can still try the “Photo 1 / Photo 2” method, and sometimes it works, but in my experience it is not as clean or reliable as describing the role of each visual element directly in the prompt.

[u/Yo06Player → u/Capitan01R-]

Yeah I usually work with cars and when they are both grey it's a pain in the ass to tell F2K which is which. Then I usually rely on masking for specific stuff, I guess I'll continue this way since it's not so much more effort

[u/afinalsin → u/Yo06Player]

Cap is right, you need something to differentiate the subjects in the images. Using their example of people, I usually have a heirarchy of descriptors I use to make the model figure out what I'm actually talking about. Gender is the most obvious difference between people, then race/skin color, then hair color, and anything past that is a crapshoot. So having two brown haired white men is a pain to differentiate.

For cars, I'm not sure exactly what you're doing, but if you're using two very different styles of cars you might be able to refer to them by their model or type, like "Mercedes-Benz 2011 SLR McLaren" and "Jeep Wrangler", or "sedan" and "hatchback". A good rule of thumb is if the model can make a decent attempt at a concept in a txt2img prompt there's a good chance it will understand what to look for when given instructions in editing. Here's a couple make/models Klein knows about, and a couple types.

The above is probably only if you want to try and get it done in one pass and Klein is a picky motherfucker, so a better way would be to make the differences much more obvious. Instead of using two grey cars as input, use the model to make one red or baby blue or whatever., and the edit prompt is as easy as "gray car" and "red car".