I've just rolled back to v2.6.0 and frustratingly still seem to have this
issue.
To illustrate the problem, I've uploaded an example that shows it
particularly obviously.
This is a screenshot of the preview in lighttable (presumably the
camera-produced JPEG): https://flic.kr/p/24d3Ttv
This is
A personal view: my deniose (profiled) works well in general (I often
only use it at 50% or less strength) but I do know that if I 'push' the
processing of the image then the default (ISO) setting for denoise will
not be satisfactory and the ISO setting then needs to be adjusted up
* Dave [02-18-19 14:38]:
> [My previous reply, repeated below, seems not to have made it to the list,
> apologies for the delay]
>
> Yes, I tried turning on the Denoise (Profiled) module and it detects the
> camera/lens and ISO but it doesn't significantly reduce the noise, if at
> all.
there
I'm thinking color (chroma) noise. Did you apply any denoising? The
correction module "denoise (profiled)" with the color preset should
eliminate the chroma noise.
Am Do., 14. Feb. 2019 um 08:12 Uhr schrieb Dave :
>
> When I bought a new camera (Olympus E-M10 MkIII) last year, I noticed a lot
>
When I bought a new camera (Olympus E-M10 MkIII) last year, I noticed a lot
of noise and areas of over-saturation in my photos when initially opening
them in darkroom, which I struggled to remove. Updating from darktable 2.4
to 2.6 solved the problem completely, presumably since it has support
