No, I haven’t tried working with PL/DopCor via the CLI … Alex will be the one to ask …
John
Yep, all good John-M and thanks.
Cheers
Chumby
1 Like
Is there any chance there is a command line equivalent in version 5?
Hi,
Could you please explain why you need it?
Alex
Imagine a busy studio. Some (unattended) automation could be welcome:
- ingest images (copy from source, make a backup…)
- apply customising preset
- apply metadata preset
- create previews
- …
Future additions
- group/stack images according to a few rules
- auto-rating/selection according to technical criteria, e.g. eyes closed
- …
I’d prefer such an automation creator with a GUI rather than a CLI, but for more technical applications, a CLI could be welcome (not sure about the size of potential buyers though).
1 Like
Certainly…one of the main motivations would be the ability to do the DeepPRIME processing on a different machine so I can continue to do work on my main workstation. While DxO is running DeepPRIME export to DNG, it severely cripples the performance of the machine. Having to locate images one by one, load them up in PhotoLab on another machine and set the processing to DeepPRIME is incredibly boring and repetitive. I could easily export the list of images I want to process from Lightroom and probably PhotoLab into a text file and use it to run a batch job on another machine while freeing up my main workstation.
I would hope in future to be able to farm out the jobs to even more machines (with additional licenses if necessary) and therefore be able to use DeepPRIME on a lot more images, instead of only using it as a last resort for really noisy high-ISO images.
How many images do you usually need to process?
Alex
1 Like
Often 100-200 per set. It does seem based on previous comments I am far from the only one who is interested in the command line functionality.
Hello Alex,
Could you please share that documentation?
I am experiencing the same problem than shaman, and seems like you did not resolve it in this thread.
Best,
Roland
Reviving this thread 2 years later. Would anyone on the forum still have the documentation alex referenced? I would like to batch automate images through the command line like what shaman attempted years ago. “dxo.photolab.processingcore.exe /h” still brings up the usage options, but like him it stops with “Exit Code: -1”.
1 Like
Bumping this thread again. Any assistance would be greatly appreciated.
Bumping this thread again. Any assistance would be greatly appreciated.
I fully agree with this feature request.
An example of use:
I have over 100,000 photos, including over 10,000 on my website.
When I develop photos, I want the maximum size with the best possible frame for the image.
But for the Internet, I limit the size to UHD (pseudo 4k) and not necessarily the same proportions.
I’ve reduced the image size with other software, but the result isn’t optimal.
I’d like to
- save two variants of my image, which is more or less possible, one for the Internet
- to export with a different definition for the Internet using a CLI batch process, of course using the definitions stored in dop files.
Hope this will a useful approach to the feature request.
Without using a command line, you can already do several different exports simultaneously (for example full definition and smaller size) directly from the Export to disk options. The only precaution is to define a different suffix for each of the exports.
It’s not even so much a feature request. The CLI is still there, just deprecated and publicly undocumented. All we really need is a kind person from DXO’s side to provide the internal CLI document that Alex shared back in August 2020.
Exposing a deprecated, undocumented, and publicly unsupported interface to the DxO audience is not without its costs. If you are an experienced software developer, team lead, or development manager you know the effort it takes to bring a new member onto your development team. It can take a year or more to bring someone up to where they can be a fully contributing and independent member of the team. And this is for an experienced coder who has passed an interview, training, and other onboarding activities. Who is going to help random users who express an interest in the command line without the background for it?
From DxO’s point of view, it may also involve potential loss of trade secrets as well as opening themselves to attempts at reverse engineering of DxO’s intellectual property.
1 Like
It could be more simple to have a SDK as already requested. This could useful to implement .Net Core interface ( CLI and/or scripting is already available with PowerShell):
But this would mean a similar mechanism for macOS as well - double the workload
That’s the beauty of .net Core: it’s cross-platform including macOS: