I’ve seen this many times before, not just with this one RAW file.
Steps to reproduce:
Additional details:
reproduced on latest Fedora Linux, with Nvidia GPU acceleration enabled
Are you saying use the xmp from there or you would also see this with default conditions on this image
I don’t know what it takes to reproduce it from scratch, so use the xmp I guess
I meant from the original defaults or maybe with your combination of modules…in any case comparing against default filmic I took 6 screen samples. I applied the exposure sampled and then applied filmic took it off . Applied it and set auto black and white…each time it came back to the exact values…for me anyway…maybe I will try your version…
Yeah, tried from scratch, with just a couple of modules, lens correction, denoise, auto-applied color calibration and it doesn’t reproduce for me either.
So there has to be something else in the xmp playing a role…
what exactly is the issue? at least on my mac there’s nothing unexpected behaviour.
It could simply be the change in exposure…Its early in the pipeline so it changes everything after it…if you get an edit and just want to bump the exposure a bit…add a second instance later in the pipeline …ie move it…this will keep your parametric masks and edits intact…same thing if you just want a small color tweak…introduce a new instance and put it after where you have things pretty much just as you like it…
Again not exactly sure of what interaction you are seeing…
Maybe i lost the state in which this was reproducible?
Tried to load the sidecar redownloaded from here but no effect… never needed to mess with thoe files, so I’m not even sure if my stuff was in it to begin with, if I didnt write the file manually from dt? Idk…
Either way, after going through that sequence, upon touching filmic the whole image is strongly tinted magenta, and ever resetting or disabling filmic doesn’t make it go away.
One has to undo both filmic and the change in exposure in the history stack.
Which doesn’t make much sense because just adjusting the exposure does NOT produce this effect, only a subsequent change in filmic.
the workaround of using another exposure instance just below filmic works though, thanks for that.
Ya I don’t see that so not sure what is going on…I can drive the exposure pretty high and not see that …
Can you do the same steps, but instead of disabling filmic, turn on HIgh Quality Processing?
weirdly… no.
Since I introduced that second instance of exposure, the issue disappeared, even after getting rid of it and reverting to a previous state. Can’t reproduce it at all, works as expected.
So… something’s weird. Applying the same changes to the same state should arguably not have different result depending on actions no longer present in the history.
I will reload the sidecar and try it, but… tomorrow, I maxed out my proverbial OCD on darktable today, need some rest.
also, can you reproduce with Open CL disabled?
It happens also to me often. Working with fimic rgb and suddenly the picture become blueish.
To restore the correct visualization I enable/disable the screen simulation (CTRL+s)
Is this the same issue? If so, please comment on that thread your steps to recreate.
To me it looks like dt uses the wrong color calibration in the preview pipe
In case anyone’s still interested, I can confirm this is not only an issue with RAWs from my Fujifilm X-T4.
Just had a go with this one that was taken with a Huawei phone and can observe the same happening.
Though I’m noticing, toggling the left or the bottom panel ot the UI also toggles the bug. Not something I noticed with my RAWs, but I might just have not messed with the UI this much in the past 
Unless you provide comments in GutHub, with the steps to reproduce, it will remain a bug.
No tint for me using dt 5.2.1 or development version 5.3 from current git master.
Linux, Debian 13, compiled from source. EDIT: Intel I914900K + Nvidia Quadro RTX 4000 GPU + 550.163.01-2 driver.
not the first one who can’t reproduce it. Gotta be someyhink specific to my hardware or OS… Though I have a Dell notebook with a standard Intel CPU, I’m not sure if the NVidia graphics are relevant here in any way.
So maybe it’s Fedora. Idk… Well, maybe starting 5.3 I’ll be using agx insteald of filmic anyway, or it goes away (haven’t seen it with 5.1 ither IIRC.
