Been doing it the same way for years. I didn’t change, DT did.
1 Like
More fun. I went back and deleted some old WB settings to see if it would fix the WB issue, it did not.
I also deleted the style displayed in the jpegs above, created another style, and applied it to one of the photos that already had the first style applied.
Before anyone comments: I have done this many, many times in the past. The NEW style always replaced the OLD style. But what happened this time?
We have two filmics, two contrast equalizers, two color calibrations, two exposures, and one of everything else. The White Balance problem persists.
What is your setting in Lighttable… append or replace…
History Stack is ‘append’, Style is ‘overwrite’.
You may be on to something, let me test. Although, why would it duplicate some modules and not others?
1 Like
No change
I wondered if there was any crosstalk…I don’t think there should be…
Adding my reiteration… Neither Tim not I were creating other Exposure modules. All I tried to do was to get rid of the exposure compensation adjustment.
We, both of us, expect to see only the one Exposure module after applying our style. Hope this is correct according to Tim too.
The new 4.8.1 ‘fix’ release did not address this issue.
- Still creating duplicate modules
- Showing exposure as ‘scene referred default’ in the style list and Darktable view, but as ‘manual’ in the applied settings
- Still messing up the white balance, has to be reset each time
Do we know if anyone has taken it up? This is the worst release of DT I’ve ever used, very frustrating.
Correct
if there’s no issue report on GitHub nothing will be analyzed by developers and maybe fixed - issues aren’t fixed by magic 
According to a post in this thread, Todd Prior filled out a bug report. I have no idea how to do anything with Git Hub or anything else. I know how to use the software to process images. And please don’t patronize me.
No, unless I have overlooked something, there is no such report. You misunderstood Todd’s reply. If you want to be sure the developers pick up your issue you will have to create an issue report yourself. Martin is right, nothing will happen until bugs are reported by users. This is an open source project, also dependent on the cooperation of the users.
Again, I have no idea how to do that. I’ve recounted everything in here. You people assume everyone that uses the software is a computer geek. I am not.
So, since I have no idea how to do it, and no one in here seems willing to pick up the ball, I guess I’ll just struggle with it and hope the next release isn’t a piece of crap.
So, you take software provided to you for free, that people develop in their free time, and when an issue you encounter, and refuse to officially report, doesn’t get fixed in a short while, you feel entitled to call it a piece of crap. That’s not the attitude we expect on this forum. Please change it or go away.
3 Likes
You open the link provided above, and fill in a form, in plain English, describing the steps to reproduce the issue, attaching screen shots of you wish. There’s nothing ‘geeky’ about it.
Sorry TIm, I didn’t yet as @kofa had seemed to dive deeply into it I left it to him to decide how to frame the issue…
I have just seen this…I think yet to be verified…
And I do think that the new instance created from modules should be correctly named and not carry over the scene-referred label at they are not the same settings yet have the same label…
1 Like
Hi everybody,
Thank you for discussing this. I encountered the same issue. ATM, I’m pretty sure it is a DT-related thing. I filed a bug-report to their git-issue-tracker. Here it is: Style creation/application messed up in 4.8.1 · Issue #17369 · darktable-org/darktable · GitHub
Greetings
Benjamin