darktable 2.4.1 released

darktable
release

(system) #1

we’re proud to announce the first bugfix release for the 2.4 series of darktable, 2.4.1!

the github release is here: https://github.com/darktable-org/darktable/releases/tag/release-2.4.1.

as always, please don’t use the autogenerated tarball provided by github, but only our tar.xz. the checksums are:

$ sha256sum darktable-2.4.1.tar.xz
6254c63f9b50894b3fbf431d98c0fe8ec481957ab91f9af76e33cc1201c29704 darktable-2.4.1.tar.xz
$ sha256sum darktable-2.4.1.dmg
75077f17332a6fda144125ab0f1d3dd219c214bf7602b0b252208f1ec665d031 darktable-2.4.1.dmg
$ sha256sum darktable-2.4.1-win64.exe
0be1e0dd8dec61a7cea41598c52db258edaee8783c543b4311fa0ac56ab43d2a darktable-2.4.1-win64.exe
$ sha256sum darktable-2.4.1-win64.zip
560d82e4c87c002f0284daca922023df136c822713e3670ba42358c9427fe26c darktable-2.4.1-win64.zip

when updating from the currently stable 2.2.x series, please bear in mind that your edits will be preserved during this process, but it will not be possible to downgrade from 2.4 to 2.2.x any more.

Important note: to make sure that darktable can keep on supporting the raw file format for your camera, please read this post on how/what raw samples you can contribute to ensure that we have the full raw sample set for your camera under CC0 license!

and the changelog as compared to 2.4.0 can be found below.

New Features

  • Allow to select the GUI language in the preferences
  • Add a filter rule to the collect module to find locally copied images
  • Add favourite toggle to darkroom modules’ right click popup
  • Allow blending/masking in the hot pixels module
  • Add keyboard shortcuts to zoom and pan an image in darkroom. Panning uses the arrow keys, zooming defaults to ctrl- and ctrl+. Use alt and ctrl to change the step size of panning.
  • Some minor speedups in the grain module
  • Handling stdout on Windows: do not redirect stdout for simple command line arguments (--help and --version)
  • On Windows, show the location of the log file in the help message
  • Enable searching in the more modules list – click into the list to give focus to it, then start typing. The default GTK shortcut ctrl-f doesn’t work as it’s used for filmstrip already
  • Add a debug print when compiling OpenCL kernels

Bugfixes

  • Use the configured overwrite color profile when exporting from Lua – this broke GIMP integration
  • Support presets with < in their name
  • Fix export to non-existing path with \ as the path separator on Windows
  • Don’t insist on the db being locked when it doesn’t even exist
  • Don’t touch the mix slider when resetting the curve in color zones
  • Fix a bug in the exposure module that would only allow corrections of up to 10 stops
  • Fix custom shortcuts with shift modifier
  • Properly ellipsize text in the recently used collections list
  • Fix exported galeries with filenames containing a '
  • Fix finding mipmaps cache folder in purge_from_cache.sh script
  • Fix a crash in the recently used collections list due to a broken config file
  • Set the sqlite threading mode to Serialized
  • Fix old export presets using OpenEXR
  • Fix building with clang on Windows

Changed Dependencies

  • iso-codes version 3.66 or newer is suggested for a nicer list of translations in the preferences.
  • The Windows installer comes with an updated libexiv2 so TIFF exports should be much faster now

Camera support, compared to 2.4.0

Warning: support for Nikon NEF ‘lossy after split’ raws was unintentionally broken due to the lack of such samples. Please see this post for more details. If you have affected raws, please contribute samples!

Base Support

  • Panasonic DC-G9 (4:3)
  • Paralenz Dive Camera (chdk)
  • Pentax KP
  • Sjcam SJ6 LEGEND (chdk-b, chdk-c)

White Balance Presets

  • Leaf Credo 40
  • Nikon D3400
  • Olympus E-M1MarkII
  • Panasonic DC-G9
  • Sony ILCE-7RM3

Noise Profiles

  • Canon EOS 750D
  • Canon EOS Kiss X8i
  • Canon EOS Rebel T6i
  • Canon EOS 77D
  • Canon EOS 9000D
  • Canon EOS M100
  • Canon EOS M6
  • Sony DSC-RX100M4
  • YI TECHNOLOGY M1

Translations

  • Czech
  • Dutch
  • French
  • German
  • Hebrew
  • Hungarian
  • Italian
  • Slovenian

This is a companion discussion topic for the original entry at https://www.darktable.org/2018/01/darktable-241-released/

#2

What happened to the buffalo?!


#3

It seems discuss is broken and ignores edits done to existing posts, at least when adding an image.


(darix) #4

You need to use HTML for editing imported posts. It wont render markdown for them.


(darix) #5

Linux packages updated on Various packages for darktable


(Mica) #6

Flahub’s flatpak is also up to date.


(Pat David) #7

@darix fixed it already. yay, the buffalo’s back!


#8

And a lovely .dmg file :slight_smile:


(Mike) #9

Hello patdavid. I’m new to DT and I am really enjoying the app. This is my first look at PX and I’m searching for an answer to a small problem I’m having on windows 10. My system crashed a few days ago and DT did not shut down properly. So, I have been getting and error code 8944 concerning the lock file and a pid that is supposed to be alive. I have a feeling you might have knowledge of this problem. I’ve been searching online for a way to find the lock file in the library but can’t seem to find it. Supposedly you can extract it and put it on the desktop and so on to then be able to open DT successfully. I would appreciate your help or a lead to someone who understands how to get around this problem. Thanks a million. Mike


(Mica) #10

Hi Mike,

Welcome! The lock file lives along side the library.db file, in the ℅APPDATA℅ folder, which I believe is located at C:\Users\<your user>\AppData\Local\darktable\.

So long as DT isn’t running, you can safely delete the lock file.