I am currently doing some benchmarking of RAW development tools, and I was trying to run RT in batch mode with Auto-CA enabled. Here is the .PP3 file that I have been using:
the program does not seem to perform the automatic calculation of the CA correction parameters, and the processing time is very close to the one with CA=false. On the other hand, when enabling the auto-CA in the UI, one can clearly see the cursor progress during the CA processing, taking it seems at least half of what is needed by the AmAzE demosaicing…
I am using version 5.2 under Linux, installed from the myway PPA.
That means auto correction is enabled. The correction parameters are per tile and not written into the pp3.
Edit:
CA=true means raw ca auto-correction is enabled and CARed and CABlue are ignored. CA=false means the CARed and CaBlue values are used for the whole raw, except if both are zero, then raw ca correction is skipped.
I just tested full processing (in rt queue) of amsterdam.pef (10 MP) on my 8-core. Neutral needs 1270 ms while neutral + auto-ca-correction needs 1330 ms.
I checked, and indeed there is a difference. What puzzles me a bit is that if I export the file directly from the UI (export button below preview) I can clearly see the progress bar advancing during the automatic CA correction, for a time which is more than 1/10 of the Amaze demosaicing phase… however, if I use rawtherapee-cli there is little difference in processing time with and without auto-CA.
How I can print the time required to process a file in the queue?