Filmic RGB reconstruction with slider on bloom causes gray highlights when not using OpenCL #15329
Description
Describe the bug
While writing this issue, I actually fixed it myself by installing OpenCL. Before I did that, this is what happenend to me when I tried to reconstruct highlights with filmic RGB and moved the bloom
In the first picture, the highlight reconstruction module is enabled by default.
I'm using the default options:
I tried disabling the highlight reconstruction module, which is enabled by default, and when I do that, the highlights turn pink.
White balance is left at default (camera reference).
Steps to reproduce
- Make sure OpenCL is not enabled in settings
- Open a RAW image (in my case a Nikon .NEF file)
- Check "enable highlight reconstruction" in the filmic rgb module
- Set the threshold to where the clipped highlights are masked
- Move the bloom
$\leftrightarrow$ reconstruct slider towards bloom and observe the highlights becoming a darker and darker gray
Expected behavior
Moving the bloom
Logfile | Screenshot | Screencast
d_common_log.txt
d_opencl_log.txt
Commit
No response
Where did you install darktable from?
distro packaging
darktable version
4.4.2
What OS are you using?
Linux
What is the version of your OS?
Arch
Describe your system?
- Kernel: 6.5.4-arch2-1
- KDE
- X11
- NVIDIA GeForce GTX 970, proprietary drivers
- AMD Ryzen 5 2600
- 16 GB RAM
Are you using OpenCL GPU in darktable?
No
If yes, what is the GPU card and driver?
NVIDIA GeForce GTX 970, proprietary drivers
Please provide additional context if applicable. You can attach files too, but might need to rename to .txt or .zip
I'm pretty sure I had the same issue on Wayland. The weird thing is that it used to work for me as expected a couple of days ago before I had OpenCL installed/enabled. System updates might have broken something else?