we’re proud to announce the first bugfix release for the 2.2 series of darktable, 2.2.1!
the github release is here: https://github.com/darktable-org/darktable/releases/tag/release-2.2.1.
as always, please don’t use the autogenerated tarball provided by github, but only our tar.xz. the checksum is:
$ sha256sum darktable-2.2.1.tar.xz da843190f08e02df19ccbc02b9d1bef6bd242b81499494c7da2cccdc520e24fc darktable-2.2.1.tar.xz $ sha256sum darktable-22.214.171.124.dmg 9a86ed2cff453dfc0c979e802d5e467bc4974417ca462d6cbea1c3aa693b08de darktable-126.96.36.199.dmg
and the changelog as compared to 2.2.0 can be found below.
- Show a dialog window that tells when locking the database/library failed
- Ask before deleting history stack from lightable.
- preferences: make features that are not available (greyed out) more obvious
- Always cleanup undo list before entering darkroom view. Fixes crash when using undo after re-entering darkroom
- Darkroom: properly delete module instances. Fixes rare crashes after deleting second instance of module.
- Levels and tonecurve modules now also use 256 bins.
- Rawoverexposed module: fix visualization when a camera custom white balance preset is used
- Canon EOS M5
When I change from wanting to see five stars to all one star images, I do not expect to lose the focus from the image I was working on to a different random image. As a result, I may have to scroll through several hundred images to get back to where I was. It is really annoying.
You can see this better if you zoom out a bit, select an image that has a high star rating, and then change the star rating in the view dropdown.
Seems to me it makes sense to scroll the images when you change the view dropdown so that the currently selected image is visible, at least when you're zoomed in all the way. Whether it makes sense when you're zoomed out I'm not so sure.
Either way, the correct place to request a change is here:
And then open new issue https://redmine.darktable.org/projects/darktable/issues/new
Du site web : https://darktable-fr.tuxfamily.org/forum/index.php
– Correcteur de tâches à revoir (++++++)
– Pouvoir trier les Modules (+)
– Améliorer et simplifier le traitement du bruit (1 module de 2 ou 3 curseurs) (+++)
– Tourner la molette de la souris vers le haut pour agrandir un masque plutôt que vers le bas (+)
– Pouvoir fermer les boites de dialogue (+)
– Pouvoir exporter de façon multiple (++)
– Développer le catalogage (comme LR) (++)
– Améliorer les champs de saisie “jobcode” et “surcharge de la date” dans importation par le boitier. (+)
– Préciser le poids d’une image en export (comme Gimp) (+++)
– L’outil Pinceau masque trop noir. Impossible de voir en dessous ni la zone de floue. (++)
– Valeur en iso supérieure à 52600 impossible. (+)
- Pouvoir modifier la balance des blancs d'une image par zones (++)
Je laisse de côté les problèmes de masques.
I've played around by readjusting the export values but it seems to make no difference. If I export as ' copy ' mode - I don't have the problem - but then I don't have the edits in the pictures either...
Any ideas ??
Just upgraded to 2.2.1 from 2.0.7. I haven't tried all of the new features yet, but I have played with the color lookup table. I don't know exactly how it works yet, but its ability to modify colours is cool. It seems to work more locally somehow that the color zones tool. For example, in one image there was a beach with mostly warm tones, blue ocean, and a mostly grey, slightly blue sky.
As an experiment, I tried to make the sky more blue with the color zones tool, but in mainly affected the already blue ocean. However, when using the color lookup table, I could select the sky with the eyedropper, and changing the saturation slider to more saturated only increased the saturation of the sky. (I don't really advocate doing this to most pictures though!)
But the point is, it's an effect that was easy to accomplish using the LUT, but difficult with color zones. Neat.
I agree, I also need to play with the module a bit more to refine my understanding of its use.
I agree that Adobe should be afraid of Darktable.
The commitment and skill of the developers is outstanding. Thank you to all of them.
once more: ask your distribution.
That can fail if there is no package on CentOS for some dependency, or if it's of a version older than the minimum required. In that case, you would need to install that dependency from source too.
there is only list of dependancies and build instructions for ubuntu and fedora. Not sure how to proceed for CentOS.. :/
What do you need to include D810 specific base curve https://redmine.darktable.org/issues/10760 ?
More samples ? beta testers ?
It is a littlebit boring to have to use RT for my raw workflow instead of using directly Darktable for this reason...
1. we have no methodics to verify their validity. 2. we have no one to take care of them
doesn't list my distribution (CentOS 7)