We’re proud to announce the new feature release of darktable, 3.8.1!
The github release is here: https://github.com/darktable-org/darktable/releases/tag/release-3.8.1.
As always, please don’t use the autogenerated tarball provided by github, but only our tar.xz file. The checksums are:
$ sha256sum darktable-3.8.1.tar.xz 81ee069054dbde580749b2d3a81cda01b7d169a82ba48731823f3ea560b2bef6 darktable-3.8.1.tar.xz $ sha256sum darktable-3.8.1.dmg 9ca2bb86af90e76aeb67e0e12e167dc35d8a022ee79d66a1e08c5b0345d123a8 darktable-3.8.1.dmg $ sha256sum darktable-3.8.1-win64.exe 9ed13cc0972c4473c7e5ac69b3393e6636ba9e2a2cf8b8b9e2a51882288235d1 darktable-3.8.1-win64.exe When updating from the currently stable 3.6.x series, please bear in mind that your edits will be preserved during this process, but the new library and configuration will no longer be usable with 3.
This is a companion discussion topic for the original entry at https://www.darktable.org/2022/02/darktable-3.8.1-released/
19 Likes
As always, please see the published news article (here) for a complete and properly formatted version of the announcement.
2 Likes
did you see that the link is also at the bottom of the post above yours? 
Yes I did. I figured it was easier to include the link than say “the link at the bottom of the original post”
2 Likes
@elstoc Chris is this true…someone asked on FB and I went to the pulls and it seemed the problem was that rejected images were showing as rating 0 and this is now fixed so rejected shows as an X?? That is not what this makes it sound like was done?? Just checking…my PC with DT is fried and I am waiting for a new one so I could not check…
For me, on 3.8.1 that variable returns nothing for zero stars and an X for rejected. I suspect that this is the correct behaviour and the release notes are wrong.
That is what I was trying to convey…badly…and it sounds like it is correct now whereas in the past rejected showed as zero…
1 Like