I totally agree. This is really a great release. Particularly the filmic and retouch modules mean a big step forward when it comes to processing my architecture shots
filmic because it allows such a great tone mapping and it became much more convenient to achieve the bright but still contrasty tones. (Nevertheless, it is great for so many pictures!)
And retouch allows to get rid of a lot of distracting stuff. And it is really astonishing how powerful it is. Not sure, if I could benefit from the frequency separation in architecture photography. But even without using this feature it gives great results.
Thank you very much for your outstanding work in the new release.
In the linked article “Filmic, darktable and the quest of the HDR tone mapping” there are some “Proper settings examples” for the filmic module. Is it possible to include them as module presets in darktable (I mean in the installation package)?
This would make the life of beginners easier since they can get ideas of how to use a module without learning the complex backgrounds of a module.
The development version, 2.7, has filmic presets and the saturation sliders have been reworked. So, if you can compile the git version of darktable then you can have them otherwise they probably wont be out until the next bug fix release (maybe).
I am able to build it on 16.04, so technically there seems no obstacle. I just did not manage to find Pascals email address yet to ask him. Could you please find his address and ask?
K, sorry @aequalis, please ignore my stupid advice and do not contact Pascal. Isn’t there another source for ubuntu packages, with Opensuse or something similar? I have to research tonight … I would be happy to find a source as well, since I do not want to use my self compiled version for my production database, since I may have done something wrong.
That’s the OBS darix and I mentioned - so I guess, it’s time to switch from the PPA to the OBS. I was just wondering, why only the PPA for 16.04 didn’t received the update.
I just tested my self compiled version against the one from OBS, and I found that the self compiled one is by order of magnitudes faster. Any idea what’s wrong with the OBS build?
Probably nothing. Repositories use generic CPU optimizations for SSE2. Self-builds use optimizations for your specific architecture/processor.
If your CPU is recent and supports AVX/AVX2, it can give a serious boost to the performance.
But that could also come from the compilation environment (for example, missing dependencies disabling support of multi-threading or OpenCL, or different compiler).
I must say this version 2.6 works perfectlty and I have noticed no bugs comparing to all versions used before. Really, devs, consider collecting donations, even if they provide you with just one more beer. Your work is worth being paid for either way!
I second that. For the last two or three years (at least) darktable has had a bad tendency to crash when importing images. I reported this quite early, but no one seemed to have a solution so I just stuck with it. Now in 2.6 this has so far not happened even once: It’s been rock steady. That alone would have made me satisfied, and then all the new features on top of that, things couldn’t be better