Feature: Better LoRA management

[moonwhaler]

This might be a bigger one: I work with LoRAs a lot (maybe others do too). I have collected hundreds of LoRAs over the last months.

The current implementation of the LoRA management is straightforward, but very limited in terms of UX.

I would love to have some sort of browser (with preview images grabbed (manually) from e.g. Civitai.com and some sort of automatic trigger word implementation.

I use Civitai.com Browser+ for Forge to collect this information (which places a text file and a preview image next to the LoRA (or model checkpoint) with the same filename).

This might not be high on any list, but it would make life a lot easier.

Thank you.

[rktvr]

agreed

[Acly]

Note that trigger words are supported in general:

Picking them up from text files: this is a bit complicated because the plugin doesn't scan folders (and they might be on some remote server). Lora files are reported by ComfyUI. So first support for the text files and exposing them would have to be implemented there (can be done as a custom node).

Preview image: that would be a lot of work and not very useful for most people without also implementing a way to grab those images from civitai. I'm probably too rigorous with deleting crappy Lora to ever feel motivated enough tbh

[moonwhaler]

Thanks for the info. I already looked at the code and saw you're refreshing the LoRA list when starting the plugin and save it locally. One could theoretical make an API call to an meta data provider at refresh time, which would certainly impact startup time. As I said, it's more of a nice to have feature for me.

What I noticed is that refreshing the LoRA or model list after the plugin started (using the settings dialog) takes a huge amount of time when comparing the same process at startup time. Sometimes it takes up to 60-100 seconds for a complete refresh, when having 500+ LoRAs on the server side (locally).

Maybe I open an issue.

[Acly]

Might also be related to checkpoints if you have a lot of those (they are always refreshed together, even though there are separate buttons).

[moonwhaler]

After a bit more digging I started writing a little "CivitAI" scraper myself, which is also able to sync trigger/activation words directly to the "loras.json".

"metadata": { "lora_triggers": "word1, word2" }

So yeah. Getting this included into Krita AI Difusion seems overkill.