Does rawtherapee-cli apply Dynamic Profile Rules?

rogerx · January 10, 2020, 8:40pm

Having a little time to muck around, scanning over the initial rawtherapee-cli import:

github.com/Beep6581/RawTherapee

cli version to speedup start time / rt-cli branch

opened 09:55PM - 14 Feb 17 UTC

closed 09:37PM - 12 May 17 UTC

Hombre57

scope: performance type: enhancement

I've created `rt-cli` branch that build 2 executables : `rawtherapee.exe` and `r…awtherapee-cli.exe`. The later one doesn't integrate the GUI code at all but includes all the command line options, while the first one now only support directory or files through the command line options. Use `-h` to see what is supported. You'll se a new `-q` option (for _Quick Start_ mode) that will not load the HaldCLUT files nore the color profiles. Users should use this flag if they start RT through command line for every new file to process (i.e. don't use wildcards). To test the `-q` mode, just include film simulation, custom input profile and non standard output profile to the pp3. Works fine here. Example of processing a 10MPix PEF file with lots of processing on Core-i7 / Windows7/64 : - rawtherapee-cli.exe - w/o `-q` : 9.08s - rawtherapee-cli.exe - w/ `-q` : 7.50s The difference is (should be) the gain of the `-q`flag. This will increase the install bundle by ~2Mb. Please tell me if it's worth it. It's still possible to revert the usual `rawtherapee.exe` to its initial state (i.e. get back all the options flags) and reserve the cli version to people that wants performance and can build themselves...

The discussion on GitHub doesn’t explicitly mention if Dynamic Profile Rules are applied. Performing a quick test it seems likely initiating rawtherapee on an image does apply all rules and profiles similarly as if rawtherapee.exe/bin were called itself. I believe the “-q” option averts or disregards all default profiles and rules, quickening the startup time of rawtherapee-cli. Did I comprehend the discussion correctly as well as rawtherpee-cli execution properly here?

Doesn’t rawtherapee-cli, by default, apply the default profile set within rawtherapee GUI as well as Dynamic Profile Rules? I think I might end-up answering this one myself, use “-d” to use the rules specified within the rawtherapee GUI settings/preferences (eg. Dynamic) (The -h help statements were somewhat vague.) (My question #3 answers this question.)
Within the “rawtherapee -h”, “-o” and “-O” options seem to be a little quirky, and “-O” should likely reference “-o” instead of “-O” within it’s help text? (rawtherapee-cli ignores the “-o” option.) I’m also experiencing if other options are not put within a specific order, some options might be omitted during rawtherapee-cli execution. To re-word this better, rawtherapee-cli seems to be ignoring options on the command line when the options are specified in a certain order. (eg. “-d” option placed at the end of the line after “-c” file/folder name.)

If the user specifies “-d” after the input filename, error “”-d" doesn’t exist!" is printed to stdout.

No debug/verbose option when using rawtherapee-cli. If there were a debug option, likely the output would likely include information on what profiles and/or fixes are being applied. (I guess I could recompile with -ggdb. “-O” prints a pp3 file, and I can now see the lens’ profiles being applied.

Think maybe offering a patch to make the “-h” and manpage more explicitly worded?

Using the following for processing my raw files through the command line:

$ rawtherapee-cli -d -c /folder/input_file.nef

Use “-O” to also output the *.pp3 profiles used for processing.