[Community Pipeline] Wildcards

Intro

Community Pipelines are introduced in diffusers==0.4.0 with the idea of allowing the community to quickly add, integrate, and share their custom pipelines on top of diffusers.

You can find a guide about Community Pipelines here. You can also find all the community examples under examples/community/. If you have questions about the Community Pipelines feature, please head to the parent issue.

Idea: Wildcards

Wildcards is an idea from @jtkelm2 for Automatic1111 Web UI. This is a copy paste (with slight modifications) from the official wiki

Script support so prompts can contain wildcard terms (indicated by surrounding double underscores), with values instantiated randomly from a corresponding txt file (or a list of strings)

a woman at a cafe by artist and artist

will draw two random artists from artist.txt. This works independently on each prompt, so that one can e.g. generate a batch of 100 images with the same prompt input using wildcards, and each output will have unique artists (or styles, or genres, or anything that the user creates their own .txt file for) attached to it.

Resources

• https://github.com/jtkelm2/stable-diffusion-webui-1/blob/master/scripts/wildcards.py
• https://github.com/AUTOMATIC1111/stable-diffusion-webui/wiki/Custom-Scripts#wildcards

[WASasquatch]

I have something similar, which this seems to be based upon idea: https://github.com/WASasquatch/noodle-soup-prompts [Wiki] (Seems to be my artist list)

I have been suggested to move my system to a file-system for ease of management, but I do like how easy it is to distribute JSON.

This is more meant for the end developer to easily implement and parse prompts before hitting diffusers, so that the prompt is like a normal well-formed prompt.

[patrickvonplaten]

In general, the philosophy is to open a PR that is already in a reasonable state to have this issue be assigned to you. Then we can all work on the same PR 😃