-
Notifications
You must be signed in to change notification settings - Fork 27.3k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Feature Request]: "notes" and presets per model when switching Checkpoint, hypernetwork, embedding, etc #5922
Comments
related - #4996 |
I asked for something like this, here - #3522 though yours is a lot more comprehensive. Mine is essentially a little editable note box per model, so you could add the data. |
I would go one step further and introduce the concept of "presets" or "profiles" (or whatever you'd like to call them) which can be selected to auto-configure any number of parameters automatically. I haven't looked at the code (and would need a crash course on Python first), but given that all the controls are already named in |
Notes has been implemented as of recent UI rework in 1.5.0. #7458 (comment) |
Is there an existing issue for this?
What would your feature do ?
It's quite common for the ever growing number of checkpoints, texutal inversions, hypernetworks and etc to have requred keywords or other changes, such as modifications to the UI settings as best practices or results, like clip skip 2, etc
For example, when I select a model like ranmadiffusion , there is an expected keyword: "80sanimestyle" . However, there is nothing in the UI to remind me to do that, and the results will differ from what is expected if you forget.
The same thing exists of course for hypernetworks and embeddings. 2.1 functions significantly better with embeddings, and while It's USUALLY the case that the embedding is named after it's keyword, it's not always.
A shortcut to those as something attached to the model on load, or a reminder for your keywords to activate embeddings would be a much welcome enhancement.
It should be fairly easy to implement too, since it's just a front end ui change that might work a bit like saving prompts as presets.
Proposed workflow
Additional information
No response
The text was updated successfully, but these errors were encountered: