Darktable, a powerful open-source photography workflow application designed for RAW photo processing and non-destructive editing, has officially released version 5.4.1 as a maintenance update for its current stable 5.4 series.
Several fixes address issues in multi-preset export, including incorrect scaling, improper overwrite handling, and incorrect settings applied during batch exports. Issues where RAW-specific presets were incorrectly applied to non-RAW images have also been resolved. Plus, exported images with incorrect parameters when using multiple presets are now handled correctly.
Darktable 5.4.1 also fixes subtle color casts in Bayer dual demosaicers and resolves issues related to the initialization of the Color Equalizer module. Mask handling in the scale pixels module has been corrected, as has the erratic behavior of the curvature sliders in the mask manager.
Regarding stability improvements, several potential crashes have been fixed, including those related to workspace loading, locale-dependent camera mounting, and workspace list ordering. A possible standstill when discarding history on fast systems has also been addressed.
Additionally, thumbnail overlays and tooltips now update correctly when metadata variables change, and outdated metadata values from the darkroom have been fixed. The list of editable metadata tags in preferences has been restricted to user-editable fields to avoid inconsistencies.
On the hardware and platform side, Darktable 5.4.1 fixes loading issues with certain Olympus ORF files that could previously cause crashes or memory corruption. RustiCL now uses the same default compiler optimization flags as other platforms. Noise profiles have been added for the Canon EOS 10D and Sony ILCE-7CR.
Lastly, the release maintains existing limitations around unsupported compression formats, including Apple ProRAW DNGs, Fujifilm lossy RAFs, Nikon high-efficiency NEFs, and several others. Support for several older cameras remains suspended because RAW samples are missing on raw.pixls.us.
For more information, see the announcement. The full changelog is here.
Users upgrading from the stable 5.2 series are warned that while edits are preserved, the updated library and configuration will not remain compatible with 5.2. Backups are strongly recommended before upgrading.
