Create a remote processing executable for batch operations

CaptureOne could dramatically reduce the amount of time to perform batch operations (e.g. generating previews, packing EIP files and exporting finished images) by creating a separate executable which could be run on other machines whose sole purpose is to run batches of operations.

Example #1 Outputting Images

Many photographers have additional machines sitting around their office which may be idle. I work on large batches of images in the 10s of thousands and output time can really be an issue. However, I have five capable, but idle, machines which could be doing work.

An executable which could be run on a networked machine (and does not count against the CaptureOne seat/license count of a business) which could watch a particular session location or watch an XML file for output instructions and output completed images would be very valuable.

This could operate in "watch for changed files" mode where it would watch file timestamps. Or it could operate in "queued files" mode where it only exports images which are specifically queued for processing via the normal CaptureOne export interface.

I personally would prefer the timestamp mode. This would result in the same image being output multiple times in between edits (perhaps a delay could be added between the last modified date/time and when the exporter "picks up" the file for processing to reduce the number of times a file is exported), but this mode results in images being ready with the least delay from time of editing completion.

Example #2 Generating Previews

Preview Generation is another area that could benefit from an external batch processing executable. Fed a list of paths, the batch processor could inspect each path for RAW images and generate previews for any found. Alternatively, fed a root path, CaptureOne could inspect subfolders automatically.

I photograph sports and every match I photograph is organized into its own folder structure. I can return from an event with 15,000+ RAW images. Before I begin editing, I typically start CaptureOne and, one by one, point CaptureOne to each folder of RAW images and wait for it to generate previews, then move on to the next match folder. This is time consuming and would greatly benefit from automation. I envision being able to point a CaptureOne batch executable to a root folder and let it traverse the subfolders looking for RAW images and generating previews.

Example #3 Packing EIPs

Another area that could benefit from a batch executable is packing EIPs. As I type this, I am waiting for CaptureOne to complete packing a batch of over 1200 EIPs. Estimated time to completion was 16 minutes. CPU utilization is between 40-90%, impacting system responsiveness. It would be nice to hand this off to a networked machine and keep my editing machine as responsive as possible.

My hope is these are high value, low effort features. :)