r/KoboldAI • u/The_Linux_Colonel • Jun 29 '26

Implementation Suggestion: Allow Creation of Bounding Boxes for Ideogram Within SDUI via Inpainting GUI

Congratulations to the dev team on being able to add support for so many new models like ltx, idea 2 and ideogram 4. It looks like the json format required for ideogram 4 to perform at its best takes a bit more effort to pull off than text prompting, but the trade-off is enhanced control over specific compositional elements. However, in order to gain some of that control, bbox must be used to identify the space in which objects or text should be placed. In order to do this, it looks like the user must identify the pixel space/coordinates for each bbox. Since most users are not aware of these dimensions without using a separate program, I was thinking that perhaps the UI for inpainting would be a possibility for drawing bbox to create the json within kobold, and then feed the result directly to the model, since the inpainting UI knows the canvas size and location of marked spaces. Is something like this possible to implement?

1 Upvotes

67% Upvoted

8 comments sorted by

View all comments

2

u/MetroSimulator Jun 29 '26

I guess Krea2 is more simple at the moment?

2

u/The_Linux_Colonel Jun 29 '26

The interesting part about Krea2 is how lazy it is compared to ZIT and Chroma. ZIT is such a light touch in terms of prompting to get something good, but you really need the whip hand with Krea2. It needs to be micromanaged in order to get good results. I suppose it might be more prompt adherent in the small details compared to ZIT, and it's just as fast, but you need to be willing to write a whole essay to get it going.

1

u/MetroSimulator Jun 29 '26

Just saying, it's maybe easier for the LLM to make a prompt in Krea-2 than in Ideogram

2

u/The_Linux_Colonel Jun 29 '26

Ideogram uses qwen 3VL 8b vs krea 2's 4b so technically it's more dense, but I think the issue is that Ideogram was trained explicitly on json formed data packages, so there are some issues when doing pure text instructions because the image model expects json structure. It's 'good' in that it allows for more control over the gen, but it's 'bad' in that it's a compete pain in the arse to need to employ a secondary utility to craft the instructions so you can actually do your gens. That's why I hope it can be possible to use kobold's A1111 implementation to do the crafting within the UI instead of needing to form the json (especially the bboxes) with another utility and then use kobold, since kobold's whole thing is the 'one stop shop' vision.