> So the input color profile (camera RGB -> XYZ transformation matrice) is wrong in darktable. Maybe it is not the the color matrix itself that is wrong (source code says it was extracted from Adobe DNG Converter and those matrices are usually very good), but handling the color matrix in DT is somehow off. I am facing another issue [1] currently where, when using a color matrix, the green channel gets substracted from the red channel. I.e. visually it looks like red(out)=red(cam)-x*green(cam), and x is bigger than one would expect. In my understanding that could cause a green tint as well. Maybe these cases are related, maybe they are not, I can't really tell. Only thing I know is: there is something going on when using color matrices in darktable. [In my case the same color matrix is used by dcraw and works fine there.] For me the problem vanished when i used an actual color profile as inpout color profile instead of a color matrix. But to be honest, I can't tell for shure if the two cases really have the same root cause or not. I had a thorough read of the related source code passages, but all these magic numbers that are involved in the chain of various conversions through different color spaces and finally into a color profile were too much for me. So far I settled with using dcraw or the camera manufacturer's tool to convert the raw file into a 16bit TIFF. Maybe that is a workaround that works for Christian, too.
[1] https://github.com/darktable-org/darktable/issues/2528 ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
