For DNG input and outut we use Adobe's DNG SDK. We base our proprietary raw decoding on the dcraw parser, which have built in color matrices (if not provided by the format, which raw formats usually don't) for the formats it supports. These matrices actually come from Adobe's DNG converter in general.
If Adobe's DNG converter is installed we get color matrices from the corresponding Adobe standard DNG. In this first release the DCP color correction code is not enabled since there was a few issues to iron out but we plan to enable that soon. All this is only valuable if you read raw input and write say TIFF output. If you write DNG output the color management will be taken care by the raw converter you open the DNG in. The internal color space used for raw files is Prophoto, same as the reference color space used by the DNG specification.
With TIFF input we support the typical matrix shaping profiles you would use ie sRGB, AdobeRGB or Prophoto, the software tunnels the icc from input to output, and displays colors properly according to the display profile.
We do support a large variety of cameras, but it's hard to make a precise list. We could copy Dcraw's list, but some cameras require some further fine-tuning to provide good quality. I can tell you that I'd really like manufacturers to adopt DNG
, lots of our development time has gone into parsing raw files. I intend to help out if problems do arise with a camera model, it's often just some fine-tuning fix required. If it's a huge reverse-engineering job I can't comply though, but that's rarely the case. We did run into problems with Leaf's new Credo models though, they use some new revision of the IIQ format which we don't have support for yet. I'm also a developer in the open-source RawTherapee project and there I have among other things contributed with support for various camera models. We do read .PEF. Note that we only support ordinary Bayer array cameras though, ie no Fuji X-Trans or Sigma Foveon unfortunately
To be more specific on the CM question. If you want to read raw and write TIFF output we do not yet have full color management support, as we don't apply the DCP color corrections. We do get matrices though, so you get okay color, but for me to say that we have full CM support I want the software to provide a possibility to choose a camera profile which is not yet possible. This feature would only be used for RAW in TIFF out though, and we suspected that most users would do "TIFF in TIFF out" or "RAW in DNG out" or "DNG in DNG out" and then it does not matter, so we postponed it for a later release. If you open DNG instead of proprietary RAW for input does not matter from a color management perspective in general, unless you attach some custom profile with a custom color matrix to your DNG.
When I use the software myself I usually open .mos from my Leaf Aptus and save to DNG for further processing in RawTherapee or Lightroom. Unfortunately some raw converters have a bit dodgy DNG support, so if you are for example a Capture One user you'd probably want to use a C1 -> TIFF -> Lumariver HDR -> TIFF -> C1, at least if you want to take part of C1's color rendering (which kind of sucks in the DNG case
). In the "fine art" case when I really want to fine-tune I want multipage TIFF output from Lumariver HDR so I can post-process further in say photoshop then I usually prepare TIFF input so color rendering is complete before Lumariver HDR is inolved. However if there's a merge involved I do that first, raw in raw out, as merges get more precise that way.
No screen grabs yet unfortunately, we wrote the manual at the same time the GUI was moving around a bit in design so I did not dare to make screengrabs then as I would have to redo that work
. The GUI is pretty basic though. We do merging and tonemapping with a few parameters and generate and display layers.