Starting DT from the command line, preceded by ensuring there were no
presets in the monochrome module (*), deleting the .raw.xmp file for the
subject image, replacing the image raw file and its .xmp from lightroom
and clearing the DT cache, results in an image that is clean – no
‘rash’. Original issue obviously a result of
incompetent-and-uninformed-user error. But I still don’t understand how
that ‘monochrom’ entry got into the stack.The results in the history
stack now are:
9 input color profile
8 base curve
7 orientation
6 display encoding
5 output color profile
4 input color profile
3 demosaic
2 white balance
1 raw black/white point
0 original
Most of the additions, over what you surmised might appear, I understand
(well, nearly) but the presence of the ‘input color profile’ module
twice I do not understand, as I have done nothing to this image, aside
from open it in darkroom.
BTW opening DT in this way erased all knowledge of previously imported
filmrolls and all collections. Is that a specific result of opening DT
in this way ? (this command is, to me, a good example of a ‘magical
incantation’ known only to DT developer-types that us local uninformed
Aboriginals are not supposed to understand; it is science so advanced as
to appear to be magic, just like trying to explain the topological
quantum field theory of gravity to that guy from Vinci - Leonard
somebody or other).
(*) There is one remaining preset in monochrome, named ‘red’, that is
locked. Did I do that in my dotage? Why is it locked? Is it a key
component of the monochrome module? If not, how do I unlock it?
PS: The user manual has been read, repeatedly, over the last 6 months.
Aside from being well written and well constructed it is notable for
its ability to not bother the reader with details , so it has not
answered any of the questions which I end up posing to the
long-suffering readers of this list.
On 24/07/2020 14:04, Patrick Shanahan wrote:
* tony Hamilton <[email protected]> [07-24-20 08:09]:
Can somebody please explain to me what controls the content of the history
panel for a newly imported image, newly opened in the darkroom? Or, in other
words, what factors determine what modules appear in the history stack on
such an image before I have started to do anything?
I also want to understand how the ‘property’, (as indicated by the tiny icon
shown to the right of each named module in the stack), is set or determined.
By ‘property’ I mean the choice of ‘always-on module’, ‘default enabled
module’ or ‘<blank>’. The icons for these last two properties are
indistinguishable on my system.
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?
Just guessing from your recent posting you have adjusted a preset or and
import style to always apply "monocrome".
You may partially test this by starting dt from the command line as:
darktable --library :memory:
open an image which displayed your "rash"
in darkroom mode look at history in left panel
you should see something like:
4 orentation
3 display encoding
2 output color profile
1 input color profile
0 original
any other entries such as "monocrone" would be due to you setting them
deliberately.
note that the list may be different for different cameras (I don't know)
but this is what I see importing a new image with default configuration.
I suggest that from your multitude of problems that you begin with a new
install and new configurations, library, ... , and do your own tests.
*** and read the fine manual ***
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
