I have a strange problem I have been breaking my head on the last week. I run Arch linux, and have the official Darktable 3.0.2 version, and a home-compiled 3.1.0+2495~g79cc7ac9b. I have been running dfferent git versions the last few months without any problems. This latest versions shows my raw files from my Nikon D750 very very dark, like they have been extremely underexposed. Even increasing exposure doesn’t give a proper exposure.
I have a feeling it’s my fault, but I don’t know what - I searched the forums and open issues at github, but I don’t find anything similar (therefor I think it is me). Maybe something has changed in the default applied modules, or some other setting I need to change?
I have separate config dirs for my Darktable versions, and totally cleaned my databases before importing the raw files (removing old leftover xmp files first).
I’m set up to run multiple darktable versions (2.63., all of 3.0.X and the latest 3.1.0) and the D750 is my main camera: I do not have, or had, any issues with my RAW’s in any of my test or production environments.
Just focusing on the development version:
Have you tried building the latest version? (at the time of writing that would be 3.1.0+2543~gafe88cdb7) Experience shows that a particular development version might sometimes not be completely up to specs, this being development and all.
Have you tried using a fresh darktablerc file? Just move the current one to a safe spot and start dt).
You mention removing xmp’s and cleaning the DB, but have you tried creating a new, dedicated directory, copying a few RAWs into it and importing that dir?
You do not mention how you have separated running the different versions and this might be of influence. I have strictly separated everything; Each version has its own config, cache and (RAW) directories.
I tried 3.1.0+2495~g79cc7ac9b but not the very latest one, and a few earlier ones, but I don’t know the versions. It (the darkness) did already happen last week with an earlier version. That’s why I updated again.
Anyway, I use fresh darktable rc files, and both versions have separate configdirs. I did also try a clean new directory which I imported anew.
Don’t know where you get your version from. I pull the latest version from GitHub. Latest one ( 79cc7ac) was updated a few hours ago (12:45 CEST).
I did a few more tests, specifically scene referred vs display referred and turning on/off base curve auto apply. Whatever I try my RAWs look normal.
Only thing that comes to mind now is a, possibly self made, preset that is automatically applied. Only way to be sure: Check the presets in the preferences dialogue.
BTW: Have you tried RAWs from another type/brand then the D750? If so: Same issue? If you don’t have any lying around: Check out pixls Play Raw section, plenty RAWs to choose from.
About our versions appearing to be different: They aren’t
This: (g)79cc7ac9b is the part that counts and those are the same for both of us.
2495 and 2543 are rather irrelevant. I have merged Aurélien’s future channel mixer rgb into my local copy for testing, that explains the difference in this number.
PS: You didn’t mention if you also see this problem with RAWs from other brands/types…
Ah, of course how silly of me, I concentrated on the first number.
Three observations - (0) the effect is a lot worse with one of my older lenses, and (1) the git version of dt has highlight recovery on. Could that be a reason? (2) I tried one of the files from playraw (a nice lilly ) which shows up identical in both versions. So it has to do with my RAW files.
Looking at the things you have mentioned thus far I’m starting to believe that darktable isn’t the issue.
About highlight recovery being on: Yep I noticed that as well on my side, but no negative side effects at all.
The other 2 points in your latest reply both suggest it being your gear and/or the way you shoot. It is strange though that you only see this problem as of late. Have you set EV compensation and forgot about it? Had a brain-fart like that myself once (forgot to turn off -2/+2 bracketing).
You could upload one of your RAW’s here so we can have a look.
Yes, I am also thinking that it is my raw files/the way I shoot. I do have a -1/3 EV compensation set, recovering shadows is easier than recovering highlights, but that was never a problem before.
I haven’t deliberately changed settings on my camera, and it didn’t happen before, but I’m doing something wrong
how silly of me, I concentrated on the first number.