search

DigitalIO / ComfyUI-stable-wildcards

Stable Wildcards Node
MIT License
23 stars 5 forks source link

Is there any way to store the chosen random term in the workflow #1

Closed artkatz closed 6 months ago

artkatz commented 11 months ago

This node works like a charm when it comes to explore random variations of a prompt. What I am deeply missing is the chance to see which term of a random list was picked when reloading a workflow. The "show text"-node by phytongosssss does display the prompt the way it was used e.g. "A blue duck in a lake", based on the original "A {blue|red} duck in a lake". Sadly this information is stored, but not accessible (readable) in the workflow, making it necessary to rerun the workflow to get this info. While it is easy to distinguishing red and blue ducks, it becomes tricky if the random terms are synonyms like {retro|vintage}. TIA :)

DigitalIO commented 11 months ago

Thanks for the feed back. I have made a quick update to store the resulting text into the "extra" section of the workflow. This however does not show up in the UI, you will need to use another tool to read the data. Ex: https://pngchunk.com/

ComfyUI_00109_

I will need some time to figure out how to read that data back and display it in the UI, but for now the data will be saved for future use.

artkatz commented 11 months ago

Brilliant. Thanks a million for the quick fix. Would be perfect to have an additional info field for the extra, (like the seed that was in action)so not to hop back and forth between the chunk reader and comfy. Btw, till about two month ago this storing of the random term worked in Comfy (even so it removed all the bracket-lists in a prompt). So maybe there´s some abandoned line of code in ComfyUI itself, that might be of help. But this comes from a complete noob in terms of code. Thanks again :)

DigitalIO commented 11 months ago

New feature for you:

Hovering over the text area will display the processed prompt. If the prompt was saved in the file, it will be read back as is. If it was not, it will be re-processed and displayed anyway. I wanted to keep the result saved in the metadata just in case it needs to be recovered without the source code.

The hover text will continue to stay updated as the prompt is changed. The caveat to that is that it will not update when the seed is changed. The result will change, but the hover text wont (until the prompt text area is changed again). I'm still looking for a way to get a callback from the seed input changing.

Still a work in progress, feed back is welcome.

DigitalIO commented 11 months ago

Figured it all out :) Everything should stay updated as you are editing prompts and seeds.

artkatz commented 11 months ago

Wow, just when I found out that stepping back in history fixes the cached hover-text, you fixed it already. I run everything again, and it works like a charm. Random may sound like an arbitrary thing, but for folks like me you've restored an essential part of playing with pure chance :) You are a hero :)