Since this is all FOSS, a fix requires some help from users. There are no beta-tester teams like in SW companies, so it’s the user community here that provides insights and strange behaviors like you observed to the developers.
Filing a bug is really no big thing, you already have all information you would need to provide at hand, by just copying your insights into a bug report. With some luck, this gets fixed.
For further information see
So just feel being invited and welcome to the contributing community
Maybe it’s only the display that’s corrupted (the histogram being the same). You could try exporting with OpenCL = on, denoise (profiled) enabled. If that works, disable it in your processing; create a new style with the module enabled; add that profile to your export settings in append mode (darktable 4.0 user manual - export) for images that need denoising.
As for the original post claiming that the effect is ‘almost invisible’: I actually find that unless I’m careful, the images can become oversharpened (e.g., with the dehaze preset, especially if combined with others). I continue to use the ‘old’ local contrast module, too, and if you cannot get diffuse or sharpen to run at a reasonable speed (or you just don’t like what it does), you can still use the other modules like sharpen and contrast equalizer (it was a long-time favourite of mine, before diffuse or sharpen arrived).
It’s been said more than once in this forum: macOS is not a prioritized OS for the darktable developers. I was unhappy with performance, but I did what I had to: installed Linux after 17 years of macOS. I’m very happy with the decision. darktable runs better in its native environment. My work computer still runs macOS though…
In version 3.8 I too used the chroma only preset. However, I now get better results in version 4.0 with the default settings of the denoise (profiled) module. It tackles most chroma and luma noise well. I even sometimes push the strength slider up to 1.5 with good results on noisy images. I am really impressed with the improvements in this module in the latest version of darktable. Test it for yourself.
@kofa with the high ISO noise shots from my Canon G16 I get good results with the defaults in the latest version of the denoise (profile). It tackles both chroma and luma noise nicely. In 3.8 it softened the image too much for the luma noise correction so I only did the chroma noise in this module and used other modules to tackle luma noise. Noise is less of an issue on my D-SLR images so my testing for noise reduction is based on my G16 images.
If you are using the official release 4.0 for macos, it run under Rosetta on Apple silicon and opencl is unavailable. If you compile darktable for arm64 it runs natively (at least on my macbook pro 14" with m1pro) and opencl is supported (I suppose it’s emulated by metal) and diffuse and sharpen is pretty fast. But you need to compile dt and it’s not straightforward.
JF
I recently upgraded to 4.0 and I am impressed with the new Diffuse/sharpen module. Great results, and even without OpenCL on my old Lenovo Ideapad 110 running Linux mint, it is quite fast enough (I use it for sharpening mostly)
Welcome to the forum… I am the same. I can create enough blurring all on my own when I shoot… The presets are great and then you can do some small tweaks to them and get some really nice results…
you should get some helpful information. I’m on Windows, building there is really not a big thing, updated instructions are available and straight forward. Good luck!
You can safely ignore those warnings: the code is written for Intel processors and use optimizations not available on the arm64. To get rid of the ‘exec windows’ you can create a small app with apple automator to launch darktable. Or the darktable bundle should solve this but the gtk-mac-bundler-0.7.4 script does not work on my macbook and I have not investigate further because I am usually using brew instead of macports . If you need more help, you can send me your mail address because I think we are a little out of topic.