-
Notifications
You must be signed in to change notification settings - Fork 27.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Config/scripting support #71
Comments
I'm aware of the feature. |
What kind of workflow is that? You just wrote that you'd be OK with running your script. You literally can run your script in one kine by just importing it the script field. |
I need to be able to automatically process prompts without any human interaction at all. |
Which is what you can do from the thing in the UI. You can process as many pictures from wherever you want, ignoring UI entirely. It's just a place to launch your custom code from. |
And then any change in parameters or functionality does not get logged to my bash history so I cannot reliably reconstruct what exactly I did if necessary. |
did you consider writing parameters to file |
Yes, but I would want several files for several sets of parameters. |
I don't understand this. I don't understand not being able to write to multiple files. I don't understand thinking that things just randomly won't be logged for no reason. I do understand that you don't want a scripting support so I guess we can stop this exchange. |
I am currently investigating the effects of brackets and exclamation marks:
/~https://github.com/JohannesGaessler/stable-diffusion-tools/tree/master/emphasis
I will compare the results against those obtained with this fork where brackets are explicitly processed.
To this end I will not be using a GUI of any kind since GUI interactions are generally not recorded and risk human error.
On the hlky fork I implemented a --cli argument which reads in a YAML config file and automatically processes prompts without further human interaction (the contents of the YAML file are simply passed on to the txt2img function).
Would such functionality be desirable on this fork?
If yes, I will make a PR.
If no, I will simply maintain the changes in a private repository.
I have no problem using JSON instead of YAML if desirable (I thought I had seen you post a screenshot of a JSON file from your repository before but I could be mistaken).
An alternative approach to a config file would be to specify the functionality that I need in an external Python script (would probably need very slight modifications of the existing files).
The text was updated successfully, but these errors were encountered: