Agreed, 95% of the time LUTs are too strong and you need to tweak them for the simple reason that LUTs are created for/in/out of a certain situation. LR allows you to do the same. Before Aurelien goes nuts and says darktable isn’t LR: I know, but if you want more people to use darktable then we need to make sure it’s just as user friendly (so I’m not talking about options)
For the opacity, click on the circle at the bottom of the module to show the normal blending options.
2 Likes
For having a chance that you see that on darktable, the best way is to post a feature request on darktable Github : https://github.com/darktable-org/darktable/issues/new/choose
Hi,
And thanks to all of those who contributed to this great piece of software that is Darktable!
It’s my first compilation, and compared to the 2.6 version shipped with Manjaro, this 2.7 is finally reactive enough (4k screen) to be usable.
One thing I miss is the EXIF info inside the histogram. I have managed to show it just over it, but I would like to know how I could take part of the discussions that happen around these kind of changes? I’m starting to following what is happening on github just now, is that enough, or are there better channels to use?
Thanks!
And thank you for bringing the culling mode in DT! Not as neat as in Lightroom, but already useful!
The exif information is above the thumbnail slider. If it isn’t there for you, you hided it, so close the slider and open it again and it will be there …
Thanks but when I’m editing a photo in the darkroom, I do not show the bottom thumbnails.
But as I said above, I moved it to the top right position, so above the histogram, but it now uses more space than before… So it seems to go against the idea of having as much space as possible to work on the photo 
done today. thanks.
Looks slick… can’t wait 
Is darktable easy to customize yourself? I’d really like to be able to detach the histogram and to increase its viewing size. I don’t have a username on github, but can I just post something there and then someone will pick it up?
You can make feature requests on github, and there is a possibility that someone will pick it up. It is certainly not a given that someone will pick it up anytime soon.
A user ID on github is free of charge. I believe that the people here will welcome your contributions, and will cut you some slack as you find your way around as a new user. Set one up here:
1 Like
I was able to download version 2.7.0+1232…-win64.exe and was able to run for a while. Now however, when starting i briefly see a “command window” then however, the program dies out. Tried to uninstall, even deleted:
C:\Users"USERNAME"\AppData\Local\darktable entries
and
C:\users"USERNAME"\AppData\Local\Microsoft\Windows\INETCache\darktable
as well as all entries in registry. At this point still not able to start the program, not even earlier versions that ran successfully.
Where else would I need to check for potential errors, mishaps?
Thanks
Did your windows updated itself in the meantime? Chances are virus protection is killing the program.
If you have this folder then this is where you should find the log file. If you post it, it may give us some clues.
originally in that darktable log file it complaint about that it cannot open the database. it complaunt ablout the wrong version
in
\AppData\Local\darktable are the following files
data.db
data.db.lock
library.db
library.db.lock
since reinstalling I do no get the log file written anymore.
how would virus protection kill it?
1 Were you using dt 2.7 before or 2.6? Chances are there is an incompatibility. An old file or two that may be giving you issues.
2 Windows 10 updated 2-3 times recently. An update may change permissions of files, fiddle around with Defender settings or even move entire partitions. Crazy, eh? But normally, it is user error or misunderstanding.
It has happened to me in the past that windows defender detects that some program is going start executing and it stops it doing so. Thinking that it is a malware. That is what I meant by killing it.
The *.db.lock files should only be present when dt is running. Delete those and try again.
As @afre alluded, if you’re trying to go back from 2.7 to 2.6.x then your database won’t be compatible.