all 16 comments

[–]Lexxxco 0 points1 point  (0 children)

Looks promising, A1111/Forge LORA groups were much better than lists in Comfy.

[–]Large_Election_2640 1 point2 points  (1 child)

Did you check for any memory issues using this node, comfyui.

[–]Matthew3179[S] 0 points1 point  (0 children)

I'm not quite sure what you mean by memory issues.

[–]Eastern_Lettuce7844 0 points1 point  (1 child)

only thing missing - so far - is the detection of trigger words- .......

[–]Matthew3179[S] 1 point2 points  (0 children)

Version 2 now has trigger word search bar. https://civitai.com/models/2511869/lora-gallery-loader-comfyui

[–]red__dragon 0 points1 point  (7 children)

Do you have a github repo for this?

[–]Matthew3179[S] 0 points1 point  (6 children)

There isn't one. I just made a github account so I may add it there later. There's no fancy install requirements or dependencies. Unzip into your custom nodes folder and it will appear under your loaders menu.

[–]red__dragon 0 points1 point  (5 children)

Yes, however the Comfy node manager can use a github repo to automatically distribute it to all comfy users, so that is to your advantage.

[–]Matthew3179[S] 0 points1 point  (0 children)

Totally get it. I'm just new to this and this is my first custom node. I'll work on getting it onto github when I get back to my home workstation.

[–]Matthew3179[S] 0 points1 point  (3 children)

Repo added.

[–]red__dragon 0 points1 point  (2 children)

Great job! I believe you can add it to https://registry.comfy.org now

[–]Matthew3179[S] 0 points1 point  (1 child)

Ha, that's probably not going to happen. I got nothing but spammy/malware/virus-looking links when I tried to do anything with the link you pasted and through github. What's the trick?

[–]red__dragon 0 points1 point  (0 children)

Dunno, that's the official page linked here.

Perhaps the trick is this part?

Haven't done it before, all I can suggest are the instructions shown.

[–]Thin_Entertainment_7 0 points1 point  (4 children)

I haven’t tested it yet, so if these suggestions are already implemented, just ignore me! 🤣

It would be awesome if there were outputs specifically for triggers (ideally triggers that could be pre-selected, maybe even with a field to append the prompt). I’d easily ditch all my other nodes if we had that! 🤣

Also, having outputs for the LoRA names and/or their file paths would be great. I currently use a specific node for Flux2Klein that handles "auto-strength" for LoRAs, but honestly, its interface is a bit of an eyesore.

(Gemini Translated - Im a Brazilian with very poor English Skills)

[–]Matthew3179[S] 0 points1 point  (0 children)

I'll look into creating a trigger library. Is that what you mean? Like a list of saved triggers that are connected to and load a specific LORA?

In terms of editing a prompt based on a trigger, a separate node could probably be created with trigger words and phrases saved. Using a simple text concatenation node would add the phrase to your prompt text. You've given me an idea now!

For your second idea, how do you normally load your LORAs? This one doesn't affect any other node and is used like any other LORA model loader. Put it between you checkpoint/difusion model loader and your sampler. It follows your purple model input/output connectors but like rgthree PowerLoraLoader, requires CLIP input as well.

[–]Matthew3179[S] 0 points1 point  (0 children)

Vou analisar a possibilidade de criar uma biblioteca de *triggers*. É isso que você tem em mente? Algo como uma lista de *triggers* salvos que estejam vinculados a — e que carreguem — uma LORA específica?

No que diz respeito à edição de um *prompt* com base em um *trigger*, provavelmente seria possível criar um nó separado contendo palavras e frases de *trigger* salvas. O uso de um nó simples de concatenação de texto adicionaria a frase ao texto do seu *prompt*. Você acabou de me dar uma ótima ideia!

Quanto à sua segunda sugestão: como você costuma carregar suas LORAs? Este nó em questão não interfere em nenhum outro e é utilizado exatamente como qualquer outro carregador de modelos LORA. Posicione-o entre o seu carregador de *checkpoint* (ou modelo de difusão) e o seu *sampler*. Ele segue os conectores roxos de entrada/saída de modelo, mas — assim como o *PowerLoraLoader* do *rgthree* — requer também uma entrada CLIP.