Correct, previously I was trying to get monochrome applied
automatically. But, aside from knowing that I was not trying to do that
in this case, please note that I have not said the whole image is in
monochrome; only a selection of pixels have turned a sort of 'polluted'
grey - with, apparently, some red in them. I don't see how this can be
the result of some preset as, as part of this learning exercise, I have
performed a clean install of DT and all my test images, newly copied
from LightRoom. None of this answers the question of how did the
monochrome module get into the history stack in the first place. Of
course one valid explanation is that I am so intellectually stunted that
I do things without realising it or perform actions with no idea of
their consequences. If this were the case, would I be able to use DT at
all?
On 24/07/2020 10:49, KOVÁCS István wrote:
On Fri, 24 Jul 2020 at 11:29, tony Hamilton <shaky.st...@ntlworld.com> wrote:
The reason I ask is that 1 module’s appearance in a newly
imported/opened image grabs my attention: monochrome. Why is that there?
And it makes a difference, causing a ‘rash’ of mid-grey pixels to appear
in the sky in this particular image. If I ‘reset’ the history to the
step before ‘monochrome’ this rash disappears. What is going on here?
Monochrome turns the whole image B/W, unless it's applied with a mask.
Am I mistaken, or were you trying to get monochrome applied
automatically just a week or so ago? Maybe there's a connection?
https://www.mail-archive.com/darktable-user@lists.darktable.org/msg09426.html
Kofa
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to darktable-user+unsubscr...@lists.darktable.org
