Yes, the desaturation when you use the "DNG neutral" profile is obvious. Besides the fact that they use one identical profile under the names of "M240 generic v. 2" and "M10 generic" it is the second cause to leave C 1 alone - which I regret.
Did anybody try if the strong desaturation in thr DNG neutral profile happens as well when you use files from other cameras? Or is it an issue only for M10 files?
I realise this is an old-ish thread... but I have had exactly the same issue that was mentioned in some of the above posts.
I used to use Capture One v.9 ("C1v.9"), and the 'DNG Neutral' profile worked very well with M10 files. Now, using Capture One v.11 ("C1v.11"), this profile looks awful and de-saturated using the DNG Neutral profile. And the "Leica M10 Generic" profile is also awful, compared to the way the "DNG Neutral profile" used to work...
"Leica M10 Generic" profile vs "DNG Neutral" profile:
The named "Leica M10 Generic" profile in C1v.11 is much inferior to the "DNG Neutral" profile in C1v.9. Not only are the colours using the M10 Generic profile in C1v.11 too saturated (which would be easily correctable if that were the only issue), but they are a bit odd: darker blues shift too far to magenta/purple, and skin tones often take on a pink hue. I have seen this with pictures taken in vastly different lighting conditions - from daylight sun, to cloudy, to flash, to indoors with (low) available light.
Problems with the DNG Neutral profile in Capture One v.11 vs v.9:
The problem is that, as mentioned above, the DNG Neutral profile seems to have gone rapidly downhill in C1v.11. The colours don't match the C1v.9 process even when the saturation slider is increased. I even tried copying across the C1v.9 'DNG Neutral' profile file (.icm file) to C1v.11 and applying that, but it looks the same.
Interestingly, in C1v.11, if I view M10 DNG files that were previously processed in C1v.9 (with the "Engine" still selected as "Capture One 9" in the "Base Characteristics" tool), these also look desaturated and washed out. Very odd - given the very same file looks fine if I go back and open it in C1v.9.
Attempts to correct colours for the M10 in C1v.11:
Indeed the colours in the JPEGs produced by the M10 are much better than either profile option in C1v.11. But I have found it extremely difficult in C1v.11 to try to match them for DNG file processing, even approximately. (Have tried the following tools in C1v.11 without success: white balance; colour balance; colour editor (both basic and advanced); and even tweaking the separate R, G and B curves - looking at a JPG file as a reference and sampling RGB colours, and trying to match in the equivalent DNG file.)
I would rather not go back to C1v.9, having paid to upgrade to v.11, and wanting to use some of the newer features etc. ... but this is all quite annoying.
Does anyone have any thoughts on using C1v.11 with M10 files in light of the above? For example, has anyone tried creating their own C1v.11 colour profile for M10 DNG files? (I think I saw something from Adan on this topic in another thread a while ago, but I don't think I've seen anyone post any actual files or C1 settings...)