Then you are saying that when C1 processes a dng file converted by an Adobe product they are using the Adobe Profile? Why not the Capture One profile (for the particular camera) and use the raw data that is within the dog file?
Why would I use Capture One if an Adobe recipe is going to be used? Just saying!
Hi Denis,
The profile type is connected to the color model/engine used. DCP profiles are output referred profiles, while ICC capture device profiles are in principle scene oriented (and can be simply converted towards output ICC profiles in a standardized manner because ICC is an industry standard).
Apparently Phase One have chosen to follow the DNG/DCP profiles for specific (native DNG) Raws, and convert that back to the input scene referred model they use. That's a time consuming thing because they have to tweak that reverse engineering for each specific camera, while they already have full support for the camera native Raw format for all other cameras that do not produce native DNGs.
So for the majority of cameras, they would have to do the work twice, once for their own (for them superior) color model, and additionally for DNG/DCP profiles using another color model for those who for some reason like to switch to Adobe products but who already can use the native non-DNG Raws. The question for them, give limited budgets, is then why make life easier for Adobe with the risk of customers switching (thus a wasted investment) if there is already full native Raw support?
But, Phase One apparently do intend to improve color support for DNG, even if it is not their highest priority.
In my (simplistic) view, Phase One should treat DNGs as
two different input formats. One would be for native DNG raws where no other native camera Raw exists, which need to be reverse engineered towards an ICC colormodel. And another for 'converted-to' DNGs where they should almost completely ignore the DNG tags, and only work from the Raw sensor data (before demosaicing) that's stored in the DNG.
The tricky part still remains that only Adobe controls the DNG specification, so Phase One needs to constantly monitor changes in the specification, or errors in the conversion, to see if original Raw data is altered in the process of converting to DNG. There are also variants of DNG (which is a flexible TIFF variant) where the Raw sensor data is not Raw anymore, because it was already converted in RGB. So they still need to interpret the DNG to make sure they are dealing with truly Camera Raw data.
Fact remains, DNG is only beneficial for an Adobe centric workflow, and totally unnecessary (in fact only causes issues) for cameras that produce native Raw data files.
Those who have followed / are following the discussion about DCamProf profiling software
here on LuLa will start to grasp how difficult it is to make a robust profile for a specific color model (let alone two conflicting ones), and how much of a 'look' specific profiles can force upon a casual user of a specific camera/brand. That also explains why Camera makers are not too eager to put their eggs into one (Adobe) basket, and why their own Raw converters occasionally produce a color quality that's preferred by many.
Cheers,
Bart