There is a suggestion for VAE documentation, which I agree with, but I would go further and ask for built-in fields for all generation criteria where the model's creator can share what they think the ideal parameters are. (Basically, what we already have for trigger words, but for non-prompt parameters.) Many creators already do this in their description text, and there are informal attempts to standardize a format, but this is definitely inefficient. Having (optional) built-in fields for this information will encourage creators to supply it in the first place when they might not think to do so otherwise (or think more about their model's performance in the first place), and making it API-friendly will greatly empower model preset managers, making models easier to use across the board. I am not personally a software developer and wouldn't directly use this API feature, but I do have a lot of checkpoints and LoRAs, and having to check back with the page on Civitai every time I need to remind myself if this is a low or high CFG checkpoint is a pain. I've looked at a number of solutions, but all the Auto1111 extensions are strung up by the fact that this data isn't easily accessible in a systematic way, even when it is available. As AI art software becomes more accessible and streamlined, I think convenient preset management will become standard, and this seems like low hanging fruit that will help the entire AI art community.
Please authenticate to join the conversation.
Awaiting Dev Review
π‘ Feature Request
Over 2 years ago
A1322
Get notified by email when there are changes.
Awaiting Dev Review
π‘ Feature Request
Over 2 years ago
A1322
Get notified by email when there are changes.