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 the same photo opened darkroom with only defaults applied (just the white balance module with "camera" preset as far as I can tell): https://flic.kr/p/2dqJg4z The is with the "Contrast/Brightness/Saturation" module turned on, with default values: https://flic.kr/p/24d3TjT On Mon, 18 Feb 2019 at 20:08, David Vincent-Jones <david...@gmail.com> wrote: > 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 > accordingly. > > There is of course loss of detail at higher ISO values but with my camera > I have very clean (noise free) results through the full ISO range. > On 2019-02-18 11:36 a.m., Dave wrote: > > [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. > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > > > ___________________________________________________________________________ > darktable developer mailing list to unsubscribe send a mail to > darktable-dev+unsubscr...@lists.darktable.org > ___________________________________________________________________________ darktable developer mailing list to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
