That is well possible. The sensor uses an RYYB filter, so I would not be surprised.
Any input on why my own builds mess up the colors when using a camera profile, no matter what DNG? Even if I don’t change anything and just build stable 5.8, the colors on DNGs come out wrong. The installed version downloaded works just fine with the same files.
I am pretty confident extending the color temp range would be a workaround for me, but for that my builds need to work…
That basically explains everything. RawTherapee and darktable both assume a RGGB filter array. The “greens” are actually yellows, so the color is way off.
At the moment there is nothing that can be done about this, except to submit a sample to https://raw.pixls.us and file bug reports for camera support here and here. No guarantee that anything will happen with it any time soon though…
The embedded profile is properly used to decode the colors, but not to compute the color temperature. The color temperature is only an interpretation of the WB coeffs × color profiles. It’s really just a code path to add, the case has simply not been planned.
RYYB or RGGB is the same. First of all, none of them is what they say (there is no green, blue, red, yellow or whatever, it’s only arbitrary spectral slices), but then the mechanics are the same : multiply channels by wathever coefficients you have. If you have the right coeff for the right channel, you absolutely don’t care about what this channel is.
I did not test, but one reason for this issue might be, that RawTherapee always uses the D65 matrix inside a DNG file (if available). Maybe for this kind of files it would be better to use the Standard light A matrix (which is available in this file btw.) ?
You can see that there is a weird purple tint on my own builds. Any ideas how to fix that? This is my first time building anything, so it might just be a silly rookie mistake. I build for Windows 64 bit, simply following the guide on RawPedia.
Sure, it’s just a quick fix for the OP in case he cannot roll back the gcc. I have the problem because i compile on Windows with msys2. Once gcc was updated, I could no longer rollback.
$ pacman -U /var/cache/pacman/pkg/mingw-w64-x86_64-gcc-libs-9.3.0-2-any.pkg.tar.xz
loading packages...
warning: downgrading package mingw-w64-x86_64-gcc-libs (10.1.0-2 => 9.3.0-2)
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: installing mingw-w64-x86_64-gcc-libs (9.3.0-2) breaks dependency 'mingw-w64-x86_64-gcc-libs=10.1.0-2' required by mingw-w64-x86_64-gcc
trying to remove first gcc I get:
$ pacman -R mingw-w64-x86_64-gcc
checking dependencies…
error: failed to prepare transaction (could not satisfy dependencies)
:: removing mingw-w64-x86_64-gcc breaks dependency ‘mingw-w64-x86_64-gcc’ required by mingw-w64-x86_64-libunwind
:: removing mingw-w64-x86_64-gcc breaks dependency ‘mingw-w64-x86_64-gcc’ required by mingw-w64-x86_64-uasm
and it continues like this.
I guess I will stay with the removed optimization and gcc-10 for a while. I did not noticed any performance hits anyway.
The good part is that I can report when the problem no longer appears with gcc-10
by the way, sorry @MakeItColder for hijacking your thread