If you hover over a node on the graph you can scroll it up or down now.
You have three tabs for hue, saturation and brightness.
I did like the way Rawtherapee did this. If I remember rightly, it had a selection of this-according-to-that pairs. But hey,we picks our raw processor and have to lie in it, feathering out nests accordingly 
Oh! …that doesn’t work for me. scroll moves the whole right panel, even if the pointer is on a colour-equaliser module.
I don’t mind. Mostly, that is what I want it to do. Might be a result of one of my settings.
I don’t know what you are dreaming about, but deprecated modules are not seen except in old edits where there are in history.
Mandatory modules will be visible. You can hide them actively but as a dt option, a no go.
Beginner workflow or QAP are your darktable friends.
Auto snapshots via lua is ok for sure. Not inside dt because a) most users won’t want/need it b) eats up resources c) is just a feq shortcuts away.
This is just a forum …
There was no question, or? Suggestions or dreams, yes.
The devs have a clear concept about this and some things are not open to “voting” 
Get a midi device
Yes, if there is some spare time on my side (I usually charge > 80$/h) Or you’d need a dev thinking so too
2 Likes
Greater than $80/h is a pretty big range… what’s the actual number?? 
Yes, but not when I’m in the image with the mouse and the colour picker is set.
The colour picker (node placement) has the function, together with the slider, of bringing a node to the point where you want to change the colour of the selected point, doesn’t it?
I opened a feature request for this issue but it didn’t go anywhere. I solved the issue you are trying to solve for myself by having a shortcut for the colour picker of Colour EQ and the same shortcutkey+scroll to adjust the node placement.
3 Likes
Oh my gosh, I think I had written about capture sharpening specifically in a different topic thread… I had started this topic to track that discussion without cluttering up the other thread. @rvietor I apologize, I thought I had included my thoughts on capture sharpening specifically in the original post of this topic. I am sorry I thought you had just not read my post entirely.
@Phemisters thank you for pointing out my error. I appreciate it.
Oh ok great.
3 Likes
here is the quote of me from a different topic. It was the inspiration for this topic and I thought I had written it here.
1 Like
I think it only selects by hue…so you get hue based adjustments which I think you normally decide from the picker or a range to have the control you need on that hue selection…The masking tab then handles how these adjustments are masked but its not like the tone eq…
I suppose you could look to build something in to it… so it would work on he hue of the area that you were hovering on?? I have no idea if this would be a smooth feature in the code??
What do you expect ist the difference to the already existing reset option in preset generation?
reset all module parameters to their default alues
…. This can be used to automatically set certain modules (color calibration, exposure, filmic) based on the Exif properties of the current image rather than setting to hard-coded parameters.
The difference is that the current option in the create module preset dialog actually resets all module parameters, not just the ones that generall auto-detect exif data
this sounds like an issue, please provide a reproducible scenario …
Reading this topic, but also other topics, I am prone to think that most us of - including myself - do project the way we use darktable on others. So we are extremely biased (unconsciously) about how to use darktable.
To give a couple examples:
-
for my gear, capture sharpening doesn’t do much. I hardly see any difference. So I have wondered why is it even in darktable.
-
for my type of photography using the simple tab for tone equaliser does not bring the results I want. I have said to others that would like to see it removed. But then I learned that someone else is using the simple tab a lot, because they have different workflow and use case.
-
I recently learned that someone else is using color callibration module to make image monochromatic. I have not considered that use case and have wondered if that module could be simplified as many of the effects I use it for can also be done using the primaries module. I use a couple of LUTs to make my images monochromatic.
So bottom line, we don’t know how every one else is using darktable. So I would like to make an appeal to everyone that read this:
Please, dear developers and core people,
if someone comes up with a suggestion to change, please thank them for their feedback. By far most of the comments I read here on pixls was just a user expressing their opinion. Sometimes it was clunky. But almost never it was an attack on you as a developer.
I am a software engineer by profession. And when users talk with me about something that is not working for them or is unhappy. I feel my blood pressure rising, I feel attacked, I start to think: “you have no idea how hard this was. You have don’t have any appreciation for my work”. But looking back for almost 25 year now, I can’t think of many situations that I was attacked personally. I have learned over the years that if I go beyond my initial emotions often there was incredible feedback that made the product (much) better. Because, as a developer I make mistakes and I don’t have perfect knowledge.
So please as from one developer to another, take user feedback - even if it is clunky - as something to consider. Don’t assume that the user is uneducated, doesn’t know the software, doesn’t know what he is talking about. Maybe they have a point. Probably not all the time. But appreciate that the user took the time to write a suggestion.
dear fellow users
Shall we keep in mind that we are biased how we use darktable? We are maybe not understanding what the developers intended.
Let’s remember that we only have our small world. Let’s be grateful to devs that they build this incredible project. Do we know that things can be improved? Of course we do!
But let’s be aware that when we talk about a certain module, we are talking about the hard work that a developer has put in. And that their feels are attached to the module - even if they are not aware of that.
So my appeal to us, from one user to another: if we want to make suggestions about things that can be improved. First let’s ask the question on the forum how others are using darktable. And shall we keep the feedback in the ‘first person’ in stead of generalising?
28 Likes
+1, @martinus’ post should be mandatory reading before participating in any discussion 
I will add that when writing into a textbox, it is very easy to forget that there are people on the receiving side. The dynamics of interactions over the Internet are very dehumanizing, and it’s easy to leave the good manners outside the door. Even more so nowadays, as we are getting used to issue harsh orders to language models that behave like slaves and that will take any kind of abuse without a complaint.
In addition, trolling on the web is huge, so it is very easy to read more (aggressiveness, complaints, harsh criticism) into messages affected by careless wording, naivety, poor computer literacy, linguistic barriers or what not.
Each and every of us, even when armed with the best intentions, can write something that will hurt someone at some level. Let’s all remember that, assume best intentions and reply with kindness. There is nothing to lose and a lot to gain.
12 Likes
@MStraeten You can reproduce this, for example, with the lens correction module. I assume that the manual vignette correction is not dependent on EXIF data (hence the name). But with the reset option set in a preset, these values are also set to their defaults.
Actually, I think this kind of mentioned in the documentation
reset all module parameters to their default values
Selecting this option will cause all module parameters to be reset to their default values (as if you had simply enabled the module on a new image or clicked the module reset button).
I tested just the other day with lens corrections. I tried creating a preset that would detect the lens of whatever photo it was applied to, but only correct distortions. I enabled the “reset all module parameters…” option to make sure that the parameters that use exif data would not be hardcoded to the lens used for the original photo.
When applying the module preset, all controls get reset.
I have spoken with other forum members and this seems to work as intended. That is why I suggested a different option all together.
You could do it with a lua script. Have the script create a shortcut that enables the module and then sets whatever parameters you want.
Yes, and I will provide another examples due to this comment:
The orientation module have a usage far beyond this:
When we look at an image, our brain immediately starts a cognitive process in trying to interpret its content – to understand its description of our 3D world and of any social relations/implication (if there are any humans involved or implied).
This process automatically takes precedence over any analysis/perception of the image’s 2D properties as to forms, lines, colors etc – which for a great part sums up to that what we call “composition”. (And this is, by the way, the reason for the existence of many visual illusions, e.g. why we see similarly colored patches in the image as different, because our brain have already cognitively given them different meaning/function in the image.)
So to be better able to consider the pure compositional aspects of an image, we ought to be able to turn off the influence of this 3D interpretation process and let our brain rather see images as color patches on a plane. If we have the image on paper we can quickly do so by turning the image up side down (and thereby deny our brain the immediate recognition of known objects/situations).
Working digitally the orientation module is our friend.
Yes, in general we humans too easily do so. It may be useful, though, to try to remember that “an offense can not be given, only taken”.
Oh yes, many modules have uses beyond the basic case.
I just wanted to give some examples why hiding the “mandatory” modules might not be the best of ideas. I didn’t even want to imply that the examples are valid for everyone…
1 Like
And that’s where you are very, very wrong. Actually that comment alone proves that that there is very much need for the point I was making in the post above.
If someone calls you names, makes allegations, or threats you nasty. That is attacking and ‘giving’ an offence. Also passive / aggressive behaviour, which maybe is more covert, is part of that. Actually al communication you use in any way to ‘talk down’ the person you are communicating with is an attack.
Your point basically says: “it doesn’t matter what I say, the problem is how the other party receives it.”, I really hope you don’t life by that…
4 Likes