Yes, the difference between listening to Spotify and playing a piano. Sorta. 
DT is a multi-faceted tool, a means to a solution whereas some others are designed as pre-built solutions - “take your pick”. Obviously that’s not 100% accurate across the spectrum, but it looks that way to me.
1 Like
You mean like darktable 4.0 user manual - process ?
6 Likes
Absolutely. How did I forget (overlook?) that… oops.
Thanks.
Quiet possibly dt would not be a ‘first choice’ for a casual shooter with a phone-camera.
Those comments were not nearly as bad as I had feared. It seems Darktable’s image has improved considerably in the last few years.
Now it’s mostly, “cool, but seems too hard to use”, instead of “dumb toy for Linux nerds” that I seem to remember from not too long ago.
2 Likes
I use them - both.
Because the PC market is growing in general and Linux is used in many devices, but hidden, like most NAS. Plus, many other hardware (RasPi, embedded whatever). As a windows user for those sort of hardware I would always go with Linux. But on a desktop Windows often comes pre-installed free of charge and that’s what 98% of people want. Bonus: it just works.
Back to topic, so darktable got forked by someone into R&Darktable. Now, there are 900+ darktable forks. If something good comes I will take look. A de-cluttered version would be great (anybody here used the “monochrome module” within the last 3 years 
) , and a file browser please…
Just keep an open mind, forks can be wonderful, see ART (which is not a RT replacement btw)
2 Likes
Oh, believe me… you paid for it. TANSTAAFL, particularly when it comes to Microsoft. 
5 Likes
As I said before, you almost need to fork if you want to contribute to dt (pull requests are requests to pull from another git repository). So a lot of those forks have no intention of being used as a variation of darktable. That’s what makes Aurelien Pierre’s fork different (besides him being one of the “louder”, more visible contributors).
(Not saying all forks end in pull requests, many could just be out of curiosity or to play a bit with the code)
Have you read the darktable FAQ? Of course, you can already browse the directory structure as far as imported images are concerned, or when importing images…
I’ve sometimes used the “fork” function without making any changes, just because it’s easier to look through stuff I’ve forked than through stuff I’ve “starred” or am watching. Also in case the upstream project has someone go excessively scorched-earth, or accidentally commits something that calls in a DMCA nuke, I’ve got a copy of the source code preserved. (In the case of DMCA nukes, assuming I cloned the repo before whatever triggered the situation and thus don’t also get nuked.)
As another example, there are 249 “forks” of RawTherapee on github. To my knowledge, the only true fork (as opposed to just a contributor cloning a repo) is now hosted on gitlab (ART) and in fact does not exist in that list of 249 “forks”.
For “true fork” read “permanent fork”.
This is a minor thing hopefully and I didnt want to start a new thread; is anybody using R&Darktable able to use LUA? I’m unable to make it work (and yes it does work on dt4).
CIao, @aadm,
Yes, it works up here in The North.
I used git source and did not change a thing in the settings:
What OS are you presently using?
LUA version?
Cord. Sal.,
Claes a Lund, Svezia
thanks Claes. Compiled from master on Ubuntu 21.04, lua version I don’t know but it’s the same as in dt 4.0 (where it works)? I have copied bits of the darktablerc config file from dt 4 to r&dt, I should probably check with the original config file?
Ho-hum Sounds like a very plausible culprit…
Well, it wasnt the config file after all. I had no liblua installed so when compiling LUA support was switched off. I had to sudo apt install liblua5.4-dev and now I have lua support back on.
However I do have another problem with r&dt (*); I see no captions below thumbnails in lightable!
r&dt:
dt 4.0:
I have of course read the wiki where AP writes:
the extended overlays mode for thumbnails: each of the EXIF metadata display triggered its own SQL request per-thumbnail.
Which I thought was meant to remove the text that appears when hovering on an image (set with preferences/lighttable/thumbnails/pattern for the thumbnail tooltip), while the “fixed” text, i.e what is shown above in the dt4 screenshot (set with preferences/lighttable/thumbnails/pattern for the thumbnail extended overlay text) was still available.
(yes I know that what AP clearly refers to extended overlay mode, i.e. what I’d like to see under the thumbnails but in terms of avoiding sql calls I thought that the dynamic display when hovering was more problematic)
(*) I will say that the only thing that really bothers me about this fork is the name: with the stupid ampersand in the name itself I’m sure google will never find any reference to this particular fork and redirect to the normal darktable.
My vote is to call it narktable (because the maintainer became so narked )
2 Likes
Yes; the lack of thumbnail overlays is something that I really would like to see fixed. … otherwise I find this fork very comfortable.
Who wants to study manuals to browse files? Their file system is simply bad and not logical, leave alone intuitive. Start with ‘Import’ - I and the files stay on my folder. I know, maybe poor translation from French. But over the years it never got corrected.
BTW, I understand darktable can’t really be intuitive, it’s too complex. All the better photo editors are like that and require a good amount of learning.
2 Likes
FAQ != manual