Sd1.5 and Chroma - low hanging fruits and very easy to add

[entropy010]

Hello,

I looked at the code and checked out the changes from the initial commit.
Unfortunately the structure becomes a bit unwieldy with a lot of if/elif/or... statements intermingled. It's hard to implement additional model architectures I guess. My guess is that you try to catch every form of possible misconfiguration by the user.

But I just wanted to mention 2 models that are extremely easy to implement.

• SD1.5: it's literally in the SDXL code 1:1 and nothing has to change extept that you can write SD.15 / SDXL in the dropdown description.
• Chroma: It's just Flux with negative prompt and model guidance set to 0. Simply adding a negative prompt in the helpers.py API json structure, replacing Basic Guider with CFG Guider and exposing FluxGuidance to 0 should do the trick. If CFG is set to 1 negative prompts have no impact whatsoever anyways.

Or would a Chroma dropdown and piggybacking Chroma through the 'flux1' model_architecture into a custom Chroma API workflow json be possible? Anyways the model is 99% Flux but infinitely more powerful than Flux.

Anyways superb Addon.

[sakalond]

Yes, that should be possible.

SD1.5 already works as far as I know, so it would be only a matter of actually telling the user that it does. Will add that.

Chroma should be possible. Only reason I didn't add it yet was that there was no depth guidance option for Chroma specifically. But I guess Flux cn / LoRAs could work in theory? I frankly just don't really care about Flux and derivatives that much anymore since it has the proprietary license and Qwen exists. However, I guess it should be easy to add, so I will consider it.

[sakalond]

Also, yes, the code is a bit messy at this point. I would probably like to refactor it at some point to increase readability, but I don't have that much time at the moment, so I will see when I get to it as functionality-wise it isn't a top priority.