You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What I would love to see is an extension that creates a metadata file next to each model.
That we could store the:
Title
Description
Recommended Weight
Trigger Phrase - prompt to go with the model
URL
Example Prompt
And display Model Info
Then when you mouse over the model you would see a description. Clicking on the model would put not only the model tag, but also the recommended weight value and the trigger phrase.
For example, if I clicked on a Mazda Miata LoRA, rather than just adding <lora:Mazda Miata:1> to the prompt,
it would put <lora:Mazda Miata:0.6>, MazdaMiata, 1car
Using my preset weight and tags with the model.
The only needed Icons on the card would be an edit icon and an insert without the trigger phrase icon.
Clicking the model would add the model with the set weight and trigger phrase.
Example: <lora:GI Landscape 2:0.8>, Render of a {prompt} in Mondstat, CG, Unreal Render
Clicking the no-tag icon would add the model without the trigger phrase
Example: <lora:GI Landscape 2:0.8>
Clicking the gear would open the edit box.
Here is a mockup edit box.
The metadata files should be universal, such as JSON or XML. Easy to edit manually. But there should also be an edit icon in the UI on the model to edit the fields.
Additionally, it would be nice to have it scrape starting metadata from sites like Civitai to pull the initial values, which could then be modified.
I find the default weight of 1 and recommended trigger words are almost never enough on their own to get a good result. I have been manually adding every single LoRA, TI, and Hyper to my Styles CSV list to have it fill in the best weight, and trigger phrase combo. This works but is annoying as it requires me to double my efforts. It would be great to be able to specify the values that I want for each model.
Here is a fork of the civitai extension that is trying to add some of this functionality.
Thanks for working on this idea.
There are quite a few bugs on the alpha version, but its a good start.
Here is a post I made on AUTOMATIC1111/stable-diffusion-webui#7458 with a mockup:
What I would love to see is an extension that creates a metadata file next to each model.
That we could store the:
Then when you mouse over the model you would see a description. Clicking on the model would put not only the model tag, but also the recommended weight value and the trigger phrase.
For example, if I clicked on a Mazda Miata LoRA, rather than just adding
<lora:Mazda Miata:1>
to the prompt,it would put
<lora:Mazda Miata:0.6>, MazdaMiata, 1car
Using my preset weight and tags with the model.
The only needed Icons on the card would be an edit icon and an insert without the trigger phrase icon.
Clicking the model would add the model with the set weight and trigger phrase.
Example:
<lora:GI Landscape 2:0.8>, Render of a {prompt} in Mondstat, CG, Unreal Render
Clicking the no-tag icon would add the model without the trigger phrase
Example:
<lora:GI Landscape 2:0.8>
Clicking the gear would open the edit box.
Here is a mockup edit box.
The metadata files should be universal, such as JSON or XML. Easy to edit manually. But there should also be an edit icon in the UI on the model to edit the fields.
Additionally, it would be nice to have it scrape starting metadata from sites like Civitai to pull the initial values, which could then be modified.
I find the default weight of 1 and recommended trigger words are almost never enough on their own to get a good result. I have been manually adding every single LoRA, TI, and Hyper to my Styles CSV list to have it fill in the best weight, and trigger phrase combo. This works but is annoying as it requires me to double my efforts. It would be great to be able to specify the values that I want for each model.
Here is a fork of the civitai extension that is trying to add some of this functionality.
butaixianran#36 (comment)
The text was updated successfully, but these errors were encountered: