Where is the "legacy" configuration button gone?

Software darktable
61

Pascal, there are two kinds of changes:

  • deeply technical, where users have no chance of contributing to the discussion; may not even be directly visible to users (like refactoring and optimisation);
  • changes directly visible for / impacting users (even if it’s a technical change).

I think if you want to make a change to make the tool easier to use for users, discussing it only on GitHub is not the right choice, as most users are not there. Discussing the technical details can and should take place there
I think the way sigmoid 1 2 or color calibration was discussed here, even when things went into the details, was very useful. I understand that it’s a pain to have separate discussion threads running.

2 Likes
62

This idea that merging is somehow an irrevocable process is problematic for me and it’s not the first time it’s been suggested or implied. I am a regular github user (a “dev” for want of a better term). I monitor the issues and the pull requests on a fairly regular basis. I don’t always have time to examine and consider the implications of every change. Sometimes the impact of a change isn’t felt until it’s used or some “aha” moment is encountered. Sometimes I think of something but I don’t have time to discuss/test and sometimes I don’t even have time to read beyond the first paragraph. Ideas that seem good at first glance don’t necessarily pass muster after serious consideration.

There is no length of time after which mistakes can no longer be reverted.

63

Nothing irrevocable, we can adjust when needed and this has already been done numerous time. We had comments about simplifying the workflow setting, this has been done. There is corner cases not foreseen, no problem we can adjust when we we’ll have a clear idea of the blocking problem. Reading latest comment I’m still not sure we have blocking issues, especially with:

But sure I already said it, I’m not for reverting except when it is plain wrong. We need to move forward.

2 Likes
64

Sometimes moving forward means realising that we have not improved things and that reverting to a previous state is the best (least bad) approach. It feels like you are saying that only major bugs should cause us to reconsider a decision already made. Anyway we’ve had this discussion before about other things so I’ll leave it there.

1 Like
65

@Terry I posted this on this thread. If the change had a negative impact, start an Issue on GitHub. Explain your case with details. There is no need provide a solution (eg Revert!). But grumbling (your words) here is not an effective way to provide feedback and start a change. There is plenty of time before 4.4, so plenty of time to address issues.

I searched on GitHub and I don’t see an Issue for this.

1 Like
66

That looks good! Assuming the WB module responds to initialization by reverting to as shot, that would solve any remaining issues for me. Great :+1:

67

I meant no offense with my grumbling here. I see this forum as an informal way of discussing issues and learning solutions. It is not possible for all users to follow every conversation between the developers on GitHub so I was unaware of the coming change. I download and use each weekly build for Windows to keep track of the changes and improvements as well as I presume beta test the changes to DT. I feel my comments here are just a response about the beta testing of the change. Please take it as constructive comments of my observations and not any attack on the work of the developers. I would never do that.

I plan to persevere with the change and find my own solution with the help I have received here. If I truly can not resolve the issues I have with the change I will then post a comment on GitHub with details to explain my case, but I don’t want to add noise to GitHub until giving the change a fair chance.

I feel this informal forum can be the right place to at least express our original reaction. Then others can give advice and help in overcoming our reluctance to change.

Again, thanks to all the developers for their efforts creating Darktable and moving it forward at such an incredible pace.

Edit:

I have set my workflow to none and then created a style applying modules that I want such as filmic. This seems a reasonable solution to me at the moment and I will test it out as I continue processing images. Thanks for the suggestion which is obvious in retrospect. BTW, I did not include white balance in the style as I suspect it would apply the WB from the image I created the style in.

EDIT: I discovered that raw black/white point must also be excluded from the style or bad results can occur.

2 Likes
68

Interesting point, I’ve asked about that where Pascal Obry linked.

69

It does at the moment, but I’m not sure if anything else could affect it…