Cool use of Plush nodes - optimize Flux prompts for T5-XXL and Clip-L text encoders!

[EnragedAntelope]

https://civitai.com/models/663699/t5-xxlclip-l-flux-prompt-optimizer-and-lora-autoloader-by-enragedantelope

[glibsonoran]

Nice workflow!

[an303042]

hey @EnragedAntelope and thanks for the workflow!
I've been using it and mostly enjoying it.
I do have a question though.
I'm using groq, and for some reason, if my prompt is something a little loose like "come up with an idea for a photo of an item on the moon" and queue up some generations, it will go back to the same topics, or same ideas over and over again. It doesn't use the same prompt exactly - so it does go out and fetch a new prompt, but somehow groq will go back to the same 3-4 concepts over and over again.
Has anyone else experienced that?
Thanks!

[Jonseed]

@EnragedAntelope check out this collection of "billions of wildcards" in a single YAML file.

[tazztone]

i used those. but it it's just so many that it felt overwhelming to manually use them. what would be some smart way to use them ?

[Jonseed]

@tazztone in the ImpactWildcardProcessor node you can pick the "Select to Add Wildcard" field in the node, which will bring up a list of all the wildcards you have in your custom wildcards folder (which is obviously a very long list if you have this YAML file). But you can quickly filter this list with the open box at the top of the list. So type in "machine," for example, and it will filter the list of wildcards to only those that contain the word "machine," including some long wildcard prompts already put together under the "Bo" category at the top of the list. Click on the wildcard you want, and it will pop it into the prompt. This is a lot easier than using the wildcards manually.

[tazztone]

EDIT: only now i understood what the bo/ categories are for, they are like predefined recipes of multiple wildcards.

thanks. tho i considered this to be "manually" as well.
however i just found you can basically prompt for the categories to get results from multiple wildcards at once by using * :
properties/materials*/*
will get you every material

[EnragedAntelope]

@EnragedAntelope check out this collection of "billions of wildcards" in a single YAML file.

Thank you BTW. I am very familiar :) I try to keep up with wildcards from Civit and have a huge collection, and lately have really liked telling LLMs to make the wildcards for me based on ideas I have (like historical situations, horror scenes, etc.).

[EnragedAntelope]

FYI I just added a new version of this workflow that takes advantage of the additional parameters.

[glibsonoran]

Hey @EnragedAntelope, A while back you had asked me if there was a way to load/use saved 'add_parameter' files (since my node allows you to save them as a file). Well I figured out a way using the Load Text node from the Custom Scripts suite. I made an example workflow called: 'How_to_retrieve_and_use_saved_parameter_files.png', it's in the Example_workflows subdirectory. If you're interested.

[EnragedAntelope]

Thank you for the follow-up! I have since been keeping a long note in my workflows with the settings for copy/pasting, so this is a neater solution :) .

[glibsonoran]

Hey I added an Model-CLIP switch that allows multiple outputs from a single input. It does rely on the nodes it's attached to be able to handle a 'None' value for when the switch is set to another path, but this has worked OK so far.
It would be a way for you to switch between the Lora leg and the No-Lora leg on your workflow (see attached image). Let me know if it works.