What chauey is saying has merrit. Many of the users in this forum that have tried using the CLI or batch features were not happy and a lot of them even said that they would not even renew their subscription.
Plus: I think that a working CLI that covers most of the settings the UI has would bring you a long way towards the ability to integration test the entire Application.
And it shouldn’t be too hard to just feed values via json (instead of the autopilot method output).
I’m proposing a simple:
- command line parameter to read a json file, e.g. --useSettings myFile.json
- AutoPilot is still run for each image and stored in the variable that you already use in memory
- But then every (sub)property that is specified in the loaded json (e.g. Enhance/enabled, Enhance/model, …) overrides the one of the autopilot. So in the end you have a merge between AutoPilot and the json. [And if everything was specified in the JSON file, it uses all settings from that file / If only Enhance/model=High Fidelity was specified it uses all AutoPilot settings, except the specific enhance model HQ]
The JSON file could come from this idea, saved via UI.
That should be pretty simple to implement. And it would allow users to re-calculate existing images (or sets of images) with a given preset of their choice. They could even re-run the image in different [future] versions, with the same values to see if the results improved.
And in your integration tests you could trigger the models with specific values and then get an exact expected result image (with which you can compare).
