It would be helpful to allow a preset to be specified on the command line, to have an existing preset to be applied to the input images rather than Autopilot. This would also be much easier and less error prone than using --override to specify individual enhancement parameters.
My intention is to run TPAI from a script or batch file, as part of my workflow for scanning boxes of 4x6 prints using an Epson FastFoto FF-680W scanner. The scans are all very noisy, and the jpgs have very large file sizes considering the quality of the scans. So I denoise them in batches in TPAI before importing to Lightroom Classic for further editing. I want to automate this denoise step.
I have a workflow that involves consistently needing to batch process photos through TPAI but the jobs consistently always utilize the same .json preset file.
Looking through the CLI documentation, it states that the CLI jobs will run whatever Autopilot is configured to - but I’m not seeing a way to associate Autopilot to the imported .json.
Is there a means of doing this that I’m not seeing, or would this need to fall under a feature request?
The CLI capabilities will always use the Autopilot Preferences, meaning it will apply the settings you’ve configured there. Currently, there’s no direct way to associate Autopilot preferences with a specific .json preset file in the CLI workflow.
This sounds like a useful feature, and is added to our Ideas section
We use Photo AI mostly to scale up photos for printing.
Generally letting photo ai decide works well. Other times I have to manually drive the options as the upscale is not enough or it decides to ruin a great photo with noise, or face correction is too strong.
I have a number of presets that work well and it would be great to be able to specify them on the command line.
Idea: Add an option on the command line to specify the preset to use when processing.
