https://github.com/butcherg/rawproc/releases/tag/0.7
Not a lot of new capability, but what’s there hurt my head. Lensfun is not ‘fun’ to integrate. Automake has its own mind about things, but not so insane as to drive me to CMake, yet.
Anyway, this release now supports my workflow completely. The img command line program now saves its processing in the image metadata with sufficient clarity to allow rawproc to open-source the original raw file from the img-produced JPEG. img will also read and use the same configuration file as rawproc. So, now I can take a day’s NEFs, copy them to a subdirectory of the day and kick off a batch process with img that produces 800xAspect JPEGs in the parent directory, where my wife can view them in her browser. I can open-source any of them with rawproc and do other processing in addition to the img chain. Nirvana… well, mine, anyway.
The Github release page has an overview. One simple addition that just tickles me giddy are tool lists. These are lists of tool commands that can be inserted anywhere in the processing chain. A tool list is just a text file, one command per line. They reside in the directory you specify in app.toollistpath. Color negative conversion got me to put this in; find a digital image of a color negative, open it in rawproc and crop it to the image. Make sure tool.blackwhitepoint.auto is set to 1. This tool list:
blackwhitepoint:red
blackwhitepoint:green
blackwhitepoint:blue
curve:255,0,0,255
will turn it into a passable color positive. I just did a bunch one morning just to watch it operate… 
Unbounded floating point TIFFs can also be saved and opened. To save one, you have to specify a suitable matrix profile in output.tiff.cms.profile; see Elle’s LCMS unbounded mode article for discussion. Yes, the “u-word”, but I think the capability is still important in this community. I did some changes in rawproc 0.7 to set the stage for incorportating OCIO in 0.8, so I’m not totally ignoring scene-referred.
Numerous bug fixes and robustness changes. Still, I got it to crash my Surface 3 with ~10 tool processing chain. I’m not going to chase that one prior to releasing but if a cause becomes apparent later, a maintenance release will be built.
I know some think, “why doesn’t he pitch in to one of the mainstream efforts, RT, DT…?” Right now, I find this to be my individual solace and refuge as my regular career winds down, something from which I can glean some satisfaction of accomplishment. Once I retire, I’ll have time and attention to contribute to one or more of the ‘regular’ projects, and I look forward to doing so. So long as it doesn’t take away from real photography, or fishing… 